Where segmentation is used to separate the CDE from other networks, the segmentation controls must be penetration tested: at least every 12 months, plus whenever segmentation controls or methods change; covering every segmentation control or method in use; in line with the penetration testing methodology the entity has defined; confirming the segmentation controls or methods are operational and effective and keep every out-of-scope system separated from the CDE; confirming the effectiveness of any isolation used to separate systems of different security levels (Requirement 2.2.3 refers); carried out by a tester who is qualified, whether an internal resource or an external third party; and with organizational independence of the tester (a QSA or ASV is not required). Guidance (good practice): host discovery and port scanning can help show out-of-scope segments cannot reach the CDE. Objective under the customized approach: where segmentation is used, periodic technical testing, including after any changes, confirms it keeps working to wall off all out-of-scope systems from the CDE.
This control maps to 29 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
PCI DSS 4.0 11.4.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 29 it maps to, and the evidence behind each claim, over MCP and REST.