# Vulnerability Scanning Checklist

## Scan Design

- Define what will be scanned: source, dependencies, containers, IaC, or runtime artifacts.
- Know which scanner classes are mandatory and which are advisory.
- Set severity thresholds before running the scan.

## Validation

- Treat scanner output as triage material until confirmed.
- De-duplicate repeated findings across tools.
- Record versions, hashes, and the exact artifact boundary being scanned.

## Follow-through

- Separate exploitable issues from hygiene debt.
- Document false positives and compensating controls.
- Re-run the smallest useful validation after remediation.
