CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.2: Transaction & Function Control

Confine each authorized user to the specific transactions and functions their role permits, so privileges bound what can be executed and not merely whether access is granted.

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

What else in your programme already covers this

This control maps to 60 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.

PCI DSS 4.0 · 7 controls

  • 7.2.1 7.2.1 Access control model defined
  • 7.3.2 7.3.2 Access control system enforces role-based permissions
  • 9.4.1 9.4.1 Physical security of all media
  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 7.2.6 7.2.6 Query access to stored cardholder data restricted
  • 7.3.1 7.3.1 Need-to-know access control system covers all components
  • 8.6.1 8.6.1 Interactive use of system accounts controlled

CIS Controls v8 · 5 controls

  • CIS-13.10 Perform Application Layer Filtering
  • CIS-13.9 Deploy Port-Level Access Control
  • CIS-3.3 Configure Data Access Control Lists
  • CIS-6.7 Centralize Access Control
  • CIS-6.8 Define and Maintain Role-Based Access Control

ISO 27001:2022 · 5 controls

  • 5.15 Access control
  • 8.15 Logging
  • 8.2 Privileged access rights
  • 8.3 Information access restriction
  • 8.32 Change management

SOC 2 · 5 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

AWS Well-Architected Security Pillar · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • AC-17 Remote Access
  • AC-2 Account Management
  • AC-3 Access Enforcement

FedRAMP Moderate · 3 controls

  • AC-17 Remote Access
  • AC-2 Account Management
  • AC-3 Access Enforcement

HIPAA Security Rule · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-AM-4 Limit access to asset management
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle

C5 (Germany) · 2 controls

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

ISO 27002:2022 · 2 controls

  • 5.15 Access control
  • 8.3 Information access restriction

ISO 27701:2019 · 2 controls

  • 6.6.1 Business requirements of access control
  • 6.6.4 System and application access control

UK Cyber Essentials · 2 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.5 Separate Admin Accounts for Administrative Activities

ACSC Essential Eight · 1 control

  • E8-APP-ML1 Application Control (ML1)

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

  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-18 Restrict administrative privileges (Essential)

CMMC 2.0 Level 1 · 1 control

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

NIST SP 800-171 Rev 3 · 1 control

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.2 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.

If you hold FedRAMP Moderate98.2% covered · 2 gapsIf you hold NIST SP 800-171 Rev 394.5% covered · 6 gapsIf you hold NIST SP 800-53 Rev 585.5% covered · 16 gapsIf you hold ISO 27001:202279.1% covered · 23 gapsIf you hold ISO 27002:202267.3% covered · 36 gapsIf you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll CMMC 2.0 controls