For any organisation that stores, processes or transmits payment card data, an unresolved vulnerability is a potential way into the cardholder data environment (CDE). PCI DSS v4.0.1 sets specific expectations for how those weaknesses are identified, ranked, patched and verified.

Since 31 March 2025, the future-dated requirements introduced in v4.0 are mandatory. They raise the bar most for internal scanning, and they are where many vulnerability management programmes now fall short at assessment. The question to ask isn't "are we scanning every quarter?" It's: does our process rank, fix and verify vulnerabilities the way the standard now requires, and can we show it?

Requirement What it requires Timing
6.3.1 Identify new vulnerabilities from industry-recognised sources, including CERT alerts, and assign risk rankings. At minimum, identify high-risk and critical Ongoing
6.3.2 Maintain an inventory of bespoke and custom software and its third-party components Ongoing
6.3.3 Install patches for critical vulnerabilities; install all other applicable patches within timeframes set by your risk ranking Critical: one month from release
11.3.1 Internal scans; resolve high-risk and critical findings; rescan to confirm At least every three months
11.3.1.1 Address all other findings based on a targeted risk analysis (Requirement 12.3.1) As defined in the TRA
11.3.1.2 Run internal scans authenticated Every internal scan
11.3.1.3 Internal scan after any significant change After each change
11.3.2 External scans by a PCI SSC Approved Scanning Vendor (ASV) that meet the ASV Program Guide's passing criteria At least every three months
11.3.2.1 External scan after any significant change, by qualified personnel (an ASV is not required) After each change

Risk Ranking: Your Ranking, Not the Scanner's

The ranking you assign under Requirement 6.3.1 drives everything downstream. It decides which patches fall under the one-month rule in 6.3.3, and which internal scan findings must be resolved under 11.3.1. CVSS is a useful input, but it is not the answer on its own.

