11.3.2 External vulnerability scans quarterly by ASV
External vulnerability scans are performed at least once every three months by a PCI SSC Approved Scanning Vendor (ASV) with passing scans achieved.
5
artefacts
3
held by a system
1
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
- ASV scan reports for past 4 quarters (passing) · Vulnerability scanner / patch tooling
- Remediation tickets for failed scans · Vulnerability scanner / patch tooling
- Re-scan reports confirming pass · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- ASV attestation of scan compliance · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Scope of external-facing IPs · 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 passing scan
- Scope incomplete
- ASV not engaged
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.1.3 Internal scans after significant changes · 11.3.2.1 External scans after significant change