Join our Newsletter — 33% off our NHI Course
Home› Glossary› NHI Lifecycle Management› Decommissioning
NHI Lifecycle Management

Decommissioning

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: NHI Lifecycle Management

Decommissioning is the controlled retirement of an identity and its access when it is no longer needed. For non-human identities, it requires proof of ownership, usage, and dependency so removal does not disrupt production or leave hidden accounts active longer than intended.

What decommissioning means in identity and access

Decommissioning is not simply disabling an account. It is the controlled retirement of an identity, which means ending access in a way that preserves ownership evidence, avoids breaking dependent systems, and leaves a clear record of why the identity was removed.

For identities that are still embedded in production workflows, the practical challenge is sequencing. A safe retirement process usually distinguishes between disabling access, observing for hidden dependencies, and only then deleting or fully revoking the identity material.

Why decommissioning matters

When retirement is handled badly, the organisation can end up with dormant access, orphaned accounts, stale API keys, or services that keep running on trust that no one still actively owns. That creates both security exposure and operational blind spots, especially in environments with many machine or service identities.

Decommissioning also matters because access removal is part of lifecycle governance. If an identity is no longer needed, the control objective is not just to reduce footprint, but to ensure that privileges, sessions, keys, and dependent integrations disappear on a known timetable rather than lingering indefinitely.

What a controlled decommissioning process has to cover

A controlled retirement process normally starts with ownership confirmation, then moves to usage review, dependency mapping, and staged shutdown. For non-human identities, that often includes checking where the identity authenticates, what secrets it uses, and which applications or pipelines would fail if the identity disappeared too early.

The same process should account for recovery needs. Some identities cannot be removed immediately because logs, audit trails, rollback steps, or application references still depend on them. In those cases, the goal is to make the identity inert while proving that no critical workload still relies on it.

Good decommissioning is therefore as much about evidence as execution. The point is to show that removal was deliberate, that no hidden account remains active, and that the retirement decision is supportable if the identity later appears in logs or vendor tooling.

Decommissioning as a security control

Decommissioning closes the gap between “no longer needed” and “actually gone.” That gap is where overexposure persists, because old identities can retain access after the business owner has moved on, a system has been replaced, or a service has been retired in one environment but not another.

It also reduces the chance that compromised or forgotten credentials remain available for reuse. In practice, decommissioning should be understood as one part of broader access governance, because retirement without verification can leave behind active tokens, certificates, keys, or linked service accounts that still matter operationally.

For a deeper treatment of safe retirement steps, NHI offboarding patterns, and evidence expectations, see NHI Offboarding and Decommissioning Guide. Related control thinking is also reflected in NIST SP 800-53 Rev 5 Security and Privacy Controls, which frames access control, auditability, configuration discipline, and system integrity as part of a controlled lifecycle.

What practitioners should verify before removal

Before an identity is retired, practitioners should verify that the owner is known, the usage pattern is understood, and the dependency chain has been checked. If the identity is non-human, the review should extend to connected workloads, automation jobs, API integrations, and any secret material tied to that identity.

That verification step is what prevents accidental outages and reduces the chance of leaving a shadow identity behind. In mature environments, decommissioning is treated as an explicit change event, not an administrative cleanup task, because the security and availability consequences can be material.

Standards & Framework Alignment

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

OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementDecommissioning is lifecycle removal of accounts and their access.
IA-5 — Authenticator ManagementDecommissioning often requires retiring passwords, keys, tokens, and other authenticators.
AU-2 — Event LoggingDecommissioning needs records showing when access was disabled, revoked, and deleted.
Recommendation — Remove or disable accounts when they are no longer required and confirm residual access is gone. Revoke or retire authenticators tied to the decommissioned identity and verify they can no longer authenticate. Log identity retirement actions so post-removal review can confirm what was changed and when.
CIS Controls v85 — Account ManagementDecommissioning is a core account lifecycle safeguard that prevents stale access from persisting.
Recommendation — Enforce timely removal of unused accounts and validate that access paths are fully retired.
OWASP Non-Human Identity Top 10NHI-01 — Improper OffboardingDecommissioning directly addresses safe offboarding of non-human identities.
Recommendation — Apply offboarding controls that disable, revoke, and delete non-human identities in a controlled sequence.

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