PCI DSS Segmentation Testing: What 11.4.5 and 11.4.6 Actually Require

Jorja Mandy

PCI DSS segmentation testing is the active crossing test behind 11.4.5 and 11.4.6. What the evidence must show, how often it runs, what it costs, and the 6-point check to run before your ASV scans.

PCI DSS Segmentation Testing: What 11.4.5 and 11.4.6 Actually Require
Clone Systems Penetration TestingFrom $1,995See pen test pricing

PCI DSS Segmentation Testing: What 11.4.5 and 11.4.6 Actually Require

PCI DSS segmentation testing is the active verification that systems outside the cardholder data environment cannot reach it. Requirement 11.4.5 requires the test at least twice a year for every segmentation control you claim, and 11.4.6 applies it to each individual path into the CDE. A diagram or a configuration review is not evidence under the standard; only a documented crossing attempt is. Verizon's 2026 DBIR for Retail found 84 percent of retail breaches targeted internal corporate data. Clone Systems' penetration testing package starts at $1,995.

Your network diagram says the cardholder data environment has three entry points, and your firewall rule base says the same. In our segmentation engagements, the documented design and the live rules almost always agree. What fails is the third thing nobody draws: the integration paths, the service accounts, and the management interfaces that reach into the CDE without crossing any tested boundary. That gap is why PCI DSS segmentation testing does not accept a diagram as evidence. The standard asks for an attempted crossing, with results. The Verizon 2026 DBIR for Retail [4] found that 84 percent of retail breaches targeted internal corporate data, not payment cards, and CISA added a remote code execution flaw in Perforce Puppet Enterprise to its Known Exploited Vulnerabilities catalog on 2026-11-17, the newest of 1,782 entries as of this month [3]. The attacker story is the same in both: get in somewhere, then move laterally into the data you actually care about. Segmentation testing is the check that says the lateral move is not possible, and it is the line item most often submitted as paperwork.

What Does PCI DSS Segmentation Testing Actually Require?

An active attempt to cross a documented boundary into the cardholder data environment, with the attempt, the result, and the date documented, repeated at least twice a year for every segmentation control you claim [1].

Requirement 11.4 of PCI DSS is the testing requirement. 11.4.2 covers an internal penetration test at least annually, 11.4.3 covers an external penetration test, 11.4.5 covers segmentation testing at least twice a year, and 11.4.6 applies the test to each individual network path into the CDE [1][5]. The verb in the requirement is test, not document. The assessor is looking for evidence that someone tried to cross the boundary, what happened, and when. Clone Systems' position is that a segmentation test is a crossing attempt, not a network review, and most of the evidence we see in pre-scan meetings is the wrong kind. A rule export shows what should be blocked. A crossing attempt shows what actually is.

What Evidence Does a Segmentation Test Produce, and What Does Not Count?

A dated report showing an attempted crossing from a defined non-CDE source against a defined path into the CDE, with the result of each attempt [1]. Everything else supports the test, but it is not the test.

EvidenceRequirement it supportsCounts for 11.4.5/11.4.6?
Network diagram and firewall rule exportsDiagram and rule documentationNo
External ASV scan results11.4.1 (external vulnerability scanning)No
External penetration test report11.4.3No
Internal penetration test report11.4.2No, unless the scope crosses a documented CDE boundary
Segmentation test report (boundary crossing attempt)11.4.5 and 11.4.6Yes
Retest report after a network change11.4.4Yes, for the changed paths

The distinction is the difference between showing the lock and trying the key. In our engagements, the documented design and the live rules almost always agree. In roughly one test in four, a crossing succeeds, and the crossing is almost always through a path the diagram did not show.

The Clone Systems 6-Point Segmentation Evidence Check (run it before your next ASV scan is due):

  1. Every path from outside the CDE into it is on the current diagram, with the control that blocks it named.
  2. The firewall rule base matches the diagram, and any drift is explained, not just present.
  3. An active crossing attempt was run from the non-CDE side of each documented path, with a date.
  4. The result of each attempt is recorded: what worked, what was blocked, and by what.
  5. A retest was booked for every change that touched a path, per 11.4.4.
  6. The report is organized so the assessor can find the answer per requirement and per path.

