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

What else in your programme already covers this

This control maps to 26 controls across 15 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 · 5 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-13.9 Deploy Port-Level Access Control
CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

NIST SP 800-53 Rev 5 · 4 controls

NIST800-SC-32 System Partitioning. Partition the system into [organization-defined] residing in separate [organization-defined] domains or environments based on [organization-defined]
NIST800-SC-46 Cross Domain Policy Enforcement. Implement a policy enforcement mechanism [organization-defined] between the physical and/or network interfaces for the connecting security domains
NIST800-SC-49 Hardware-enforced Separation and Policy Enforcement. Implement hardware-enforced separation and policy enforcement mechanisms between [organization-defined]
NIST800-SC-50 Software-enforced Separation and Policy Enforcement. Implement software-enforced separation and policy enforcement mechanisms between [organization-defined]

AWS Well-Architected Security Pillar · 2 controls

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

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

NIST SP 800-172 · 2 controls

3.1.3e Employ Secure Information Transfer Solutions
3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation

SOC 2 · 2 controls

SOC2-CC6.6 Measures against threats outside system boundaries are implemented
SOC2-CC6.7 Transmission of data is restricted to authorized users

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-22 Network segmentation (Excellent)

Azure Security Benchmark · 1 control

NS-1 Establish network segmentation boundaries

CMMC 2.0 · 1 control

AC.L2-3.1.3 Control CUI Flow

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

CCM-IVS-06 Segmentation and Segregation

HIPAA Security Rule · 1 control

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

NIST SP 800-171 Rev 3 · 1 control

03.01.03 Information Flow Enforcement

NIST SP 800-66 Rev 2 · 1 control

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

PCI DSS 4.0 · 1 control

1.3.3 NSCs between wireless and CDE

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 FedRAMP Moderate have you already done?

FedRAMP Moderate AC-4(21) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

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