PCI DSS v4.0.1 Requirement 11.4 calls for internal and external penetration testing at least every 12 months and after significant infrastructure or application changes. Where segmentation isolates the cardholder data environment (CDE), its controls also need validation: at least annually for merchants and every six months for service providers, plus after segmentation changes.
PCI DSS applies to organizations that store, process, or transmit cardholder data, or can affect its security. The applicable penetration testing requirements and scope depend on the environment and validation documents used for the assessment.
A vulnerability scan identifies known vulnerabilities, misconfigurations, and exposed services. A penetration test validates whether weaknesses can be exploited to compromise systems, move through the environment, or access cardholder data. One does not replace the other.
This guide explains PCI penetration testing scope, requirements, frequency, preparation, and reporting for security leaders and compliance teams, discussing remediation efforts to prevent cyber threats against your cardholder data environment.
What is PCI penetration testing?
PCI penetration testing is a security assessment focused on the systems, applications, networks, APIs, and segmentation controls that make up or support an organization's cardholder data environment.
The goal is to test whether exploitable vulnerabilities or security weaknesses could affect the confidentiality, integrity, or availability of cardholder data.
In PCI DSS v4.x, penetration testing is primarily addressed under Requirement 11.4: external and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected.
A PCI DSS penetration test usually includes:
Internal penetration testing
External penetration testing
Application-layer penetration testing
Network-layer penetration testing
Segmentation testing, if segmentation is used to reduce the PCI scope
Retesting of exploitable findings after remediation
Documentation suitable for audit or QSA review
The main objectives of PCI DSS penetration testing are:
Identifying exploitable vulnerabilities
A PCI penetration test should identify weaknesses that could be exploited to compromise systems in or connected to the CDE. This includes exposed services, insecure applications, weak access controls, misconfigurations, authentication flaws, and network paths that should not exist.
Validating security controls
A penetration test helps verify whether security controls are working as intended. This includes network segmentation, firewall rules, authentication controls, access restrictions, monitoring coverage, and application-layer defenses.
Supporting PCI DSS compliance
The test provides evidence that the organization has conducted internal and external penetration testing in accordance with a defined methodology and has corrected exploitable weaknesses.
Prioritizing remediation
A PCI DSS penetration test should help teams focus on the issues that matter most. Findings should be ranked by risk, exploitability, business impact, and potential effect on cardholder data.
Improving security over time
PCI DSS penetration testing is not only an audit exercise. When done properly, it helps teams understand how their environment can be attacked and how to reduce real risk across applications, infrastructure, and payment flows.
Understanding PCI DSS v4.0.1 penetration testing requirements
Requirement 11.4 covers penetration testing. Requirement 11.3 now covers vulnerability scanning; its use for penetration testing belongs to the retired PCI DSS 3.2.1 numbering.
Requirement | What applies / when | Evidence to retain |
|---|---|---|
11.4.1 — Methodology | Define and implement an accepted approach covering the CDE perimeter, critical systems, internal/external perspectives, application/network layers, and segmentation. Consider threats and vulnerabilities experienced in the last 12 months and how identified risks are assessed. | Documented methodology; penetration testing and remediation results retained for at least 12 months. |
11.4.2 — Internal penetration testing | At least every 12 months and after significant infrastructure or application changes. | Scope and report showing internal coverage and qualified, organizationally independent pentesters. |
11.4.3 — External penetration testing | At least every 12 months and after significant infrastructure or application changes. | Scope and report showing external coverage and qualified, organizationally independent pentesters. |
11.4.4 — Remediation | Correct exploitable vulnerabilities and security weaknesses according to assessed risk; repeat penetration testing to verify corrections. | Remediation records and retest results. |
11.4.5 — Segmentation | Where segmentation isolates the CDE: at least every 12 months and after segmentation changes. | Results covering every segmentation control or method used to isolate the CDE. |
11.4.6 — Service-provider segmentation | For service providers using segmentation: at least every six months and after segmentation changes. | Segmentation results covering the controls in use and demonstrating the required cadence. |
11.4.7 — Multi-tenant service providers | Support customers' external penetration testing and verification of corrections under 11.4.3 and 11.4.4. | Evidence of the relevant penetration testing on subscribed infrastructure, or prompt access for customers to perform their own pentests. |
The methodology must include application-layer penetration testing covering at least the vulnerability classes in Requirement 6.2.4. Segmentation validation must confirm that the CDE is isolated from out-of-scope systems and cover any isolation used for systems with different security levels under Requirement 2.2.3. |
Use the current PCI SSC standard and applicable validation documents to confirm which requirements apply to your environment. Agree the scope and evidence expectations with the assessor before penetration testing.
Penetration testing does not replace continuous application protection
Requirement 6.4.2 calls for an automated technical solution that continually detects and prevents web-based attacks against public-facing web applications. A periodic pentest does not replace that control. Payment-page script controls and change/tamper detection also have separate requirements; do not treat a penetration test as evidence that every application-security control is operating.
PCI penetration testing frequency
PCI DSS penetration testing should generally be performed at least once every 12 months and after any significant infrastructure or application upgrade or change.
A significant change could include a new payment application, a major application release, a new payment API, a cloud migration, firewall or segmentation changes, new third-party connectivity, a major platform upgrade, or any change that affects how cardholder data is stored, processed, transmitted, or protected.
The exact definition depends on the environment. A useful rule is this: if a change could affect the security of the CDE or create a new path to cardholder data, it should be reviewed for its impact on PCI DSS penetration testing.
Remediation and retesting process
After the penetration test, the organization should prioritize and remediate findings based on risk, exploitability, and potential impact on the CDE.
Fixing the issue is only part of the process. The fix should also be validated. Retesting provides evidence that exploitable vulnerabilities and security weaknesses were corrected.
This evidence is important for compliance review. A report that lists findings but does not indicate whether exploitable issues have been fixed may create problems during an audit or QSA assessment.
PCI penetration testing process
Scope definition
Every PCI DSS penetration test should start with a scope. Before penetration testing begins, the organization and penetration testing provider need to identify the systems, applications, APIs, networks, cloud assets, endpoints, and third-party connections that store, process, transmit, or could impact the security of cardholder data.
This is where many PCI penetration testing projects go wrong. If the scope is too narrow, the test may miss systems that can affect the CDE. For example, pentesting only a public-facing payment page may not be enough if internal APIs, administrative interfaces, cloud networks, or segmentation controls also support the payment environment.
The scope should include the CDE itself, the CDE perimeter, critical systems, and any connected systems that could create a path into the CDE. It should also define what is out of scope and why.
What to prepare before your PCI pentest
Current asset inventories, payment data flows, and network diagrams showing CDE boundaries and connected or security-impacting systems.
Applications, APIs, IP ranges, segmentation controls, and proposed exclusions with their rationale.
Authorized access and starting points for internal, external, and segmentation penetration testing.
Written authorization, rules of engagement, approved windows, escalation contacts, and operational restrictions.
Relevant recent changes, previous findings, remediation records, and agreed reporting and retest expectations.
External and internal penetration testing (networks and applications)
PCI DSS-focused penetration testing should evaluate external and internal attack surfaces to identify potential vulnerabilities and validate security controls, following the pentesting guidance outlined by the PCI Security Standards Council.
External penetration testing targets systems and services at the perimeter that are accessible from the internet, such as public-facing networks, servers, web applications, and APIs. This type of penetration testing helps uncover security risks that external attackers could exploit to gain unauthorized access to cardholder data or disrupt services.
Internal penetration testing covers the CDE and relevant internal networks, applications, and critical systems. It includes starting points inside the CDE and paths into it from trusted and untrusted internal networks, to assess weaknesses available to insiders or attackers who have breached the perimeter.
Automation and AI-assisted analysis can support the assessment, while security engineers direct the penetration test, validate findings, and assess their effect on the CDE.
Network segmentation testing
Segmentation testing is an essential component of PCI DSS, specifically targeting organizations that implement network segmentation to isolate their CDEs from other networks. The primary goal of segmentation testing is to verify the effectiveness of the implemented controls and ensure they are robust enough to prevent unauthorized access to the CDE.
Segmentation cadence depends on the entity. Requirement 11.4.5 calls for testing at least every 12 months and after segmentation changes. For service providers, 11.4.6 sets the minimum at every six months and after changes. Test all segmentation controls used to isolate the CDE. The PCI SSC Document Library contains the current standard and supporting scoping guidance.
For example, assess whether an out-of-scope office network can reach CDE services that should be isolated. Document the source network, destination, attempted connection, and result; assess any permitted connection against the agreed scope rather than treating every reachable service as an automatic failure.
Documentation and reporting
Maintaining detailed documentation and reporting of the assessment is crucial for demonstrating PCI DSS compliance. The PCI penetration test report should include clear information about the test scope, penetration testing methodology, details about all identified vulnerabilities, remediation recommendations, and retest results. Organizations should retain these reports as evidence of compliance during PCI DSS audits.
In our experience, some auditors may also request that the report include the exact date and time a vulnerability was identified and exploited, as well as the same information for when it was marked as fixed after retesting.
What is the difference between a PCI penetration test and a regular pentest?
A PCI penetration test and a regular penetration test use many of the same pentesting techniques, but they differ in scope, purpose, reporting, and compliance expectations.
A regular penetration test may focus on a single application, API, cloud environment, network, product, or business-critical system. The scope is usually defined by the organization's security priorities.
A PCI penetration test focuses on the cardholder data environment and systems that can affect cardholder data security. It must address PCI DSS expectations for internal penetration testing, external penetration testing, segmentation testing where applicable, methodology, remediation, and evidence retention.
Key differences between PCI DSS penetration testing and regular penetration testing
Area | PCI DSS penetration test | Regular penetration test |
|---|---|---|
Primary purpose | Validate the security of the CDE and support PCI DSS compliance | Identify security weaknesses in a defined target or environment |
Scope | CDE, CDE perimeter, critical systems, connected systems, segmentation controls | Defined by business risk, product scope, or security objectives |
Frequency | At least annually and after significant changes | Based on the internal security program, risk appetite, customer requirements, or release cadence |
Reporting | Must support compliance and audit review | May be more flexible depending on the audience |
Retesting | Expected for exploitable findings | Strongly recommended, but not always required by a framework |
Segmentation testing | Required if segmentation is used to reduce PCI DSS scope | Usually not required unless included in scope |
Methodology | Must be defined, documented, and aligned with accepted approaches | Methodology may vary by provider and objective |
Both types of penetration testing are valuable. The key is to make sure the PCI DSS penetration test is scoped and reported in a way that satisfies Requirement 11.4, rather than treating a generic pentest report as automatically PCI-ready. |
PCI penetration testing vs PCI vulnerability scanning
A PCI vulnerability scan is not the same as a PCI penetration test.
Vulnerability scanning is usually broader and more automated. It identifies known vulnerabilities, missing patches, weak configurations, exposed services, and other security issues.
Penetration testing uses expert analysis, tools, and exploitation to validate weaknesses, chain findings, and determine what an attacker could actually achieve.
Area | Vulnerability scan | Penetration test |
|---|---|---|
Main goal | Identify known vulnerabilities and misconfigurations | Validate exploitability and attack paths |
PCI DSS section | Requirement 11.3 | Requirement 11.4 |
Frequency | At least quarterly and after significant changes, depending on scan type | At least annually and after significant changes |
External requirement | External scans may require an ASV | Pentester must be qualified and independent; not required to be a QSA or ASV |
Method | Mostly automated, with validation | Security engineer-led assessment using tools and automation |
Output | Vulnerability scan report | Exploitation evidence, impact analysis, remediation guidance, and retest evidence |
Compliance role | Required security testing activity | Separate required security testing activity |
Most organizations subject to PCI DSS need both activities. A passing ASV scan does not prove that a penetration test was performed, and a penetration test does not replace required vulnerability scans. |
Key differences between PCI DSS 4.x and PCI DSS 3.2.1
The core idea behind PCI penetration testing has not changed: organizations need to test their environments, identify exploitable weaknesses, fix them, and verify remediation.
However, PCI DSS v4.x changed how the requirements are organized and clarified several expectations.
The most important change is numbering. Penetration testing moved from Requirement 11.3 in PCI DSS 3.2.1 to Requirement 11.4 in PCI DSS v4.x.
Other important changes and clarifications include:
More explicit expectations for a documented penetration testing methodology
Clearer internal and external penetration testing requirements
Clearer segmentation testing expectations
More emphasis on application-layer and network-layer penetration testing
Retention of penetration testing and remediation results for at least 12 months
Explicit use of authenticated internal vulnerability scanning under Requirement 11.3.1.2
Newer requirements around payment page change and tamper detection under Requirement 11.6
More focus on roles, responsibilities, targeted risk analysis, and continuous security processes
For current assessments, organizations should work from PCI DSS v4.0.1 or the version in force at the time of assessment. References to PCI DSS 3.2.1 should be treated as historical unless an auditor is reviewing older evidence.
Internal penetration testing needs appropriate starting points within the CDE and on internal networks that could reach it. External penetration testing examines the exposed perimeter and relevant systems reachable from public networks. Document these perspectives in the scope rather than assuming that one unauthenticated scan covers both.
What Blaze finds in PCI penetration tests
In Blaze's 2025 PCI assessments, recurring findings included weak or risky cryptographic algorithms (CWE-327), improper access control (CWE-284), and sensitive-information exposure (CWE-200). These findings show why an assessment needs to validate how controls behave, not simply confirm that they exist. Our PCI DSS penetration testing findings analysis explains these patterns as part of Blaze's broader 2025 study of more than 660 pentests.
Common tools used in PCI penetration testing
In PCI penetration testing, a wide range of tools is employed to assess the security of the CDE environment and identify potential vulnerabilities that attackers could exploit.
These tools are crucial in evaluating various aspects of an organization's security posture, including network configurations, web applications, wireless networks, and system vulnerabilities. The choice of tools may vary depending on the specific needs and goals of the penetration test, but some commonly used tools in a PCI penetration test include:
Nmap: For network scanning and discovery of open ports and services, as well as segmentation checks.
Nessus: Helps identify known vulnerabilities and configuration weaknesses. Using a scanner does not make its operator an Approved Scanning Vendor; required ASV services must come from a PCI SSC-listed ASV.
Metasploit: A comprehensive exploitation framework for developing and executing exploit code against identified vulnerabilities.
Burp Suite: A powerful web application security testing tool with features such as an intercepting proxy, web vulnerability scanning, and session manipulation.
Wireshark: A network protocol analyzer for capturing and analyzing network traffic, providing valuable insights into potential vulnerabilities and attack vectors. Particularly useful for verifying whether card data is traversing the network unencrypted.
Memory scraping tool: A regex-based RAM scraping tool can help in PCI security testing by identifying credit card data temporarily stored in the memory of a CDE-located server after the pentester has compromised it.

