Skip to content

PCI DSS Penetration Testing Requirements: Requirement 11.4 Explained Line by Line

PCI DSS v4.0.1 Requirement 11.4 explained: internal and external tests, segmentation testing, retesting, methodology, tester qualifications, QSA evidence.

Azad KhanBy , Senior GRC & ComplianceWahid IqbalReviewed by Wahid Iqbal, Head of ComplianceUpdated 12 min read

Network Penetration Testing ServicesExternal from $4,200, internal from $6,000Fixed scope, free retest, no hourly billing.

Get my fixed price

PCI DSS spells out the penetration testing it wants in more detail than almost any other framework. Requirement 11.4 of PCI DSS v4.0.1 sets the methodology, the cadence, the scope, the independence of the tester, and the retest. The standard itself is in the PCI SSC document library. This guide goes through it one sub-requirement at a time, then covers the parts the standard leaves to you: what “significant change” means, how segmentation testing differs from a normal test, and what your Qualified Security Assessor needs in the evidence. If you are ready to book the test itself, our PCI DSS penetration testing services cover Requirement 11.4 at a fixed price, with external testing from $4,200 and a free retest.

If you want the whole standard in one place, start with our PCI DSS compliance checklist.

Requirement 11.4 at a glance

Sub-requirement What it asks for Cadence
11.4.1 A documented penetration testing methodology Maintained continuously
11.4.2 Internal penetration test by a qualified, independent tester Every 12 months and after significant change
11.4.3 External penetration test by a qualified, independent tester Every 12 months and after significant change
11.4.4 Exploitable vulnerabilities corrected and the fix verified by retest After every test
11.4.5 Penetration test of segmentation controls Every 12 months and after changes to segmentation
11.4.6 Segmentation testing for service providers Every 6 months and after changes
11.4.7 Multi-tenant service providers support customers’ external testing Ongoing

11.4.1: the methodology

The standard requires a defined, documented and implemented penetration testing methodology that:

  • is based on industry-accepted approaches (NIST SP 800-115 and PTES are the ones assessors expect to see named);
  • covers the entire cardholder data environment perimeter and critical systems;
  • tests from both inside and outside the network;
  • validates any segmentation and scope-reduction controls;
  • includes application-layer testing that, at minimum, covers the vulnerabilities listed in Requirement 6.2.4 (injection, cryptographic failures, broken authentication and access control, and the rest of the common application flaw classes), which is the ground a web application penetration testing engagement covers;
  • includes network-layer testing of all components that support network functions and operating systems;
  • reviews and considers threats and vulnerabilities experienced in the last twelve months;
  • documents the approach to assessing and addressing the risk posed by exploitable vulnerabilities found;
  • retains test results and remediation activity for twelve months.

A vendor’s methodology document, or the methodology section of the report, satisfies this if it says these things and the test actually did them. Our methodology page is written to be handed to a QSA.

What the PCI SSC penetration testing guidance adds

The Council’s information supplement, Penetration Testing Guidance (version 1.1, September 2017), is guidance, not a requirement, and it still uses the v3.2 numbering. It remains the fullest statement of what the Council expects a test to look like:

  • Authenticated testing. Where an application requires login, testing should cover all roles or types of access, and on multi-tenant systems the tester should hold customer-level credentials to check that one customer cannot reach another’s cardholder data.
  • Social engineering. PCI DSS does not require it. An entity may add it to its methodology, and the guidance suggests documenting the reason if it is left out.
  • Tester qualifications. Certifications can indicate competence, but the guidance says experience and qualifications cannot be met by certifications alone, and it lists questions to ask about past engagements.
  • Report contents. Executive summary, statement of scope, statement of methodology, statement of limitations, testing narrative, segmentation test results, findings, tools used, and clean-up instructions.
  • Evidence retention. The guidance recommends agreeing retention and destruction of the tester’s evidence before the test starts, and says storing cardholder data on tester systems is not recommended.

11.4.2 and 11.4.3: internal and external tests

Both are required at least once every twelve months and after any significant infrastructure or application upgrade or change. Both must be performed by a qualified internal resource or a qualified external third party, and the tester must have organizational independence from the systems being tested. Independence does not require an external firm, but it does mean the people who built and run the CDE cannot be the people who test it, which is why most merchants and service providers use an outside tester and file the tester’s qualifications with the report. Most of this work runs remotely; for payment processors and fintechs in Georgia, our page on PCI DSS penetration testing in Atlanta explains when on-site work is arranged.