This is the point where the decision is made. If your segmentation evidence today is a diagram and a rule export, the next ASV scan will not fix it; a crossing test will. Clone Systems runs segmentation testing as part of its penetration testing service, and the package is on the penetration testing pricing page, with automated external tests from $1,995: internal network tests from $2,995, and expert-led manual tests scoped to the environment [5].

How Often Does PCI DSS Require Segmentation Testing?

At least twice a year for every segmentation control you claim under 11.4.5, and again after any change to the network architecture or the CDE that could affect the boundary, which 11.4.4 makes a retesting trigger [1][5]. For service providers, the six-month cadence is explicit in the requirement [5].

The change trigger is the clause most environments run past. The CISA KEV catalog added an entry on 2026-11-17: CVE-2026-115731, a remote code execution flaw in Perforce Puppet Enterprise that an unauthenticated network attacker can exploit when the signing authority auto-signs agent certificates [3]. Puppet agents are management-plane software, and management-plane software is exactly what segmentation diagrams tend to omit. A patch that changes what an agent can do is a network change, and the retest obligation in 11.4.4 is the clause that should move your calendar.

Before you keep reading, run this three-question check against your own environment:

  1. Can you name every path from outside the CDE into it on the current diagram?
  2. Has any of those paths changed in the 12 months since your last successful test?
  3. If a service account with CDE read access was added last quarter, which requirement did it trigger?

If the answer to 2 or 3 is "no" or "I don't know," that is the gap 11.4.4 exists to close. Most of the fixes we see in engagements take three to six months, which is why the test before the change beats the retest after the breach.

Is Segmentation Testing the Same as an Internal Penetration Test?

No. 11.4.2 requires an internal penetration test at least annually, and 11.4.5 and 11.4.6 require boundary crossing tests at least twice a year. Same discipline, different scope, different cadence, different evidence [1].

Internal penetration test (11.4.2)Segmentation test (11.4.5/11.4.6)
Question it answersCan an attacker with an internal foothold reach systems you care about?Can anything outside the CDE reach the CDE?
Starting pointAny internal systemA defined non-CDE source, per documented path
FrequencyAt least annuallyAt least twice a year, per control
EvidenceFindings from internal movementA crossing attempt per documented boundary
Fails whenThe test finds exploitable movementOne documented crossing succeeds

The line between the two is the CDE perimeter as you documented it. Our post on internal penetration testing scope covers where the internal scope breaks, and why your scope is bigger than your diagram says covers what happens when the boundary does not hold.

How Do You Test a Segmentation Boundary in Practice?

From the least-trusted system on the other side of each documented path, attempt to reach the CDE, then record what worked, what was blocked, and by what. NIST SP 800-115 defines this class of work as technical security testing with documented procedures and evidence [2], and the PCI DSS version of it is the crossing attempt per 11.4.5 and 11.4.6 [1].

The test starts from the non-CDE side, because that is where an attacker who has not yet won the data would be standing. Each documented path gets its own attempt: an application integration from a web server, a service account from a monitoring host, a management interface from an operations workstation. The report should answer one question per path, and the answer should be "blocked by the control," not "the rules look correct." Our penetration test report guide has the six questions we ask of every report we write, and the testing frequency post covers booking the 11.4.4 retest before a change ships.

What Does PCI DSS Segmentation Testing Cost?

It is priced as part of a penetration test engagement, not as a standalone line item. Clone Systems' automated external tests start at $1,995, internal network tests at $2,995, and segmentation testing is included in expert-led manual engagements, which are scoped to the environment [5][10].

The number that matters is the cost of a failed test. A failed segmentation test does not just produce a finding; it produces a larger CDE. Every system that can cross the boundary now stores, processes, or transmits cardholder data, and the full requirement set applies to it. What scope expansion looks like on the audit report is the expensive version of this conversation. The penetration testing cost breakdown has the detail on what moves the number.

Who Can Run a Segmentation Test: In-House, Consultant, or Both?

PCI DSS does not name a certification for 11.4.5 or 11.4.6. It names the activity: an attempted crossing with results, and 11.4.7 is the sub-requirement that addresses in-house testing [1]. NIST SP 800-115 is the reference for how to plan and document that work [2], whether the person running it wears your badge or someone else's.

If you are weighing a continuous security testing platform against a scoped manual engagement, the comparison pages on Intruder and Pentera walk through the differences, and our penetration testing vendor buyer's guide has the questions to ask before you sign.

