# NIST SP 800-53 Rev. 5 AU-9(4) — Access By Subset Of Privileged Users - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-9-4-access-by-subset-of-privileged-users - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › AU — Audit and Accountability - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `AU-9(4)`·high·Component: **Audit and Accountability** ## What this control requires > Limits management of audit logging functionality to a defined subset of privileged users or roles to reduce risks of unauthorized audit modifications. This control supports the Access Control System capability within the Audit and Accountability family. > > — NIST SP 800-53 Rev. 5, Control AU-9(4) ### In plain English Limits management of audit logging functionality to a defined subset of privileged users or roles to reduce risks of unauthorized audit modifications. 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 **Audit and Accountability**, the assessor will trace your implementation back to the catalogue reference (Control AU-9(4)) 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. - **Audit.** 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. - **Limits.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, system, identity, functionality, review, capability, accountability. ## 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: Access By Subset Of Privileged Users. ## 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.3.8** — Protection of Audit Information](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-3-8-protection-of-audit-information) - [**CIS Controls v8 6.8** — Define and Maintain Role-Based Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-8-define-and-maintain-role-based-access-control) - [**ISO/IEC 27001:2022 A.8.2** — Privileged access rights](https://support.icompaas.com/compliance/iso-27001-2022/a-8-2-privileged-access-rights) - [**BSI C5:2020 IDM-01** — Policy for user accounts and access rights](https://support.icompaas.com/compliance/bsi-c5-2020/idm-01-policy-for-user-accounts-and-access-rights) - [**SOC 2 (2017 TSC) CC6.2** — Access Provisioning](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc6-2-access-provisioning) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control AU-6(7)** — Permitted Actions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-6-7-permitted-actions) - [**Control AU-9(6)** — Read-Only Access](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-9-6-read-only-access) - [**Control AU-10(1)** — Association Of Identities](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-10-1-association-of-identities) - [**Control AU-16(1)** — Identity Preservation](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-16-1-identity-preservation) - [**Control AC-6(6)** — Privileged Access By Non-Organizational Users](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-6-6-privileged-access-by-non-organizational-users) - [**Control AU-6(8)** — Full Text Analysis Of Privileged Commands](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-6-8-full-text-analysis-of-privileged-commands) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control AU-9(4)` Topics: governance riskidentity accessprivileged accessidentity managementaccess reviewlogging monitoring ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.