The list above is non-exhaustive, and several other tools can be used depending on the assessment's needs.
What should a PCI penetration test report include?
A PCI DSS penetration test report should help three audiences:
Technical teams that need to fix the issues
Security leaders who need to understand risk
Auditors or QSAs who need evidence that penetration testing was performed properly
Use this checklist when reviewing the penetration testing report and supporting evidence:
Scope and authorization: CDE boundaries, assets, assessment dates, rules of engagement, exclusions, and limitations.
Methodology and coverage: internal and external starting points, application and network layers, and segmentation controls where applicable.
Findings: affected assets, reproduction steps, exploitation evidence, severity, business impact, and remediation guidance.
Fix validation: remediation actions, retest dates, and the status of exploitable vulnerabilities and security weaknesses.
Retain penetration testing and remediation results for at least 12 months under Requirement 11.4.1. The report and supporting records should make the coverage and correction of findings traceable during assessor or QSA review.
For PCI DSS, reporting should be specific enough to show that penetration testing covered the CDE, critical systems, and segmentation controls where applicable.
Engaging a qualified penetration testing company
PCI DSS does not require the penetration tester to be a QSA or ASV. However, the pentester must be qualified, and the organization must maintain independence.
That means the test should not be performed by someone responsible for managing, developing, or maintaining the systems being tested.
When choosing a PCI penetration testing provider, look for experience in pentesting payment environments, familiarity with PCI DSS Requirement 11.4, application and network testing capability, segmentation testing experience, clear rules of engagement, evidence-based reporting, retesting support, and relevant credentials such as CREST, OSCP, OSWE, GPEN, GWAPT, or similar.
A good provider should help you scope the engagement properly, explain what evidence the report will contain, and avoid treating a generic vulnerability scan as a PCI DSS penetration test.
To help organizations navigate supplier selection, we have created a complete guide to choosing the right penetration testing company.
Read our guide to choosing a penetration testing company.
How can Blaze help with your PCI penetration testing requirements?
At Blaze, we have our roots in providing penetration testing services for the financial sector, including banking and payments. We have performed dozens of PCI pentesting assessments throughout the years.
Blaze provides scoped internal, external, application, API, network, and segmentation penetration testing, with documented findings, remediation guidance, and agreed fix validation. Agree the required coverage and reporting with your assessment team. A pentest supports the compliance evidence; it does not establish PCI DSS compliance or replace the assessor's decision.
A practical scoping example: an online payment environment
Consider an e-commerce business with a checkout frontend, payment APIs, an administrative portal, cloud workloads, and a dedicated cardholder data environment (CDE). The PCI penetration test scope cannot be determined from the checkout URL alone. Teams should document where cardholder data flows, which systems can affect its security, and what segmentation controls are relied on to exclude other systems from scope.
A useful kickoff package includes a current network and data-flow diagram, in-scope asset inventory, payment integrations, internal and external test access, authorized test accounts, relevant segmentation rules, and a list of significant infrastructure or application changes since the previous assessment.
The assessor and testing provider should agree which systems require internal and external penetration testing, how application-layer and network-layer coverage will be demonstrated, and whether segmentation validation is required. Cloud-managed services and third-party payment components need a documented responsibility boundary, not an assumption that they are automatically excluded.
When should a payment team schedule another test?
Event | Practical action |
|---|---|
Annual PCI testing cycle | Schedule internal and external penetration testing for the applicable in-scope environment. |
Significant application or infrastructure change | Assess the change and carry out the relevant internal and external penetration testing after the change, as required by PCI DSS. |
Segmentation relied on for scope reduction | Validate the controls at the applicable frequency and after changes to segmentation controls or methods. |
Exploitable finding corrected | Retest to verify that the correction is effective and retain evidence. |
New payment service or architecture | Revisit the CDE boundary, data flows, responsibility matrix, and testing scope before assuming the previous report still applies. |
A penetration test report is evidence for compliance assessment, not a PCI DSS certification. Requirements and testing applicability should be confirmed against the organization's current assessment obligations and with its assessor.
Conclusion
PCI DSS penetration testing is central to protecting cardholder data and demonstrating compliance.
Under PCI DSS v4.x, organizations need to pay close attention to Requirement 11.4, which covers internal and external penetration testing, methodology, remediation, retesting, segmentation testing, and evidence retention.
The most common mistake is treating a vulnerability scan, ASV scan, or generic pentest as a complete PCI DSS penetration test. These activities overlap, but they serve different purposes.
A strong PCI DSS penetration test should be properly scoped to the cardholder data environment, performed by qualified, independent pentesters, include application-layer and network-layer testing, validate segmentation where applicable, and provide clear evidence that exploitable weaknesses were corrected.
For merchants, service providers, SaaS companies, fintech platforms, and any organization handling payment data, applicable PCI penetration testing should be treated as both a compliance requirement and a practical way to reduce payment security risk.




