# NIST SP 800-53 Rev. 5 AC-2(8) — Dynamic Account Management - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-2-8-dynamic-account-management - 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) › AC — Access Control - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `AC-2(8)`·high·Component: **Access Control** ## What this control requires > Organizations must dynamically create, activate, manage, and deactivate system accounts at runtime for entities that were previously unknown. This approach relies on automated provisioning and requires establishing trust relationships, business rules, and mechanisms with appropriate authorities to validate authorizations and privileges. This control supports the Governance capability within the Access Control family. > > — NIST SP 800-53 Rev. 5, Control AC-2(8) ### In plain English Organizations must dynamically create, activate, manage, and deactivate system accounts at runtime for entities that were previously unknown. 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 **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-2(8)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Account.** Document the trigger, the owner and the cadence. - **Dynamic.** 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. - **Access Control.** Document the trigger, the owner and the cadence. - **Scope:** management, accounts, account management, access control, system, identity, authorizations, 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. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Dynamic Account Management. ## 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.8** — Unsuccessful Logon Attempts](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-8-unsuccessful-logon-attempts) - [**CIS Controls v8 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**BSI C5:2020 PS-04** — Physical site access control](https://support.icompaas.com/compliance/bsi-c5-2020/ps-04-physical-site-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) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control AC-5** — Separation Of Duties](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-5-separation-of-duties) - [**Control AC-3(8)** — Revocation Of Access Authorizations](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-3-8-revocation-of-access-authorizations) - [**Control AC-2(6)** — Dynamic Privilege Management](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-2-6-dynamic-privilege-management) - [**Control AC-2(7)** — Privileged User Accounts](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-2-7-privileged-user-accounts) - [**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 AC-10** — Concurrent Session Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-10-concurrent-session-control) ## 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 AC-2(8)` Topics: identity accessidentity managementaccess reviewprivileged accesscode review testing ## 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.