NIST SP 800-53 Rev. 5 AC-2(7) — Privileged User Accounts

What this control requires

Organizations must establish and administer privileged user accounts based on role-based or attribute-based access schemes. Privileged roles should be monitored, including changes to roles or attributes, and access must be revoked when roles or attributes are no longer appropriate. Privileged roles include responsibilities such as key management, account management, and system administration. This control supports the Governance capability within the Access Control family.

In plain English

Organizations must establish and administer privileged user accounts based on role-based or attribute-based access schemes. In practice, this means you can prove you account management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated critical in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Access Control, the assessor will trace your implementation back to the catalogue reference (Control AC-2(7)) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Account. Document the trigger, the owner and the cadence.
• Access. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Attribute. Document the trigger, the owner and the cadence.
• Access Control. Document the trigger, the owner and the cadence.
• Scope: management, accounts, user accounts, attributes, account management, system administration, access control, identity.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Privileged User Accounts.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.1.7 — Least Privilege - Privileged Functions
• CIS Controls v8 6.7 — Centralize Access Control
• ISO/IEC 27001:2022 A.8.2 — Privileged access rights
• BSI C5:2020 PS-04 — Physical site access control
• SOC 2 (2017 TSC) CC6.2 — Access Provisioning

Related controls in NIST SP 800-53 Rev. 5

• Control AC-6(2) — Non-Privileged Access For Nonsecurity Functions
• Control AC-6(5) — Privileged Accounts
• Control AC-6(7) — Review Of User Privileges
• Control AC-6(6) — Privileged Access By Non-Organizational Users
• Control AC-2(8) — Dynamic Account Management
• Control AC-6(3) — Network Access To Privileged Commands

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control AC-2(7)

Topics: identity accessprivileged accessidentity managementaccess reviewkey management