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.

What else in your programme already covers this

This control maps to 97 controls across 32 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 An access control model is defined and includes granting access as follows: • Appropriate access depending on the entity's business and access needs. • Access to system components and data resources that is based
  • 7.2.3 Required privileges are approved by authorized personnel
  • 8.2.1 All users are assigned a unique ID before access to system components or cardholder data is allowed
  • 7.2.4 All user accounts and related access privileges, including third-party/vendor accounts, are reviewed as follows: • At least once every six months. • To ensure user accounts and access remain appropriate based on job function.
  • 7.2.5 All application and system accounts and related access privileges are assigned and managed as follows: • Based on the least privileges necessary for the operability of the system or application. • Access is limited
  • 7.3.1 An access control system(s) is in place that restricts access based on a user's need to know and covers all system components

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

SOC 2 · 4 controls

  • SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets
  • SOC2-CC6.2 Prior to granting access, registration and authorization processes are established
  • SOC2-CC6.3 Role-based access and least privilege are enforced
  • SOC2-P5.1 Personal information is accessed only by authorized personnel
  • 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
  • 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
  • AC-17 Remote Access
  • AC-2 Account Management
  • AC-3 Access Enforcement
  • 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-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

APPI · 1 control

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

CMMC 2.0 Level 1 · 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.

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