What 11.3 is about
PCI DSS requirement 11.3 is about regularly identifying and addressing vulnerabilities — through internal and external vulnerability scans. (Requirement 11.4 is penetration testing, a different activity.)
Internal scans (11.3.1)
- Run internal vulnerability scans at least once every three months.
- Fix high-risk and critical findings, then rescan to confirm they're resolved.
- Use authenticated (credentialed) scanning — unauthenticated scans miss a lot.
- Scan after any significant change.
External scans (11.3.2)
- Quarterly external scans must be run by a PCI SSC Approved Scanning Vendor (ASV).
- Rescan until the ASV confirms issues are resolved (a passing scan).
- Scan after any significant change — this one can be run by qualified personnel, not necessarily an ASV.
Scans after a significant change and internal scans don't need an ASV: qualified internal staff or a third party can run them, as long as the tester is organizationally independent. The official text from the PCI Security Standards Council always wins.
Where Secure Assess fits
Secure Assess ships defensive external and credentialed vulnerability assessment mapped to PCI DSS 11.3, scheduled scans, AI-triaged findings, a PDF report with 11.3 mapping and an ASV-readiness check: ready / not ready. Use it to find and fix issues before and between your official ASV scans.
What this is not
- Not a full PCI DSS 4.0 compliance program or a “meets all requirements” claim.
- Not official ASV attestation or PCI SSC Approved Scanning Vendor output.
- Not PCI 11.4 penetration testing, exploitation or red teaming.
- Not cardholder-data (CHD) discovery or a complete cardholder-data inventory.
This page summarizes PCI DSS v4.0.1 requirement 11.3 in plain language and doesn't quote the standard.