PCI DSS does not require every entity to use network segmentation. When segmentation is used to isolate the cardholder data environment (CDE) from other networks, requirement 11.4.5 calls for penetration testing of those controls at least once every 12 months and after changes to the segmentation controls or methods.
Requirement 11.4.6 is an additional requirement for service providers. It calls for testing at least once every six months and after those changes. Confirm applicability, timing, and evidence expectations with your assessor or compliance owner before scheduling the work.
Short answer: the test must cover every segmentation control or method relied upon to isolate the CDE, follow the entity's defined penetration-testing methodology, and confirm the controls are operational and effective. A network diagram or firewall review is useful input, but it is not the whole test.
When PCI DSS segmentation testing applies
The PCI SSC defines segmentation as isolating systems that store, process, or transmit cardholder data from systems that do not. Effective segmentation may reduce PCI DSS scope. Without adequate isolation, connected systems may remain in scope.
Start with three groups: the CDE, systems connected to or able to affect the security of the CDE, and systems the entity intends to treat as out of scope. The segmentation test asks whether the controls relied upon actually prevent unintended paths from the last group into the CDE. Merely assigning different subnets, accounts, or labels does not demonstrate that outcome.
Segmentation is one part of the wider PCI DSS penetration testing plan. Internal and external testing, application-layer coverage, remediation, and re-testing may also apply under requirement 11.4.
Requirement 11.4.5 versus 11.4.6
| Point | Requirement 11.4.5 | Requirement 11.4.6 |
|---|---|---|
| Applicability | Where segmentation is used to isolate the CDE from other networks. | An additional requirement for service providers only. |
| Minimum cadence | At least once every 12 months. | At least once every six months. |
| Change trigger | After any changes to segmentation controls or methods. | After any changes to segmentation controls or methods. |
| Coverage | All segmentation controls and methods in use. | All segmentation controls and methods in use. |
| Method and outcome | Follow the entity's defined penetration-testing methodology and confirm controls are operational and effective and isolate the CDE from all out-of-scope systems. | The same core coverage and outcome, at the service-provider cadence. |
| Tester | Qualified internal resource or qualified external third party with organizational independence. QSA or ASV status is not required. | The same qualification and independence conditions. |
Requirement 11.4.6 is additional for service providers; it is not a replacement for 11.4.5 and does not make 11.4.5 merchant-only. Use PCI SSC's PCI DSS v4.x Resource Hub to find supporting material, while the current standard and applicability notes remain the controlling reference for an assessment.
What the segmentation test needs to cover
The test boundary should be specific enough to show how the CDE is isolated and broad enough to include every control or method the scope decision depends upon. Depending on the architecture, that may include physical or virtual network controls, cloud network policy, host controls, identity-aware access paths, proxies, service-mesh policy, or microsegmentation.
- The documented CDE boundary: systems that store, process, or transmit account data and the relevant flows between them.
- Connected and security-impacting systems: management, authentication, logging, deployment, and other paths that can affect the CDE.
- Every segmentation method relied upon: not just the easiest firewall or one representative network segment.
- Relevant out-of-scope perspectives: the systems and zones from which isolation needs to be established.
- Different security levels: where isolation is used to separate systems with different security levels, include the applicable paths in the plan.
- The defined methodology: record the intended perspectives, validation approach, safety limits, evidence, and handling of findings.
A port list, automated scan, or configuration review may contribute evidence. None should be presented as a universal substitute for testing whether the boundary can be crossed. A scoped network penetration test and segmentation assessment should combine architecture review with controlled technical validation.
Prepare the segmentation test scope
Good preparation prevents a clean report from being based on the wrong starting position. Give the tester enough context to trace each claimed boundary from the diagram to an available test perspective.
| Input | What to record | Why it matters |
|---|---|---|
| Diagrams and flows | Current network, cloud, and account-data flow diagrams. | Connects the assessed boundary to the systems and paths that implement it. |
| Asset groups | CDE, connected, security-impacting, and intended out-of-scope inventories. | Makes the scope decision and omitted systems visible. |
| Control inventory | Firewalls, network policy, security groups, proxies, host controls, identity rules, and other segmentation methods. | Helps establish that all methods relied upon are included. |
| Test perspectives | Available source zones, identities, locations, and destination groups. | Shows which potential paths can actually be validated. |
| Recent changes | Changes to topology, rules, cloud accounts, orchestration, identity, or methods since the last test. | Supports the change-triggered testing decision and focuses review. |
| Operating limits | Approved windows, request limits, fragile systems, contacts, and stop conditions. | Lets the tester validate safely and state limitations honestly. |
Do not hide an inaccessible zone or unavailable perspective. Record it as a limitation so the entity and assessor can decide whether additional access or testing is needed.
Document results, limitations, and remediation
The report should let the entity and its assessor understand the agreed boundary, testing dates, methodology, controls and methods covered, results, findings, and material limitations. It should distinguish a corrected finding from a proposed correction. Requirement 11.4.4 addresses correcting exploitable vulnerabilities and security weaknesses found during penetration testing and repeating testing to verify the corrections.
For each failed boundary, keep the relevant source and destination context, the expected policy, controlled evidence of the observed path, impact, and recommended correction. The follow-up record should identify the environment and date, what was checked, and whether the issue was fixed, partially fixed, not fixed, or could not be verified.
Use the pentest report checklist to review the evidence, or inspect the Balhence sample report before agreeing deliverables.
Evidence boundary: a Balhence report records technical testing within the agreed scope. It does not certify PCI DSS compliance or guarantee that every weakness has been identified. Your assessor determines how the evidence applies to the wider assessment.
Segmentation in cloud and modern network architectures
Multi-cloud networks, short-lived workloads, service meshes, software-defined networking, zero-trust designs, and identity-aware proxies can make the boundary dynamic. Architecture changes how isolation is implemented and evidenced; it does not remove the entity's responsibility to define scope and verify the controls relied upon.
For dynamic environments, record how assets and policy are discovered, which identities or tags drive decisions, how representative test targets are selected, and what change events trigger another review. PCI SSC's discussion of scoping and segmentation in modern network architecture highlights multi-cloud, microsegmentation, asset inventory, and verification as connected problems.
PCI DSS segmentation testing FAQ
Is network segmentation required by PCI DSS?
No. PCI SSC guidance says network segmentation is not itself a universal PCI DSS requirement. It may reduce assessment scope. When it is used to isolate the CDE from other networks, the applicable segmentation-testing requirements must be addressed.
How often must segmentation controls be tested?
Requirement 11.4.5 specifies at least once every 12 months and after changes to segmentation controls or methods. Requirement 11.4.6 is additional for service providers and specifies at least once every six months and after those changes.
Does requirement 11.4.6 replace 11.4.5 for service providers?
No. PCI DSS describes 11.4.6 as an additional requirement for service providers. Confirm how the applicable cadence and evidence will be assessed with your assessor or compliance owner.
Does the segmentation tester need to be a QSA or ASV?
No. The requirements allow a qualified internal resource or qualified external third party with organizational independence. QSA or ASV status is not required for the tester.
Is a firewall-rule review enough?
Requirement 11.4.5 calls for penetration testing of segmentation controls according to the entity's defined methodology. Configuration review can inform the work, but review alone does not replace the required penetration test.
Does a successful segmentation test prove PCI DSS compliance?
No. It supplies technical evidence about the agreed segmentation scope at a point in time. Compliance and validation decisions remain with the entity and its assessor or applicable validation process.
Define the boundary before testing
Share the CDE, segmentation methods, available test perspectives, recent changes, and assessment deadline. Balhence can confirm whether the requested technical scope fits its network and PCI penetration-testing services; your assessor remains responsible for compliance determinations.
Discuss PCI penetration testing Review compliance testing