External means testing from outside the network against the CDE perimeter: internet-facing systems, remote access, the applications that touch cardholder data. Internal means testing from inside, with the access an attacker would have after compromising a workstation or a non-CDE segment, to see whether the CDE can be reached. Our external network and internal network engagements are scoped to these two sub-requirements respectively. If you are choosing an outside tester, our list of PCI penetration testing companies compares the firms that do this work, including which say they also deliver the ROC assessment and ASV scans.

Which SAQs include Requirement 11.4

Whether 11.4 applies to you depends on how you validate:

  • Report on Compliance and SAQ D. 11.4 applies in full. SAQ D is the questionnaire for service providers and for merchants no other SAQ fits. Service providers also carry the six-month segmentation test (11.4.6) if they use segmentation, and 11.4.7 if they are multi-tenant.
  • SAQ A-EP. For e-commerce merchants whose own website controls how the payment page reaches the customer. It includes the methodology, the external test of that site and its infrastructure, the retest, and segmentation testing if you use segmentation (11.4.1, 11.4.3, 11.4.4 and 11.4.5). The internal test (11.4.2) is not in it. Our e-commerce penetration testing guide covers what that external test should include for an online store.
  • SAQ A. For card-not-present merchants that fully outsource all cardholder data functions, payment pages included. It does not include 11.4. Since the SAQ A revision that took effect on 31 March 2025, it also no longer carries the payment-page script requirements 6.4.3 and 11.6.1; merchants with embedded payment forms instead confirm that their site is not susceptible to script attacks.
  • SAQ B-IP and SAQ C. Only the segmentation test (11.4.5), and only if you use segmentation to isolate the CDE.
  • SAQ B, C-VT and P2PE. No 11.4 requirements.

SAQs are revised from time to time, so check the version your acquirer asks for. If you are not sure which questionnaire you are on, our guide to PCI compliance levels and SAQ types matches each payment setup to its SAQ. Our PCI DSS penetration testing page shows the usual scope for each route, and your acquirer or QSA has the final word. What each SAQ route costs in total is in our guide to PCI compliance cost.

What counts as a “significant change”

PCI DSS leaves the definition to the entity, but the guidance and assessors are consistent on the kinds of change that trigger a test: a new or upgraded operating system or platform in the CDE, new network connections or firewall rule changes affecting CDE boundaries, a new payment application or a major version of one, migration to or between cloud providers, and changes to segmentation. Document the definition in your methodology, and document the decision each time a change happens, even when the decision is “no test needed.” Assessors ask for the record.

11.4.4: fix it and prove it

Exploitable vulnerabilities and security weaknesses found during testing must be corrected in accordance with your assessment of the risk (from 6.3.1), and the corrections must be verified by repeating the test. In practice this means the retest report is as much a piece of PCI evidence as the original. A test that ends with open critical findings and no retest is a test the QSA will write up. We include the retest in every engagement for this reason; see pricing.

11.4.5 and 11.4.6: segmentation testing

If you use network segmentation to keep systems out of PCI scope, you have to prove the segmentation works. Segmentation testing is different from a normal internal test: the tester starts in the out-of-scope segments and tries to reach the CDE through every path (network, shared services, jump hosts, management interfaces, cloud peering). Success means no path exists. Guest and corporate Wi-Fi count as starting points too, and on-site wireless penetration testing from $3,800 covers that side.

  • Merchants: at least every twelve months and after any change to segmentation controls or methods.
  • Service providers (11.4.6): at least every six months and after changes.

This is the sub-requirement most often missed, and the one most likely to fail a Report on Compliance, because it is easy to assume segmentation from the diagram and never test it from the wrong side. Businesses with many card-accepting sites on shared networks feel this most; our page on PCI testing for hotels and restaurants covers that case. Segmentation usually rests on firewall rules between zones, and our guide to firewall penetration testing covers how those rules are tested from the attacker’s side. Our network segmentation testing runs the annual test as part of an internal penetration test, and the six-monthly service provider re-test on its own.

11.4.7: multi-tenant service providers

If you host multiple customers on shared infrastructure, you have to support their external penetration testing, either by allowing them to test or by providing evidence of your own testing that covers their environment. Cloud and hosting providers write this into their customer agreements.

What changed from PCI DSS v3.2.1

PCI DSS v3.2.1 was retired on 31 March 2024, as the PCI SSC confirmed. v4.0.1, a limited revision published on 11 June 2024 with no added or deleted requirements, is the current version. If an old methodology document or vendor template still cites v3.2.1 numbers, this is where each item moved:

v3.2.1 v4.0.1 What it covers
11.3, 11.3.1, 11.3.2 11.4.1, 11.4.3, 11.4.2 Methodology, external test, internal test
11.3.3 11.4.4 Fix exploitable findings and retest
11.3.4 11.4.5 Segmentation testing
11.3.4.1 11.4.6 Six-month segmentation testing for service providers
None 11.4.7 New: multi-tenant service providers support their customers’ external tests
11.2 11.3 Vulnerability scanning, including quarterly ASV scans

