CMMC 2.0 SC.L2-3.13.5: Public-Access System Separation

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

CIS-12.2 Establish and Maintain a Secure Network Architecture
CIS-13.4 Perform Traffic Filtering Between Network Segments
CIS-16.8 Separate Production and Non-Production Systems
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AC-22 AC-22 Publicly Accessible Content
NIST800-SC-32 SC-32 System Partitioning
NIST800-SC-46 SC-46 Cross Domain Policy Enforcement
NIST800-SC-7 SC-7 Boundary Protection

PCI DSS 4.0 · 4 controls

1.4.2 1.4.2 Restricting traffic entering trusted networks from outside
1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
1.4.5 1.4.5 Internal IP and routing disclosure limited
11.4.5 11.4.5 Annual segmentation penetration testing

AWS Well-Architected Security Pillar · 3 controls

SEC01-BP01 Separate workloads using accounts
SEC03-BP07 Analyze public and cross-account access
SEC05-BP01 Create network layers

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

ANSSI-HYG-19 Segment the Network and Partition the Zones
ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System

Azure Security Benchmark · 2 controls

ASBv3-NS-6 Deploy web application firewall
NS-1 Establish network segmentation boundaries

C5 (Germany) · 2 controls

C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
C5-COS-06 Segregation of data traffic in jointly used network environments

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-22 Network segmentation (Excellent)

CMMC 2.0 Level 1 · 1 control

SC.L1-3.13.5 Public-Access System Separation

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-IVS-06 Segmentation and Segregation

FedRAMP High · 1 control

SC-7 Boundary Protection

HIPAA Security Rule · 1 control

164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-171 Rev 3 · 1 control

03.13.01 Boundary Protection

NIST SP 800-172 · 1 control

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

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(4)(ii)(A) Isolating Health Care Clearinghouse Functions (Required if applicable)

SOC 2 · 1 control

SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

UK Cyber Essentials · 1 control

CE-FW.1 Boundary Firewalls Deployed

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 CMMC 2.0 have you already done?

CMMC 2.0 SC.L2-3.13.5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

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