NIST SP 800-53 Rev 5 NIST800-SC-32: SC-32 System Partitioning

What else in your programme already covers this

This control maps to 34 controls across 17 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 · 7 controls

CIS-12.2 Establish and Maintain a Secure Network Architecture
CIS-12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work
CIS-13.4 Perform Traffic Filtering Between Network Segments
CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.8 Separate Production and Non-Production Systems
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity
CIS-4.12 Separate Enterprise Workspaces on Mobile End-User Devices

PCI DSS 4.0 · 4 controls

1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
2.2.3 2.2.3 Primary functions with different security levels managed
6.5.5 6.5.5 No live PANs in pre-production
6.5.3 6.5.3 Separate pre-production from production

SOC 2 · 4 controls

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC6.1 CC6.1 Logical access security over protected information assets
SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

ISO 27002:2022 · 3 controls

8.22 Segregation of networks
8.27 Secure system architecture and engineering principles
8.31 Separation of development, test and production environments

AWS Well-Architected Security Pillar · 2 controls

SEC01-BP01 Separate workloads using accounts
SEC05-BP01 Create network layers

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

CCM-IVS-05 Production and Non-Production Environments
CCM-IVS-06 Segmentation and Segregation

ISO 27001:2022 · 2 controls

8.22 Segregation of networks
8.31 Separation of development, test and production environments

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

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

Azure Security Benchmark · 1 control

NS-1 Establish network segmentation boundaries

C5 (Germany) · 1 control

C5-COS-06 Segregation of data traffic in jointly used network environments

CMMC 2.0 · 1 control

SC.L2-3.13.5 Public-Access System Separation

FedRAMP High · 1 control

AC-4(21) Physical or Logical Separation of Information Flows

FedRAMP Moderate · 1 control

AC-4(21) Physical or Logical Separation of Information Flows

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-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)

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 NIST SP 800-53 Rev 5 have you already done?

NIST SP 800-53 Rev 5 NIST800-SC-32 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 1014 NIST SP 800-53 Rev 5 controls already carry evidence.

If you hold ISO 27001:202216.1% covered · 851 gaps If you hold ISO 27002:202210.8% covered · 904 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.110.2% covered · 911 gaps If you hold CIS Controls v810.1% covered · 912 gaps If you hold NIST SP 800-171 Rev 310.1% covered · 912 gaps If you hold C5 (Germany)9.6% covered · 917 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. 342 were rejected on the ISO 27001:2022 pair alone.

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