Join our Newsletter — 33% off our NHI Course
Governance, Ownership & Risk

Deactivation

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

Deactivation is the process of disabling an identity’s access while preserving its record and related history. Organisations use it when they need to stop access quickly but still retain evidence for audit, investigation, or retention. It is different from deletion because the identity remains available for governance and compliance purposes.

What deactivation means in identity governance

Deactivation is a lifecycle control, not a deletion event. It preserves the identity object, account history, and governance record while stopping access, which is why it is commonly used when an account must be taken out of circulation quickly without losing evidence needed for audit, investigation, or retention.

Because the identity remains in place, deactivation supports traceability across access reviews, incident timelines, and compliance recordkeeping. It is a safer default than removal when an organisation may need to prove who had access, when access changed, and why the account was disabled.

How deactivation differs from deletion and suspension

Deletion removes the identity record or makes it unavailable for future governance, while deactivation keeps the record intact and blocks use. Suspension is often temporary and may be used for short-term holds, but the exact meaning varies by platform, vendor, and workflow design. In practice, organisations should treat these states as distinct because each one has different effects on recoverability, audit evidence, and downstream access dependencies.

The practical distinction matters when identities are linked to approvals, entitlements, tickets, logs, or investigations. If a record is deleted too early, an organisation can lose the context needed to prove control decisions or reconstruct access history.

Where deactivation fits in the identity lifecycle

Deactivation sits between active access and full retirement. It is often triggered by offboarding, role change, policy breach, inactivity, or a security event that requires immediate access removal. The control is especially important where a user or service account may return later, or where the organisation needs to preserve the identity for retention or legal hold.

In well-run lifecycle processes, deactivation is paired with clear ownership, time-bound workflows, and a reliable source of truth so that access is stopped consistently across connected systems. If those workflows are fragmented, an account may appear disabled in one place while still retaining usable access elsewhere.

Security and operational effects of deactivation

Deactivation reduces the attack surface by cutting off interactive use of an identity, but it only helps if the surrounding access paths are also handled. Tokens, active sessions, delegated permissions, API keys, or linked service credentials may continue to work unless they are explicitly revoked or rotated as part of the same process.

That is why deactivation is both an access control action and a governance signal. It marks the point at which the identity should no longer be trusted for access, while preserving the record that shows when the trust relationship ended.

Risk and Threat Considerations

Deactivation becomes risky when organisations assume the account is harmless once it is marked inactive. In reality, stale sessions, cached tokens, long-lived keys, or unsynchronised downstream systems can leave a disabled identity partially usable, which creates a common post-deactivation exposure.

Failure mechanism: The identity is disabled in the authoritative system, but connected applications, federated sessions, or secret material are not revoked in step, so access persists through residual trust paths.

Impact: An attacker or former user may retain limited or full access after deactivation, and investigators may wrongly assume the access path is closed when it is not.

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 ManagementDeactivation often requires revoking or managing authenticators and related secret material.
AC-2 — Account ManagementDeactivation is an account lifecycle action that governs account status and access removal.
AU-11 — Audit Record RetentionDeactivation preserves records needed for audit, investigation, and retention.
Recommendation — Revoke or retire authenticators and related credentials when an identity is deactivated. Use account management procedures to disable access without destroying governance records. Retain audit records and identity history after access is disabled.
ISO/IEC 27001:2022A.5.16 — Identity managementDeactivation is part of managing identity states across their lifecycle.
A.5.11 — Return of assetsOffboarding and deactivation often occur together when access and assets must be recovered.
Recommendation — Define identity lifecycle states so disabled identities remain governed and traceable. Recover or invalidate access-related assets as part of deactivation and offboarding.

Practitioner Guidance

Why practitioners should care: Deactivation is only effective when it is treated as a lifecycle event across the whole access fabric, not as a checkbox in one directory or application. The operational question is whether the identity is truly unusable everywhere it matters, while still being preserved for evidence and governance.

What to watch for: Review whether deactivation also removes or invalidates sessions, tokens, API keys, and any linked access paths that survive account state changes. If the environment has multiple identity stores or shadow integrations, the disabling action should be verified end to end rather than assumed.

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