Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IVS-06: Segmentation and Segregation

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

1.3.1 1.3.1 Inbound CDE traffic restricted
1.3.3 1.3.3 NSCs between wireless networks and the CDE
1.4.1 1.4.1 NSCs between trusted and untrusted networks
1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
11.4.5 11.4.5 Annual segmentation penetration testing
11.4.6 11.4.6 Service provider segmentation testing every six months
2.2.3 2.2.3 Primary functions with different security levels managed

NIST SP 800-53 Rev 5 · 6 controls

NIST800-AC-4 AC-4 Information Flow Enforcement
NIST800-SC-2 SC-2 Separation of System and User Functionality
NIST800-SC-32 SC-32 System Partitioning
NIST800-SC-39 SC-39 Process Isolation
NIST800-SC-4 SC-4 Information in Shared System Resources
NIST800-SC-7 SC-7 Boundary Protection

C5 (Germany) · 5 controls

C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
C5-COS-05 Networks for administration
C5-COS-06 Segregation of data traffic in jointly used network environments
C5-OPS-24 Separation of Datasets in the Cloud Infrastructure
C5-PSS-10 Software Defined Networking

FedRAMP High · 5 controls

AC-4 Information Flow Enforcement
AC-4(21) Physical or Logical Separation of Information Flows
SC-39 Process Isolation
SC-4 Information in Shared System Resources
SC-7 Boundary Protection

FedRAMP Moderate · 5 controls

AC-4 Information Flow Enforcement
AC-4(21) Physical or Logical Separation of Information Flows
SC-39 Process Isolation
SC-4 Information in Shared System Resources
SC-7 Boundary Protection

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

ANSSI-HYG-19 Segment the Network and Partition the Zones
ANSSI-HYG-20 Secure Wi-Fi Access Networks and Separate Usage
ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System
ANSSI-HYG-28 Use a Dedicated and Partitioned Network for Administration

AWS Well-Architected Security Pillar · 4 controls

SEC01-BP01 Separate workloads using accounts
SEC03-BP08 Share resources securely within your organization
SEC05-BP01 Create network layers
SEC05-BP02 Control traffic flow within your network layers

CMMC 2.0 · 4 controls

AC.L2-3.1.3 Control CUI Flow
SC.L2-3.13.1 Boundary Protection
SC.L2-3.13.4 Shared Resource Control
SC.L2-3.13.5 Public-Access System Separation

CIS Controls v8 · 3 controls

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

NIST SP 800-161 Rev 1 · 3 controls

161R1-AC-3 Access Enforcement
161R1-SC-4 Information in Shared Resources
161R1-SC-7 Boundary Protection

NIST SP 800-171 Rev 3 · 3 controls

03.01.03 Information Flow Enforcement
03.13.01 Boundary Protection
03.13.04 Information in Shared System Resources

NIST SP 800-172 · 3 controls

3.1.3e Employ Secure Information Transfer Solutions
3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation
3.13.4e Physical and Logical Isolation Techniques

Azure Security Benchmark · 2 controls

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

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected
NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-22 Network segmentation (Excellent)

HIPAA Security Rule · 1 control

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

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

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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-IVS-06 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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