PCI DSS internal vulnerability scans: requirement 11.3.1 explained
By Sam Rivera, Founder, SentinelPanda · October 24, 2026 · 2 min read · PCI DSS
External ASV scans get the attention. Internal scans are where most of the findings live.
Internal versus external
Requirement 11.3.2 covers external scans: quarterly, performed by an Approved Scanning Vendor, and passing under the ASV Program Guide. Requirement 11.3.1 covers internal scans, which do not need an ASV or a QSA. They need qualified personnel with organisational independence from the systems being scanned, which can be an internal team or a third party.
What a compliant quarter needs
- A scan covering every in-scope internal system component.
- High-risk and critical vulnerabilities — as ranked under your own process in 6.3.1 — resolved.
- Rescans confirming they are resolved.
- A scan tool kept up to date with current vulnerability information.
- Scans performed by qualified, organisationally independent personnel.
Authenticated scanning
Requirement 11.3.1.2, assessed since 31 March 2025, requires internal scans to be authenticated, with credentials that have sufficient privileges. An unauthenticated scan sees open ports and banners; an authenticated one sees missing patches and insecure configuration, which is where most internal findings are. Systems that cannot accept credentials must be documented, and any scanning account that can be used for interactive login must be managed under requirement 8.2.2.
The rest of the findings
Before 4.0, medium and low findings could sit indefinitely. Requirement 11.3.1.1 now says all other applicable vulnerabilities are addressed based on the risk defined in your targeted risk analysis under 12.3.1, with rescans as needed. Set a timeline per severity, write down why, and track against it.
After significant change
Requirement 11.3.1.3 adds internal scans after any significant change, with high-risk and critical findings resolved and rescanned. A change-management process that asks "is this significant?" and links to the resulting scan is the simplest evidence.
Making each quarter pass
- Scan early in the quarter, leaving time to remediate and rescan before it ends.
- Reconcile the scan target list with your system component inventory every time.
- Run a disputed-finding process for false positives, with the evidence attached.
- Keep the raw reports and the rescans together, dated.