PCI DSS Penetration Testing Requirements: Scope, Frequency and Evidence
Harsh
Cybersecurity Experts
Table of Contents
- 01PCI DSS penetration testing requirements in brief
- 02Where penetration testing sits in the standard
- 03What the methodology has to cover
- 04Scope: what has to be tested
- 05Segmentation testing
- 06What counts as a significant change
- 07Who can perform the test
- 08PCI DSS 4.0 penetration test: what changed from v3.2.1
- 09Evidence your QSA will ask for
- 10Common reasons for a finding against 11.4
- 11How Digisecuritas supports PCI testing
- 12Schedule a test before your assessment
- 13Frequently Asked Questions
PCI DSS penetration testing requirements in brief
The PCI DSS penetration testing requirements sit in Requirement 11.4 of PCI DSS v4.0.1. They call for internal and external penetration testing at least once every 12 months and after any significant change, testing of segmentation controls where segmentation is used to reduce scope, correction of exploitable findings and a repeat test to confirm the fixes.
Unlike SOC 2, PCI DSS names penetration testing explicitly. If you store, process or transmit cardholder data, or can affect its security, this guide sets out what has to be tested, how often, by whom and what evidence your assessor will ask for.
Where penetration testing sits in the standard
Requirement 11 is titled "Test Security of Systems and Networks Regularly." Requirement 11.3 covers vulnerability scanning. Requirement 11.4 covers penetration testing. In PCI DSS v3.2.1 the same material was numbered 11.3, which is why older guidance uses different references.
Requirement | What it covers | Frequency
|
|---|---|---|
11.4.1 | A defined, documented penetration testing methodology | Maintained and followed |
11.4.2 | Internal penetration testing | At least once every 12 months and after significant change |
11.4.3 | External penetration testing | At least once every 12 months and after significant change |
11.4.4 | Correction of exploitable vulnerabilities and security weaknesses, with repeat testing | After each test, according to your risk assessment |
11.4.5 | Testing of segmentation controls, if segmentation is used | At least once every 12 months and after changes to segmentation |
11.4.6 | Segmentation testing for service providers | At least once every six months and after changes to segmentation |
11.4.7 | Multi-tenant service providers support their customers' external penetration testing | Ongoing |
What the methodology has to cover
Requirement 11.4.1 lists what your documented methodology must include:
Industry-accepted penetration testing approaches
Coverage of the entire cardholder data environment (CDE) perimeter and critical systems
Testing from inside and outside the network
Testing to validate segmentation and scope-reduction controls
Application-layer testing that identifies, at a minimum, the vulnerabilities listed in Requirement 6.2.4
Network-layer testing of all components that support network functions, and of operating systems
Review of threats and vulnerabilities experienced in the last 12 months
A documented approach to assessing and addressing the risk of findings
Retention of test results and remediation results for at least 12 months
A tester's own methodology can satisfy this if it covers each point. Ask your provider to show where.
Scope: what has to be tested
PCI penetration testing covers the CDE and anything that could affect its security.
External testing targets the internet-facing perimeter of the CDE: public IP addresses, web applications, APIs, remote access services and anything else reachable from outside.
Internal testing is performed from inside the network, against the CDE and the critical systems connected to it. It shows what an attacker could do after gaining a foothold.
Application-layer testing covers payment applications and any software that handles card data, including injection, access control and authentication weaknesses.
Network-layer testing covers firewalls, routers, servers and operating systems.
Systems that sit outside the CDE and cannot reach it are out of scope only if segmentation is proven to work.
Segmentation testing
Segmentation isolates the CDE from the rest of your network so that fewer systems fall under PCI DSS. The standard does not require segmentation. If you use it, you have to prove it.
Segmentation testing confirms that systems outside the CDE cannot communicate with systems inside it. The tester attempts connections from each out-of-scope network segment toward the CDE, across all ports and protocols, and records that they are blocked.
Merchants and other entities test segmentation at least every 12 months and after any change to segmentation controls or methods (11.4.5)
Service providers test at least every six months and after changes (11.4.6)
A failed segmentation test means the out-of-scope networks are in scope. That can multiply the size of your assessment, so fix and re-test quickly.
What counts as a significant change
PCI DSS leaves the definition to each entity, with guidance. Changes that normally trigger a new test include:
New hardware, software or networking equipment added to the CDE
Replacement or major upgrade of CDE systems
Changes to the flow or storage of account data
Changes to the CDE boundary or to PCI DSS scope
Changes to the underlying infrastructure, such as a cloud migration
A new payment application or a major release of an existing one
Document your own definition in a policy, apply it consistently and keep a record of each decision to test or not to test.
Who can perform the test
Requirement 11.4 allows a qualified internal resource or a qualified external third party. Two conditions apply:
Organizational independence. The tester must not be responsible for managing, building or supporting the systems under test.
Qualification. The assessor will look at the tester's experience and certifications.
The tester does not need to be a QSA or an ASV. ASVs are required for the quarterly external vulnerability scans under Requirement 11.3, which is a separate obligation. A vulnerability scan does not satisfy the penetration testing requirement.
PCI DSS 4.0 penetration test: what changed from v3.2.1
If your last assessment was under v3.2.1, a PCI DSS 4.0 penetration test differs in these ways:
Requirement numbers moved from 11.3 to 11.4
The methodology requirement now states that results and remediation records are kept for at least 12 months
Requirement 11.4.7 was added, requiring multi-tenant service providers to support their customers' external penetration testing
Internal vulnerability scans under 11.3.1.2 must be authenticated, which affects what your testers and scanners find
The customized approach allows alternative controls where you can show the objective is met
PCI DSS v4.0.1 is the current version. The requirements that were future-dated in v4.0 became mandatory on March 31, 2025.
Evidence your QSA will ask for
The documented penetration testing methodology
Scope documentation tied to your network and data flow diagrams
Internal and external penetration test reports dated within the last 12 months
Segmentation test results, twice a year for service providers
Evidence of tester qualification and independence
Remediation records for exploitable findings
Re-test results confirming the fixes
Records of significant changes and the testing that followed
Retained results for at least 12 months
Common reasons for a finding against 11.4
A vulnerability scan presented as a penetration test
External testing only, with no internal test
Segmentation assumed and never tested
Service providers testing segmentation annually
No test after a significant change
Exploitable findings left open with no re-test
A tester who also administers the systems
Scope that leaves out connected systems
How Digisecuritas supports PCI testing
Digisecuritas performs external and internal network testing, web application and API testing and cloud assessments, with findings mapped to PCI DSS. Deliverables include executive and technical reports, a CVSS risk matrix, proof of exploitation, remediation guidance and a re-test report. Testers hold OSCP, CEH and CREST certifications. See the VAPT services page.
Schedule a test before your assessment
Send us your assessment date, whether you are a merchant or service provider and a summary of your CDE. We will propose a scope that covers 11.4, including segmentation.
