CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.3: Control CUI Flow

Enforce approved authorization rules on the movement of CUI between systems, components and destinations, so CUI flows only where policy permits.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 51 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 · 5 controls

  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-3.12 Segment Data Processing and Storage Based on Sensitivity
  • CIS-3.13 Deploy a Data Loss Prevention Solution
  • CIS-3.8 Document Data Flows

ISO 27701:2019 · 5 controls

  • 6.10.2 Information transfer
  • 7.4.9 PII transmission controls
  • 7.5.1 Identify basis for PII transfer between jurisdictions
  • 7.5.3 Records of transfer of PII
  • 8.5.3 Records of PII disclosure to third parties
  • SEC03-BP08 Share resources securely within your organization
  • SEC05-BP02 Control traffic flow within your network layers
  • SEC07-BP02 Apply data protection controls based on data sensitivity
  • SEC08-BP04 Enforce access control

ISO 27001:2022 · 4 controls

  • 5.14 Information transfer
  • 5.33 Protection of records
  • 8.12 Data leakage prevention
  • 8.22 Segregation of networks

C5 (Germany) · 3 controls

  • C5-COS-06 Segregation of data traffic in jointly used network environments
  • C5-COS-08 Policies for data transmission
  • C5-IDM-07 Access to cloud customer data

FedRAMP High · 3 controls

  • AC-21 Information Sharing
  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows

FedRAMP Moderate · 3 controls

  • AC-21 Information Sharing
  • AC-4 Information Flow Enforcement
  • AC-4(21) Physical or Logical Separation of Information Flows
  • ANSSI-HYG-19 Segment the Network and Partition the Zones
  • ANSSI-HYG-25 Secure Dedicated Network Interconnections with Partners
  • ASD37-22 Network segmentation (Excellent)
  • ASD37-27 Outbound data loss prevention (Very Good)
  • NS-1 Establish network segmentation boundaries
  • NS-2 Secure cloud services with network controls

ISO 27002:2022 · 2 controls

  • 5.14 Information transfer
  • 8.12 Data leakage prevention
  • NIST-CSF-ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-53 Rev 5 · 2 controls

PCI DSS 4.0 · 2 controls

  • 1.2.4 1.2.4 Accurate data-flow diagram for account data
  • 1.3.2 1.3.2 Outbound CDE traffic restricted
  • AUCDR-IS-3 Securely manage information assets over their lifecycle

HIPAA Security Rule · 1 control

NIST SP 800-172 · 1 control

  • 3.1.3e Employ Secure Information Transfer Solutions

SOC 2 · 1 control

  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

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.

Other controls in Access Control

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 AC.L2-3.1.3 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.

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.

Query this from an agent

The graph holds this control, the 51 it maps to, and the evidence behind each claim, over MCP and REST.