The requirements that v4.0 introduced as future-dated became mandatory on 31 March 2025. Among them are multi-factor authentication for all non-console access into the CDE (8.4.2) and the payment-page script controls (6.4.3 and 11.6.1). A test of a checkout or a CDE login should now check both.

Requirement 11.3 is not 11.4

Requirement 11.3 requires internal vulnerability scans at least quarterly, and external scans at least quarterly by a PCI SSC Approved Scanning Vendor, with rescans until passing. Scans and penetration tests are separate requirements with separate evidence, and neither substitutes for the other. Our ASV scan vs penetration test guide explains the difference; our managed vulnerability scanning covers the internal side.

What the QSA wants in the evidence

  1. The methodology document, or the methodology section of the report, covering the 11.4.1 list.
  2. The internal and external test reports, dated within the assessment period, with scope that matches the CDE diagram.
  3. The segmentation test report, with the starting segments and the paths tested named.
  4. Tester qualifications and an independence statement.
  5. Findings with severity, remediation, and the retest showing closure.
  6. The record of significant changes and the testing decision for each.

Our report carries a PCI mapping section that cites each finding against its sub-requirement by number, plus an attestation letter with items 4 and 5 summarized on one page. The format is on the sample report page.

What to request from a PCI penetration testing vendor

Send this list with your scope so every quote answers the same questions:

  1. A methodology document that names its industry basis and covers each point in the 11.4.1 list.
  2. An external test of the CDE perimeter (11.4.3) and an internal test (11.4.2), with dates inside your assessment period.
  3. Application-layer testing of the payment application, behind the login and from every role.
  4. A segmentation test that names the starting segments and the paths tried (11.4.5, or 11.4.6 every six months for service providers).
  5. A retest of exploitable findings, included in the price, with a retest report (11.4.4).
  6. A statement of the testers’ qualifications and their independence from your CDE.
  7. A report whose findings cite the PCI DSS sub-requirement, plus an attestation letter for your QSA.
  8. Agreed handling of evidence: how long the tester keeps it and confirmation that no cardholder data stays on tester systems.

A vendor that cannot commit to items 4 and 5 in writing is selling a network test, not a PCI test. Invadel runs the Requirement 11.4 penetration test. ASV scans and Report on Compliance assessments are delivered through our PCI partner, Sovereign Secure.

Frequently asked questions

Does PCI DSS require a specific certification for the tester? No. It requires that the tester is qualified, with experience in penetration testing, and organizationally independent. Your QSA decides whether the qualifications are sufficient.

Can our internal security team do the test? Yes, if it is organizationally independent of the CDE’s owners and operators. Many companies still use an outside firm to remove the question.

Does a web application firewall change the requirement? No. Requirement 6.4 covers application protection; 11.4 still requires application-layer penetration testing of the CDE.

Does using a hosted payment page remove the requirement? It reduces scope, sometimes to an SAQ A, but any system that could affect the security of cardholder data stays in scope, and your acquirer or QSA decides where the line sits.

How much does PCI penetration testing cost? External testing starts at $4,200 and internal testing, which carries the annual segmentation test, starts at $6,000, each with a free retest. Our fixed prices for the internal, external, application and segmentation components are on the PCI penetration testing cost page.

Is social engineering part of a PCI DSS penetration test? Not by requirement. The PCI SSC’s penetration testing guidance says PCI DSS does not require testing to include social-engineering techniques. You can add it to your methodology, and the guidance suggests recording why if you leave it out.

Does PCI DSS require authenticated application testing? Requirement 11.4.1 requires application-layer testing, and the Council’s guidance says that where an application needs a login, testing should cover all roles or types of access. A test that never logs in to the payment application is unlikely to satisfy a QSA.

How long must PCI penetration test results be retained? Requirement 11.4.1 says results of testing and remediation activities are retained for at least twelve months. Keep the report, the retest and the remediation record together, since the QSA asks for all three.

The short version

Requirement 11.4 wants a documented methodology, internal and external tests every year and after significant changes, a retest that proves the fixes, and segmentation testing on its own clock, all by a qualified tester who did not build the system. Get those six pieces of evidence right and the penetration testing section of the RoC writes itself. If you want it done at a published price, scope a PCI test.

Azad Khan

Written by

Azad Khan, Senior GRC & Compliance

26+ years in the field. Focus: GRC, ISO 27001 & PCI DSS consulting. Part of the team that scopes, tests, and reports for our clients. Full profile →

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online