CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.1: Authorized Access Control

Restrict system access so only identified, authorized users, the processes running on their behalf, and approved devices including other connected systems can connect.

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

What else in your programme already covers this

This control maps to 86 controls across 29 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 · 6 controls

  • CIS-3.3 Configure Data Access Control Lists
  • CIS-5.1 Establish and Maintain an Inventory of Accounts
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.2 Establish an Access Revoking Process
  • CIS-6.7 Centralize Access Control
  • CIS-6.8 Define and Maintain Role-Based Access Control

HIPAA Security Rule · 6 controls

NIST SP 800-66 Rev 2 · 6 controls

PCI DSS 4.0 · 6 controls

  • 7.2.1 7.2.1 Access control model defined
  • 7.2.3 7.2.3 Privileges approved by authorized personnel
  • 8.2.1 8.2.1 Unique ID assigned to every user
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • 7.2.5 7.2.5 Application and system accounts least privilege
  • 7.3.1 7.3.1 Need-to-know access control system covers all components

AWS Well-Architected Security Pillar · 5 controls

FedRAMP High · 5 controls

  • AC-17 Remote Access
  • AC-2 Account Management
  • AC-2(3) Disable Accounts
  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-3 Access Enforcement

FedRAMP Moderate · 5 controls

  • AC-17 Remote Access
  • AC-2 Account Management
  • AC-2(3) Disable Accounts
  • AC-2(9) Restrictions on Use of Shared and Group Accounts
  • AC-3 Access Enforcement

NIST SP 800-53 Rev 5 · 5 controls

C5 (Germany) · 4 controls

  • C5-IDM-01 Policy for user accounts and access rights
  • C5-IDM-02 Granting and change of user accounts and access rights
  • C5-IDM-07 Access to cloud customer data
  • C5-PSS-09 Authorisation Mechanisms

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

SOC 2 · 4 controls

  • 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-P5.1 P5.1 Data subject access

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

  • ANSSI-HYG-07 Authorise Network Connection Only for Managed Equipment
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources

Azure Security Benchmark · 3 controls

  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • IM-1 Use centralized identity and authentication system
  • IM-7 Restrict resource access based on conditions

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-20 Multi-factor authentication (Essential)
  • ASD37-21 Disable local administrator accounts (Excellent)

ISO 27001:2022 · 2 controls

  • 5.15 Access control
  • 8.3 Information access restriction

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.2 User access management

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • 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-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.1 User Account Approval Process
  • CE-AC.2 Authenticate Users Before Granting Access

ACSC Essential Eight · 1 control

  • E8-ADMIN-ML1 Restrict Administrative Privileges (ML1)

APPI · 1 control

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CMMC 2.0 Level 1 · 1 control

DFARS 252.204-7012 - Safeguarding Covered Defense Information · 1 control

NIS2 Directive · 1 control

  • Art.21.2.i Human resources security, access control policies and asset management

NIST SP 800-172 · 1 control

  • 3.1.2e Restrict Access to Organization-Owned, Provisioned, or Issued Information Resources

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.1 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 86 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CMMC 2.0 controls