WHAT A SOUND RISK-RANKING METHODOLOGY WEIGHS
  • Exposure: is the system internet-facing, internal, or isolated?
  • Proximity to the CDE: is it in scope, connected to the CDE, or out of scope?
  • Exploitability: is public exploit code available, or is the flaw being actively exploited (for example, listed in CISA's KEV catalogue)?
  • Impact: what would an attacker gain in terms of cardholder data or payment systems?

A CVSS 9.8 flaw on an internet-facing payment application and the same flaw on an isolated lab server are not the same risk. Your methodology should say so, and your records should show it being applied consistently.

There is one important exception: ASV scanning. Under the ASV Program Guide, a finding scored CVSS 4.0 or higher generally fails the external scan. Your internal ranking cannot override that. You either fix the finding or dispute it through the ASV with supporting evidence.

The One-Month Patch Rule

Requirement 6.3.3 is the most time-bound obligation in this area, and v4.0.1 changed its scope.

ONE-MONTH PATCH SCOPE  v4.0 — CRITICAL OR HIGH→v4.0.1 — CRITICAL ONLY
HOW THE RULE WORKS IN PRACTICE
  • The clock starts when the patch is released, not when you detect the gap.
  • "Critical" means critical under your 6.3.1 risk ranking.
  • All other applicable patches follow the timeframes your risk assessment sets, and those timeframes must be documented.
  • Missing the deadline is a non-compliance. A temporary mitigation does not change that on its own. Where there is a legitimate technical or business constraint, document a compensating control (Appendix B, with a Compensating Controls Worksheet) and track the patch to closure.

Internal Scanning Under v4.0.1

Internal scanning is where most programmes built for earlier versions now fall short. Four things need to be in place.

1

Scan Every Quarter, and After Every Significant Change

Internal scans run at least once every three months. Requirement 11.3.1.3 adds a scan after any significant change, such as new systems, major upgrades or network changes.

2

Scan Authenticated

Requirement 11.3.1.2 requires scans to log in with sufficient privileges. Scan accounts with elevated access must be managed under Requirement 8.2.2, and any systems that cannot accept credentials must be documented.

This is the biggest practical change in v4.0.1 internal scanning.

3

Resolve, Rescan, and Handle the Rest by Risk

High-risk and critical findings must be resolved and confirmed by rescan. Every other finding is handled under the targeted risk analysis required by Requirement 11.3.1.1. It cannot simply be ignored.

4

Current Tooling, Qualified and Independent People

The scan tool must be kept up to date with the latest vulnerability information. Scans must be performed by qualified personnel with organisational independence. They do not need to be a QSA or an ASV.

External Scanning

External scans must be performed by an ASV at least once every three months, and each quarter must end in a passing scan. Rescan as often as needed to get there. False positives and disputed findings go through the ASV's dispute process, with evidence.

After a significant change, Requirement 11.3.2.1 requires an external scan by qualified personnel. Findings scored CVSS 4.0 or higher must be resolved and rescanned. Finally, check that the ASV scope matches every external-facing IP address and domain in scope. Scope gaps are one of the most common findings we see.

"Deploying a patch is not the same as fixing the vulnerability. Only verification closes the finding."

A Remediation Workflow That Holds Up at Assessment

1

Detect

Vulnerabilities are identified through scans, vendor advisories, threat intelligence and penetration tests.

2

Locate

Identify the affected asset and confirm whether it is in PCI DSS scope.

3

Rank

Apply the 6.3.1 methodology and record the result.

4

Assign

Name an accountable owner and set a deadline that matches the ranking.

5

Remediate

Patch, upgrade, reconfigure, or disable the vulnerable service.

6

Verify

Confirm the fix with a rescan, configuration review or other technical check.

7

Close With Evidence

Close the finding only once verification evidence is attached.

A single vulnerability register (asset, ranking, owner, deadline, action, verification result) covers most of the evidence assessors ask for.

What Assessors Look For

Requirement Evidence expected
6.3.1 Documented process, vulnerability intelligence sources, risk-ranking methodology, and sample records of ranked vulnerabilities
6.3.2 A current inventory of bespoke and custom software and third-party components
6.3.3 Patch records showing release and installation dates; sampled systems compared against the latest vendor patches
11.3.1.x Four quarters of internal scans, rescans showing resolution, authenticated scan configuration, the 11.3.1.1 targeted risk analysis, evidence of tester qualification and independence, and change-triggered scans linked to change records
11.3.2.x Four quarters of passing ASV scans, dispute records, and change-triggered external scans

For an initial PCI DSS assessment, four passing quarters are not required if the most recent scan passed, the entity has a documented policy requiring quarterly scanning, and findings from the initial scan were corrected as shown by rescans.

Where Programmes Usually Fail

COMMON FINDINGS AT ASSESSMENT
  • A missed quarter: no passing scan for one of the four quarters.
  • Unauthenticated internal scans: still running the way they did before March 2025.
  • Incomplete inventory: cloud resources and newly deployed assets missing from the inventory and scan scope.
  • Closure without verification: findings closed on "patch deployed" with no rescan.
  • Legacy systems: end-of-life software with no documented compensating control.
  • Third-party gaps: provider-managed systems with no patch or scan evidence from the provider.

Final Thoughts

PCI DSS vulnerability management is not about running scans or installing whatever patches are available. It is a single process: identify weaknesses, rank them by real risk, fix them within the required timeframes, verify the fix, and keep the evidence. Requirements 6.3.1, 6.3.3 and 11.3 fit together around that process.

Organisations that run this process throughout the year, rather than in the weeks before an assessment, find their assessments considerably smoother. They are also the ones most likely to close a vulnerability before an attacker finds it.

Frequently Asked Questions

  • How often must vulnerability scans be performed? Internally and externally at least once every three months, and after every significant change. Quarterly external scans must be performed by an ASV.
  • What is the one-month patching requirement? Under Requirement 6.3.3, patches for vulnerabilities you rank as critical must be installed within one month of release. Other applicable patches follow your documented risk-based timeframes.
  • Do internal scans need to be authenticated? Yes. Since 31 March 2025, Requirement 11.3.1.2 requires authenticated internal scanning, with scan credentials managed under Requirement 8.2.2.
  • Can CVSS alone drive remediation priorities? Not for internal risk ranking. CVSS is one input to your 6.3.1 methodology. For ASV scans, however, CVSS thresholds decide whether the scan passes.
  • Is a clean scan enough for compliance? No. You also need vulnerability monitoring, risk ranking, timely patching, a targeted risk analysis for lower-risk findings, and the evidence to show all of it.