Join our Newsletter — 33% off our NHI Course
Home› FAQ› NHI Lifecycle Management› How should security teams handle dormant accounts without…
NHI Lifecycle Management

How should security teams handle dormant accounts without leaving downstream access behind?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: NHI Lifecycle Management

Treat the dormant account as the starting point, not the finish line. Disable the identity, then trace linked application roles, tokens, delegated permissions, and service dependencies so access does not persist in systems the IdP cannot see. The goal is to remove entitlement residue, not just inactive usernames.

Why dormant accounts are only the first signal

A dormant account is often the easiest place to notice a problem, but it is rarely the whole problem. The practical issue is that disabling one username does not necessarily revoke every path that identity created elsewhere. Security teams need to think in terms of access graph cleanup, not just account inactivity, especially where tokens, app entitlements, delegated consents, and background jobs can outlive the original login.

This is why IAM and IGA Basics matters here: the account lifecycle and entitlement lifecycle are related, but they are not the same control event. If the identity is disabled without reviewing attached permissions, the system can still act through a separate authorization path that was granted earlier.

Teams should also look beyond the interactive account and into the broader access set. A dormant human user can still own application roles, delegated OAuth-style permissions, API tokens, or linked service dependencies that continue to function even after the account stops being used directly.

What downstream access residue usually looks like

Access residue is the leftover authority that survives the account's apparent death. It can include group membership, cloud roles, long-lived refresh tokens, shared automation secrets, mail or file delegation, and service accounts that were provisioned to support the original user or workflow. In practice, the dormant account is just the entry point for finding those attachments.

For teams trying to distinguish direct inactivity from hidden privilege, Identity Security Posture Management (ISPM) Guide is useful because the posture question is not “Is this account unused?” but “What access does this account still influence?” That shift matters when identity sprawl or permission drift has occurred over time.

Where dormant access is tied to systems and platforms rather than a single directory, NHI Dormancy Detection is a strong model for the same cleanup logic: detect staleness, identify attached credentials or permissions, and quarantine safely before full removal. The same principle applies whether the dormant subject is a person, a service, or an application dependency.

How to remove the account without breaking the workflow

The safest sequence is to disable first, then map everything the account can still reach. That means tracing roles, token grants, delegated permissions, service-account links, scheduled jobs, and any exceptions that were created to make the account operational. If the account was tied to a business process, retire the dependency in a controlled order so that you are not forced to re-enable the account just to keep production alive.

This is where CIS Control 5 Account Management Guide is directly relevant, because inventory and review of accounts only works if service accounts and dormant accounts are handled as part of one lifecycle. The control objective is not just finding the account, but proving that associated access has been removed or intentionally retained with ownership.

When the dormant identity has any cloud, API, or machine-access component, Detection Engineering for Non-Human Identities Guide helps teams look for active use after supposed retirement. That includes token reuse, unexpected sign-ins, or a credential being exercised from a system that should no longer depend on it.

Risk and Threat Considerations

Dormant accounts become dangerous when they retain trust after the business thinks they are dead. Attackers favor these accounts because they often have weaker monitoring, older authentication paths, and forgotten entitlements that survive well past normal review cycles. The real risk is not the inactive username itself, but the unnoticed access path behind it.

Failure mechanism: A disabled or abandoned account can still leave behind application-level authorization, cached tokens, delegated grants, or service dependencies that continue to authenticate and act independently of the original login.

Impact: An attacker or malicious insider can exploit that residue for persistence, unauthorized access, lateral movement, or stealthy re-entry even after the visible account has been locked down.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementTokens and credentials tied to dormant accounts must be expired or rotated to prevent residual access.
AC-2 — Account ManagementDormant account discovery, disablement and follow-up review are core account management duties.
AC-6 — Least PrivilegeResidual roles and permissions should be reduced so dormant identities cannot retain excessive access.
Recommendation — Expire or rotate authenticators linked to dormant identities. Disable dormant accounts and verify associated access is removed. Remove excess entitlements and enforce least privilege after dormancy.
ISO/IEC 27001:2022A.5.16 — Identity ManagementIdentity lifecycle control requires dormant identities and their linked access to be governed and removed.
Recommendation — Manage identity lifecycle so dormant access is identified and revoked.

Practitioner Guidance

What to verify: Confirm that disabling the directory identity also removed or expired every token, app role, delegated permission, and linked service credential that could still act on its behalf. If a system cannot prove that revocation reached the downstream layer, treat the cleanup as incomplete.

Decision rule: If the account ever had production authority, do not rely on “inactive” status alone. Require an explicit entitlement review and a dependency check before closure, because operational continuity and access cleanup often fail in different places.

Practitioner takeaway: The best test of dormant-account handling is not whether the login is disabled, but whether any downstream system can still use that identity's prior trust to do useful work.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org