CMMC 2.0
Access Control

CMMC 2.0 AC.L2-3.1.5: Least Privilege

Grant users and processes only the privileges their assigned tasks require, applying this specifically to security functions and to privileged accounts.

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

What else in your programme already covers this

This control maps to 88 controls across 26 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 · 10 controls

  • 3.6.1.3 3.6.1.3 Cleartext key component access limited to minimum custodians
  • 7.2.1 7.2.1 Access control model defined
  • 7.2.2 7.2.2 User access assigned by job function and least privilege
  • 7.3.2 7.3.2 Access control system enforces role-based permissions
  • 7.3.3 7.3.3 Access control default deny all
  • 9.2.3 9.2.3 Physical protection of network hardware and lines
  • 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
  • 8.6.1 8.6.1 Interactive use of system accounts controlled

HIPAA Security Rule · 8 controls

CIS Controls v8 · 6 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-3.3 Configure Data Access Control Lists
  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-5.6 Centralize Account Management
  • CIS-6.1 Establish an Access Granting Process
  • CIS-6.8 Define and Maintain Role-Based Access Control

Azure Security Benchmark · 5 controls

  • ASBv3-GS-6 Define and implement identity and privileged access strategy
  • ASBv3-PA-4 Review and reconcile user access regularly
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • PA-1 Separate and limit highly privileged/administrative users
  • PA-2 Avoid standing access for user accounts and permissions

FedRAMP High · 5 controls

FedRAMP Moderate · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

AWS Well-Architected Security Pillar · 4 controls

ISO 27002:2022 · 4 controls

  • 5.15 Access control
  • 5.18 Access rights
  • 8.2 Privileged access rights
  • 8.3 Information access restriction

NIST SP 800-53 Rev 5 · 4 controls

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

  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need

C5 (Germany) · 3 controls

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

ISO 27001:2022 · 3 controls

  • 5.18 Access rights
  • 8.2 Privileged access rights
  • 8.3 Information access restriction

ISO 27701:2019 · 3 controls

  • 6.6.1 Business requirements of access control
  • 6.6.2 User access management
  • 7.3.6 Access, correction and/or erasure

SOC 2 · 3 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
  • SOC2-P5.1 P5.1 Data subject access

ACSC Essential Eight · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-18 Restrict administrative privileges (Essential)
  • ASD37-21 Disable local administrator accounts (Excellent)

NIST SP 800-171 Rev 3 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.6 Periodic Review of Privileged Access

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

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-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

NIST SP 800-218 · 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.5 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 88 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CMMC 2.0 controls