NIST SP 800-171 Rev 3
03.01 AC (Access Control)

NIST SP 800-171 Rev 3 03.01.05: Least Privilege

Allow only authorized access necessary to accomplish assigned tasks; review privileges periodically; reassign or remove unnecessary privileges.

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

What else in your programme already covers this

This control maps to 59 controls across 25 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 · 6 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.2.5.1 7.2.5.1 Application and system account access reviewed periodically
  • 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

HIPAA Security Rule · 5 controls

NIST SP 800-66 Rev 2 · 5 controls

  • ASBv3-AM-4 Limit access to asset management
  • ASBv3-PA-4 Review and reconcile user access regularly
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • PA-2 Avoid standing access for user accounts and permissions

C5 (Germany) · 4 controls

  • C5-COM-02 Policy for planning and conducting audits
  • C5-IDM-04 Withdraw or adjust access rights as the task area changes
  • C5-IDM-05 Regular review of access rights
  • C5-IDM-06 Privileged access rights

ISO 27001:2022 · 4 controls

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

ISO 27002:2022 · 3 controls

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

ACSC Essential Eight · 2 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • E8-ADMIN-ML3 Restrict Administrative Privileges (ML3)
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ANSSI-HYG-29 Limit Administration Rights on Workstations to Operational Need
  • ASD37-18 Restrict administrative privileges (Essential)
  • ASD37-21 Disable local administrator accounts (Excellent)

CIS Controls v8 · 2 controls

  • CIS-5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts
  • CIS-6.8 Define and Maintain Role-Based Access Control

FedRAMP High · 2 controls

FedRAMP Moderate · 2 controls

UK Cyber Essentials · 2 controls

  • CE-AC.4 Privileged Account Approval and Tracking
  • CE-AC.6 Periodic Review of Privileged Access
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 6.6.4 System and application access 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-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations

SOC 2 · 1 control

  • SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties

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 03.01 AC (Access Control)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.01.05 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 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. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

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