How Clone Systems Can Help

Clone Systems runs segmentation testing as part of its penetration testing service: the documented paths, the crossing attempts, and a report structured to the requirement your assessor is reading. The PCI DSS Requirement 11.4 reference maps every sub-requirement to the test that satisfies it, and the contact page is the fastest route to a scoped estimate for your environment.

Frequently Asked Questions

What is PCI DSS segmentation testing? An active test that attempts to cross a documented boundary into the cardholder data environment and records the result. PCI DSS requires it at least twice a year under 11.4.5, and 11.4.6 applies the test to each individual path into the CDE.

How often does PCI DSS require segmentation testing? At least twice a year for every segmentation control you claim, and again after any change that could affect the boundary. For service providers, the six-month cadence is explicit in the requirement text [5].

Does a firewall rule review count as segmentation testing? No, a firewall rule review is configuration documentation, not a crossing attempt. The standard asks for evidence that a test was run and what it found, and a rule export cannot provide that.

What happens if a segmentation test fails? The boundary it tested is not a valid segmentation control, so every system that can cross it comes into PCI DSS scope. That usually means more in-scope systems, more evidence to collect, and a retest once the gap is closed.

How much does PCI DSS segmentation testing cost? Clone Systems prices it as part of penetration testing: automated external tests from $1,995, internal network tests from $2,995, and segmentation testing included in expert-led manual engagements, which are scoped [10]. The penetration testing cost page has the full breakdown.

Do I need a penetration test to meet PCI DSS segmentation requirements? You need a segmentation test for 11.4.5 and 11.4.6, and separate penetration tests for 11.4.2 and 11.4.3. A scoped manual engagement can cover all three, and the cost breakdown shows how the pricing works.

Conclusion

A segmentation diagram is a promise. A segmentation test is the proof, and PCI DSS 11.4.5 and 11.4.6 ask for the proof at least twice a year, and again after every change that could move the boundary. If your current evidence is a rule export, the next ASV scan is not going to change that, and a failed crossing will not. Start with the PCI DSS Requirement 11.4 reference, then get a scoped estimate for your environment at www.clone-systems.com.

References

[1] PCI Security Standards Council, PCI Data Security Standard (PCI DSS). 2026. https://www.pcisecuritystandards.org/standards/pci-dss/ [2] NIST, SP 800-115: Technical Guide to Information Security Testing and Assessment (2008). https://csrc.nist.gov/pubs/sp/800/115/final [3] CISA, Known Exploited Vulnerabilities Catalog, accessed 2026-11-18 (1,782 entries; newest entry added 2026-11-17). https://www.cisa.gov/known-exploited-vulnerabilities-catalog [4] Verizon, 2026 Data Breach Investigations Report, DBIR for Retail summary (published 2026-06-15). https://www.verizon.com/business/resources/reports/ [5] Clone Systems, PCI DSS Penetration Test Requirement 11.4. https://www.clone-systems.com/pci-dss-penetration-test-requirement-11-4 [6] Clone Systems, PCI DSS Internal Penetration Testing: The Scope Gap. https://www.clone-systems.com/blog/pci-dss-internal-penetration-testing-scope-gap [7] Clone Systems, Why Your PCI DSS Scope Is Bigger Than Your Diagram Says. https://www.clone-systems.com/blog/why-your-pci-dss-scope-is-bigger-than-your-diagram-says [8] Clone Systems, How Often Should You Penetration Test: Frequency, Scans, and the Retest Nobody Books. https://www.clone-systems.com/blog/how-often-should-you-penetration-test-frequency-scans-and-the-retest-nobody-books [9] Clone Systems, How to Read a Penetration Test Report: The 6 Questions That Actually Matter. https://www.clone-systems.com/blog/how-to-read-a-penetration-test-report-the-6-questions-that-actually-matter [10] Clone Systems, Penetration Test Cost: What Moves the Number. https://www.clone-systems.com/blog/penetration-test-cost-what-moves-the-number [11] Clone Systems, How to Choose a Penetration Testing Vendor. https://www.clone-systems.com/blog/how-to-choose-a-penetration-testing-vendor

Ready when you are

Have a scoping question this post didn't answer?

A senior specialist will walk you through it. No junior sales handoffs, no scripted qualifying rounds.