NIST SP 800-53 Rev. 5 AC-6(9) — Log Use Of Privileged Functions

What this control requires

Log the execution of privileged functions to detect and mitigate misuse by authorized or unauthorized users, reducing risks from insider threats and advanced persistent threats. This control supports the Security Information and Event Management (SIEM) System capability within the Access Control family.

In plain English

Log the execution of privileged functions to detect and mitigate misuse by authorized or unauthorized users, reducing risks from insider threats and advanced persistent threats. 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.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

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(9)) and look for objective evidence on the latest two assessment cycles.

How to implement

Logging Monitoring

AWS. Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation.

Azure. Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR.

GCP. Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM.

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.
• Log Use. Document the trigger, the owner and the cadence.
• Scope: management, access control, information, system, functions, identity, review, capability.

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: Log Use Of Privileged Functions.

Common pitfalls

• Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days.

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.5.2 — Information security roles and responsibilities
• BSI C5:2020 IDM-06 — Privileged access rights

Related controls in NIST SP 800-53 Rev. 5

• Control AC-6(2) — Non-Privileged Access For Nonsecurity Functions
• Control AC-6(6) — Privileged Access By Non-Organizational Users
• Control AC-6(5) — Privileged Accounts
• Control AC-16(10) — Attribute Configuration By Authorized Individuals
• Control AC-6(3) — Network Access To Privileged Commands
• Control AC-6(10) — Prohibit Non-Privileged Users From Executing Privileged Functions

References

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

Topics: logging monitoringprivileged accessidentity managementaccess review