NIST SP 800-53 Rev. 5 AC-3(8) — Revocation Of Access Authorizations

What this control requires

Organizations must enforce the revocation of access authorizations when security attributes of subjects or objects change, based on defined rules governing the timing of revocations. Revocation timing may vary based on access type, such as when access is revoked after group removal or immediately following changes to security labels. Organizations should provide alternative methods for immediate revocation if required. This control supports the Governance capability within the Access Control family.

In plain English

Organizations must enforce the revocation of access authorizations when security attributes of subjects or objects change, based on defined rules governing the timing of revocations. 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 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-3(8)) 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.
• Revocation. 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, attributes, access control, access authorizations, removal, 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: Revocation Of Access Authorizations.

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.11 — Session Termination
• CIS Controls v8 6.7 — Centralize Access Control
• BSI C5:2020 PS-04 — Physical site access control
• ISO/IEC 27001:2022 A.5.2 — Information security roles and responsibilities
• SOC 2 (2017 TSC) CC6.1 — Logical Access Controls

Related controls in NIST SP 800-53 Rev. 5

• Control AC-2(4) — Automated Audit Actions
• Control AC-5 — Separation Of Duties
• Control AC-14 — Permitted Actions Without Identification Or Authentication
• Control AC-16(10) — Attribute Configuration By Authorized Individuals
• Control AC-2(8) — Dynamic Account Management
• Control AC-4(28) — Linear Filter Pipelines

References

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

Topics: identity accessidentity managementaccess reviewprivileged accesschange management