11.3.2.1 External scans after significant change
External vulnerability scans are performed after any significant change, with vulnerabilities scored 4.0 or higher by CVSS resolved and re-scans confirm resolution.
5
artefacts
3
held by a system
0
at each review
easy
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Change tickets linked to post-change scans · Vulnerability scanner / patch tooling
- Remediation tickets for CVSS 4.0+ findings · Vulnerability scanner / patch tooling
- Re-scan reports · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- ASV or internal scanner reports · Policy repository / GRC workspace
- Significant change criteria document · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- No post-change scans
- CVSS 4.0+ findings open
- Re-scan missing
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet11.3.2 External vulnerability scans quarterly by ASV · 11.4.1 Penetration testing methodology defined