NIST SP 800-53 Rev. 5 AC-6(2) — Non-Privileged Access For Nonsecurity Functions

What this control requires

Require users with access to security functions or information to use non-privileged accounts/roles for nonsecurity tasks, minimizing exposure of privileged accounts. This control supports the Identity and Access Management System capability within the Access Control family.

In plain English

Require users with access to security functions or information to use non-privileged accounts/roles for nonsecurity tasks, minimizing exposure of privileged accounts. In practice, this means you can prove you access 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.

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-6(2)) 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

• Access. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Access Control. Document the trigger, the owner and the cadence.
• Scope: management, accounts, access control, information, system, functions, identity, review.

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.
• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Non-Privileged Access For Nonsecurity Functions.

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.6 — Least Privilege - Privileged Accounts
• CIS Controls v8 6.7 — Centralize Access Control
• ISO/IEC 27001:2022 A.5.2 — Information security roles and responsibilities
• 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(5) — Privileged Accounts
• Control AC-6(6) — Privileged Access By Non-Organizational Users
• Control AC-6(10) — Prohibit Non-Privileged Users From Executing Privileged Functions
• Control AC-6(9) — Log Use Of Privileged Functions
• Control AC-6(3) — Network Access To Privileged Commands
• Control AC-6(1) — Authorize Access To Security Functions

References

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

Topics: identity accessprivileged accessidentity managementaccess review