PCI DSS 4.0 11.4.5: Segmentation testing

What else in your programme already covers this

This control maps to 30 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27001:2022 · 5 controls

5.35 Independent review of information security
8.16 Monitoring activities
8.20 Networks security
8.22 Segregation of networks
8.29 Security testing in development and acceptance

CMMC 2.0 · 3 controls

CA.L2-3.12.1 Security Control Assessment
RA.L2-3.11.2 Vulnerability Scan
SC.L2-3.13.5 Public-Access System Separation

Azure Security Benchmark · 2 controls

ASBv3-GS-2 Define and implement enterprise segmentation/separation of duties strategy
NS-1 Establish network segmentation boundaries

CIS Controls v8 · 2 controls

CIS-18.1 Establish and Maintain a Penetration Testing Program
CIS-18.4 Validate Security Measures

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-IVS-06 Segmentation and Segregation
CCM-TVM-06 Penetration Testing

HIPAA Security Rule · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(8) Evaluation (Standard)

NIST SP 800-66 Rev 2 · 2 controls

164.308(a)(1)(ii)(A) Risk Analysis (Required)
164.308(a)(8) Evaluation (Standard)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-19 Segment the Network and Partition the Zones

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-22 Network segmentation (Excellent)

AWS Well-Architected Security Pillar · 1 control

SEC11-BP03 Perform regular penetration testing

C5 (Germany) · 1 control

C5-OPS-24 Separation of Datasets in the Cloud Infrastructure

FedRAMP High · 1 control

CA-8 Penetration Testing

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-ID.IM-01 Improvements are identified from evaluations

NIST SP 800-172 · 1 control

3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation

NIST SP 800-53 Rev 5 · 1 control

NIST800-CA-8 Penetration testing

NIST SP 800-53 Revision 5.1 HIGH · 1 control

CA-8 Penetration Testing

SOC 2 · 1 control

SOC2-CC6.6 Measures against threats outside system boundaries are implemented

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.

You are reading one control. How much of PCI DSS 4.0 have you already done?

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 249 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202255.8% covered · 110 gaps If you hold FedRAMP Moderate55.4% covered · 111 gaps If you hold NIST SP 800-53 Rev 553.4% covered · 116 gaps If you hold ISO 27002:202248.6% covered · 128 gaps If you hold CIS Controls v843% covered · 142 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.141% covered · 147 gaps

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.

See the released pairs, $299 each Browse the graph free