Resources / Guides / Preflight vs Compare: When to Use Each on Linux

Preflight vs Compare: When to Use Each on Linux

A practical decision guide for fast readiness checks versus full baseline drift analysis.

Short answer

Use preflight run when you need a quick, scoped confidence check before a sensitive action. Use compare run when you need a full accounting of what changed relative to your trusted baseline.

Preflight is optimized for speed and go/no-go context. Compare is optimized for depth, triage, and evidence continuity.

Key takeaway

Terms used in this decision

Pick the command by job

Need Use Reason
Quick confidence before a sensitive step preflight run Fast and scoped; designed for immediate readiness decisions
Full account of changes over time compare run Comprehensive drift set for review and triage
Investigating unexplained behavior compare run Provides deeper evidence continuity for incident workflow
Routine pre-action gate preflight run Lower overhead; keeps high-frequency checks practical

Command pattern

auditwalk scan run
auditwalk baseline set --scan-id <scan_id>

# fast confidence check
auditwalk preflight run --include browser

# full drift investigation
auditwalk compare run --format json

Recommended pattern: run preflight before sensitive operations, then schedule compare runs at defined intervals or when you need full drift context. If you are still setting up your operating model, start with How to Know What Changed on Your Linux System and then apply this decision logic.

Where teams get false confidence

References

Keep reading

How to Know What Changed on Your Linux System System Integrity Monitoring for Individuals and Small Teams What to Do After Suspected System Drift

By: AuditWalk Team · Reviewed: 14.04.26 · Last updated: 14.04.26 · Source class: official standards + product docs