EvidenceSheet
PCI DSS v4.0.1 · Req 11: Test Security Regularly

11.3.2.1 External scans after significant change

After any significant change, external vulnerability scans must be performed so that: vulnerabilities with a CVSS score of 4.0 or higher are resolved; rescans are run as needed; and the scans are carried out by qualified personnel with organizational independence from the tested systems (a QSA or ASV is not required). Guidance (good practice): build the scan into the change process and complete it before the change is considered finished, covering every system component the change affects. Customized approach objective: after significant network or system changes, tools that detect vulnerabilities from outside the network confirm the security state of every system component, and detected issues are assessed and fixed using a formal risk assessment framework.

Source: PCI DSS v4.0.1, 11.3.2.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Significant change records for internet-facing systems linked to external scan reports · Vulnerability scanner / patch tooling
  • Rescan output confirming CVSS 4.0+ findings were closed · Vulnerability scanner / patch tooling
  • Scanner qualification and independence records · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Change procedure requiring an external scan before closure · 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

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 sheet

11.3.2 Quarterly ASV external vulnerability scans · 11.4.1 Penetration testing methodology defined and implemented