Verification · Testing · Dynamic security testing
Baseline scan
Passive scan of a deployed preview for headers, cookies and known misconfigurations.
How to build it
- Deploy each pull request to a preview environment.
- Run a passive baseline scan against the preview URL.
- Record the findings and fail only on new header or cookie problems.
Signals in a repository
- A zap-baseline step in a preview or deployment workflow.
- A ZAP rules file that suppresses accepted alerts.
- A preview URL passed to the scanner in the workflow.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.