AC-2(3)

Disable Accounts

MODERATEHIGH

01 - The Control

AC-2(3) is a control enhancement to AC-2, Account Management. Where the parent control governs the full lifecycle of system accounts - requesting, approving, provisioning, reviewing - this enhancement handles one specific, high-value job: shutting accounts off when they no longer have a reason to be on.

Control Text — As Specified (Rev 5)

Disable accounts within [time period] when the accounts:

  1. (a) Have expired;
  2. (b) Are no longer associated with a user or individual;
  3. (c) Are in violation of organizational policy; or
  4. (d) Have been inactive for [time period].

Like many NIST controls, AC-2(3) allows an organisation to tailor the control to their needs via an unbound time period: “within [time period]”.


02 - What the Control Is Trying to Achieve

The primary goal of NIST SP 800-53 control enhancement AC-2(3): Disable Accounts is to reduce a system’s attack surface by automatically disabling accounts that are inactive, expired, or no longer required. This prevents threat actors from exploiting dormant credentials to gain unauthorized access or move laterally within a network.


03 - Threats That Exploit Weak or Missing AC-2(3)

When this control is absent or slow to be actioned it can lead to compromise.

  • Staff who left The classic case: an employee or contractor leaves, the account survives, allowing them a path back in.
  • Account is found via external threat Password spraying and credential stuffing succeed disproportionately against stale accounts: passwords are old, MFA enrollment is often missing or tied to a returned device, and the true owner will never report the anomaly.
  • Persistence Post-compromise, attackers deliberately seek out disabled-in-name-only or forgotten accounts (MITRE ATT&CK T1078, Valid Accounts) as durable footholds. A dormant service account with a non-expiring password is ideal as it may survive regulr password reset periods and disablements.

SP 800-53A — Assessment Procedures

Assessment Objectives
  1. time period within which to disable accounts is defined;
  2. time period for account inactivity before disabling is defined;
  3. accounts are disabled within <AC-02(03)_ODP[01] time period> when the accounts have expired;
  4. accounts are disabled within <AC-02(03)_ODP[01] time period> when the accounts are no longer associated with a user or individual;
  5. accounts are disabled within <AC-02(03)_ODP[01] time period> when the accounts are in violation of organizational policy;
  6. accounts are disabled within <AC-02(03)_ODP[01] time period> when the accounts have been inactive for <AC-02(03)_ODP[02] time period>.
Examine

[SELECT FROM: Access control policy; procedures for addressing account management; system security plan; system design documentation; system configuration settings and associated documentation; system-generated list of accounts removed; system-generated list of emergency accounts disabled; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with account management responsibilities; system/network administrators; organizational personnel with information security responsibilities; system developers].

Test

[SELECT FROM: Mechanisms for implementing account management functions].


Revision History - As Issued by NIST

RevIssueDescription of Change
ASP 800-53 Rev 4Enhancement titled “Disable Inactive Accounts” - inactivity was the only trigger, automatic disable required.
BSP 800-53 Rev 5Retitled “Disable Accounts.” Scope widened to four trigger conditions (expired, orphaned, policy violation, inactive) with an organization-defined reaction period.