Organisations should continuously audit accounts, detect inactivity, and tie deprovisioning to lifecycle events such as role changes and departures. The goal is to remove access that is no longer needed before it becomes an attack path or a waste of licence spend. Automated workflows are more reliable than sporadic manual reviews because they reduce delay, inconsistency, and missed orphaned accounts.
Why dormant IAM accounts become a security and cost issue
Dormant accounts are not just unused records. They widen the attack surface, create uncertainty about who still has access, and keep licences and admin overhead tied to identities that no longer need them. The practical problem is that inactivity is easy to miss in large estates, especially when joiner, mover and leaver workflows are fragmented across HR, IT and application owners.
The strongest control signal is not whether an account exists, but whether it still has a current business purpose. That is why lifecycle-linked cleanup matters, and why account inventories need to be reviewed against departures, role changes, project endings and access exceptions rather than only on a calendar basis.
What organisations should check before deprovisioning dormant accounts
Start by confirming whether the account is truly dormant, because some identities look idle but still support scheduled jobs, integrations, break-glass access or seasonal activity. The more critical the account, the more important it is to verify last use, owner, application dependency and whether the account has any shared or inherited permissions.
A useful review also distinguishes between account inactivity and credential inactivity. An account with no interactive login may still authenticate through tokens, APIs or delegated access paths. That is why NHI Dormancy Detection is helpful when teams need to separate genuine inactivity from hidden use signals, and why a second pass should always check for service dependencies before removal.
Before deprovisioning, organisations should also decide what evidence must be retained for audit and recovery purposes, such as the account owner, last activity, approvals and the reason for closure. If an identity still maps to a business process, it should be remediated, not simply deleted.
How to operationalise cleanup without creating avoidable disruption
Effective cleanup is a workflow problem, not a one-time project. The best results come when identity reviews are triggered automatically by lifecycle events, inactivity thresholds and exception expiry, then routed to the right owner for action. That reduces the common failure mode where access reviews happen, but nobody actually removes the account.
For organisations trying to make the process repeatable, Test and Synthetic Accounts Governance Guide is a useful adjacent model because it shows how ownership, expiry and separation principles can be enforced for accounts that are easy to forget. The same discipline applies to dormant production accounts, especially where manual exception handling has created a backlog.
If an account cannot be removed immediately, quarantine is safer than leaving it untouched. That can mean disabling interactive sign-in, removing standing privilege, flagging the owner for confirmation and setting a reactivation workflow so legitimate users are not blocked without a trace.
How to keep dormant accounts from returning
Prevention is better than repeated cleanups. Organisations should define who owns account removal, what inactivity threshold triggers review, how long exceptions can live, and which systems must feed the identity inventory. Otherwise, dormant accounts reappear through rehires, temporary projects, vendor access, shared service IDs and forgotten test credentials.
Identity Security Programme Guide is relevant here because dormant-account management works best when it sits inside a broader identity operating model with clear ownership, governance and process accountability. Without that structure, cleanup becomes episodic and licence savings are quickly lost again.
The most mature teams treat dormant-account reduction as a measurable hygiene control. They track ageing accounts, closure latency, exception volume and reactivation events, then use those trends to identify process gaps before they become both an attack path and a recurring spend problem.
Risk and Threat Considerations
Dormant accounts are attractive because they often escape normal user scrutiny while still retaining valid access. If an attacker finds one with privilege, weak MFA coverage or stale credentials, it can become a low-noise entry point that is harder to detect than a fresh compromise.
Failure mechanism: inactivity creates a control blind spot, and stale accounts keep permissions alive long after the business need has disappeared. Attackers and opportunistic misuse both benefit from identities that are rarely reviewed, lightly monitored or assumed to be harmless.
Impact: the result can be unauthorised access, privilege abuse, lateral movement, licence waste and slower incident response. In some environments, a single forgotten account can also undermine the credibility of access reviews because it shows that review activity is not being converted into actual deprovisioning.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-5 — Account Management | Dormant IAM accounts are an account management hygiene issue. |
| Recommendation — Enforce account lifecycle review and disable or remove inactive accounts. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Dormant accounts require controlled creation, review, disabling and removal. |
| IA-5 — Authenticator Management | Dormant accounts often remain dangerous because credentials, tokens or authenticators still work. | |
| Recommendation — Automate account lifecycle reviews and deactivate accounts when they are no longer required. Rotate or revoke authenticators tied to inactive accounts before reuse or compromise. | ||
| ISO/IEC 27001:2022 | A.5.16 — Identity management | Dormant account control depends on identity lifecycle governance and ownership. |
| A.8.2 — Privileged access rights | Privileged dormant accounts create disproportionate exposure and should be tightly reviewed. | |
| Recommendation — Define identity lifecycle ownership and remove access when business need ends. Review and revoke dormant privileged access quickly and on a fixed cadence. | ||
Practitioner Guidance
What to prioritise: remove dormant accounts that still have privileged access, external exposure or access to sensitive systems first. The longer those accounts remain active, the more likely they are to become either a compromise path or an audit finding.
What to verify: confirm last use, owner, system dependency, approval trail and whether the account can still authenticate through non-interactive mechanisms. If any of those signals are unclear, quarantine before deletion so you can recover safely if the account is still needed.
Common mistake: treating quarterly access reviews as sufficient. A review that does not trigger timely removal only documents the problem, it does not reduce it.
Practitioner takeaway: the right control objective is not “find old accounts”, it is “make stale access impossible to keep by default, and fast to remove when business need ends.”
Related resources from NHI Mgmt Group
- How should security teams govern dormant Office 365 accounts before they become exposure paths?
- How should security teams reduce the risk from dormant SaaS accounts before they become an attack path?
- How should security teams identify inactive Active Directory accounts before they become a governance problem?
- How should Active Directory teams handle expired user accounts before they become a security problem?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org