Guide
PCI DSS penetration testing requirements
PCI DSS is the one common standard that makes penetration testing mandatory and says how often. This is what requirement 11.4 of v4.0.1 asks for, what an assessor checks, and how to deliver a test that passes.
Updated 11 November 2026 · By the Closeout team
Does PCI DSS require a penetration test?
Yes. PCI DSS v4.0.1 requires internal and external penetration tests at least once every 12 months and after any significant infrastructure or application change, plus tests of segmentation controls if segmentation is used to reduce scope. Version 4.0.1 is the current one: 4.0 was retired at the end of 2024 and the requirements that were future-dated became mandatory on 31 March 2025.
Requirement 11.4, point by point
| Requirement | What it asks | How often |
|---|---|---|
| 11.4.1 | A defined, documented methodology based on industry-accepted approaches, covering the whole CDE perimeter and critical systems, from inside and outside the network, at network and application layers. Results and remediation kept for at least 12 months. | — |
| 11.4.2 | Internal penetration test | Every 12 months and after significant change |
| 11.4.3 | External penetration test | Every 12 months and after significant change |
| 11.4.4 | Exploitable vulnerabilities found are corrected per the entity's risk ranking, and the test is repeated to verify the fixes | After every test |
| 11.4.5 | Segmentation controls tested, if used to reduce scope | Every 12 months and after changes |
| 11.4.6 | Same segmentation testing, for service providers | Every 6 months and after changes |
| 11.4.7 | Multi-tenant service providers support their customers' external penetration testing | — |
The tester can be internal or external, but must be qualified and organizationally independent from the systems tested. They don't need to be a QSA or ASV. Penetration testing is separate from the quarterly vulnerability scans in requirement 11.3: a clean ASV scan doesn't replace a pentest.
Remediation and retesting
Requirement 11.4.4 has no day count: exploitable weaknesses are fixed according to the entity's own risk ranking (requirement 6.3.1), and then retested. Separately, requirement 6.3.3 requires patches for critical vulnerabilities within one month of release. In practice, the assessor checks the client's policy, the dates in the remediation record and proof of the retest. Our guide to remediation timelines covers what deadlines to agree.
Evidence the assessor will ask for
- The report, with scope, dates, methodology, who tested and every finding with its severity.
- The remediation record: owner, due date and status of each finding, with dates.
- The retest, which proves each fix works, not just that someone marked it done. See our guide to pentest retesting.
- Accepted risks, in writing, by someone with the authority, with a reason and a review date.
- An attestation letter if the client must show the result to third parties without sharing the full report. You can make one with the attestation letter generator.
Sources
Official texts, checked in November 2026. This is a practical guide, not legal or audit advice.
Frequently asked questions
How often does PCI DSS require a penetration test?
At least once every 12 months and after any significant change, both internal and external. Segmentation tests are every 12 months, or every 6 months for service providers.
Does the tester have to be a QSA?
No. PCI DSS v4.0.1 requires a qualified internal resource or external third party, organizationally independent of what is tested. A QSA or ASV is not required.
Is an ASV scan a penetration test?
No. Quarterly ASV scans (requirement 11.3.2) are automated vulnerability scans. Requirement 11.4 asks for a separate penetration test.
Do findings have to be retested?
Yes. Requirement 11.4.4 requires exploitable vulnerabilities to be corrected and the testing repeated to verify the corrections.