CIS Controls v8 CIS-3.12: Segment Data Processing and Storage Based on Sensitivity

What else in your programme already covers this

This control maps to 60 controls across 23 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 27701:2019 · 6 controls

6.5.2 Information classification
6.6.1 Business requirements of access control
7.4 Privacy by design and privacy by default
7.4.2 Limit processing
7.5 PII sharing, transfer, and disclosure
8.4.3 PII transmission controls

NIST SP 800-53 Rev 5 · 6 controls

NIST800-AC-16 AC-16 Security and Privacy Attributes
NIST800-AC-4 AC-4 Information Flow Enforcement
NIST800-PE-22 PE-22 Component Marking
NIST800-PT-7 PT-7 Specific Categories of Personally Identifiable Information
NIST800-SC-32 SC-32 System Partitioning
NIST800-SC-49 SC-49 Hardware-enforced Separation and Policy Enforcement

ISO 27001:2022 · 5 controls

5.12 Classification of information
8.12 Data leakage prevention
8.20 Networks security
8.22 Segregation of networks
8.31 Separation of development, test and production environments

PCI DSS 4.0 · 5 controls

1.3.1 1.3.1 Inbound CDE traffic restricted
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
3.3.1 3.3.1 SAD not retained after authorization, even encrypted

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission
NIST-CSF-ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained
NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

AWS Well-Architected Security Pillar · 3 controls

SEC01-BP01 Separate workloads using accounts
SEC05-BP01 Create network layers
SEC07-BP02 Apply data protection controls based on data sensitivity

CMMC 2.0 · 3 controls

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

FedRAMP High · 3 controls

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

FedRAMP Moderate · 3 controls

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

ISO 27002:2022 · 3 controls

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

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

Australian Information Security Manual · 2 controls

ISM-0337 Using media only with authorised systems
ISM-1181 Network zones by criticality

Azure Security Benchmark · 2 controls

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

C5 (Germany) · 2 controls

C5-COS-06 Segregation of data traffic in jointly used network environments
C5-OPS-24 Separation of Datasets in the Cloud Infrastructure

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

CCM-DSP-17 Sensitive Data Protection
CCM-IVS-06 Segmentation and Segregation

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)

CIS Controls v8.1 · 1 control

3.12 Segment Data Processing and Storage Based on Sensitivity

HIPAA Security Rule · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

161R1-SC-4 Information in Shared Resources

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-C1.1 C1.1 Identifying and maintaining confidential information

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 CIS Controls v8 have you already done?

CIS Controls v8 CIS-3.12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If you hold Azure Security Benchmark49% covered · 78 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. 240 were rejected on the ISO 27001:2022 pair alone.

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