How Quick Scan, Full Audit, and Focused Rescan differ, and how zone-level visibility and safe probes affect the scan result.
- Quick Scan, Full Audit, and Focused Rescan intent
- Zone selection and scope
- Safe probes and public-edge verification
- Coverage-aware interpretation of results
Applies to
WindowsmacOSLinux
Covers
ScansZonesAnalyticsTroubleshooting
Scan profiles and zone coverage
Why there are three scan profiles
Not every question needs the same scan depth.
The current product supports:
- Quick Scan
- Full Audit
- Focused Rescan
Quick Scan
Use Quick Scan when you need:
- a fast posture snapshot
- a connection smoke test
- a broad triage pass across multiple zones
Full Audit
Use Full Audit when you need:
- higher-confidence review
- report-ready exports
- deeper evidence across the supported posture surfaces
Focused Rescan
Use Focused Rescan when:
- a rule changed
- a finding was remediated
- you only need to re-evaluate a smaller surface
Safe probes
The product can use limited public-edge checks such as:
- public DNS
- TLS verification
- non-destructive HTTP verification
Coverage-aware interpretation
The correct response to partial visibility is to record it, not to erase it from the narrative.