Manual deprovisioning is the process of removing a user's accounts, roles, entitlements, or system access by hand. It relies on administrators to disable accounts, revoke group membership, and close privileged access after a joiner-mover-leaver event. Because it depends on human action, gaps can leave orphaned accounts or lingering access.
How manual deprovisioning works
Manual deprovisioning is the hands-on end of the joiner-mover-leaver process. Administrators review the event, locate the user’s accounts across systems, and then disable or close access one system at a time. It is often used where automation is incomplete, where the application lacks a standard provisioning connector, or where exception handling still requires human review.
Because the work is performed case by case, the quality of the outcome depends on timely intake, accurate account discovery, and clear ownership. If any of those inputs are weak, access can remain active longer than intended even when the business believes the user has left.
Where manual deprovisioning is used
Manual deprovisioning is common in mixed environments, especially where older systems, niche SaaS tools, third-party portals, or privileged access workflows do not integrate cleanly with automated identity tooling. It can also appear as a fallback for contractors, urgent leaver events, or emergency access cleanup when the normal workflow is unavailable.
The practice is not limited to simple account disabling. In many environments it also includes removing group memberships, revoking application roles, retiring shared access paths, and closing privileged sessions that would otherwise let the former user continue to act inside the environment. Joiner-Mover-Leaver (JML) Guide covers the broader lifecycle controls that manual deprovisioning is meant to support.
Why it matters for access governance
Deprovisioning is one of the main points where access becomes provably current or stale. When it is manual, the organisation is relying on people to complete every revocation correctly, in order, and across every system that matters. That makes it a governance control as much as an operational one.
The practical challenge is that access is rarely stored in one place. A user may have direct accounts, inherited group access, tokens, API credentials, privileged roles, or application-specific entitlements that all need separate removal. If one layer is missed, the person may still have effective access even after the primary account is disabled. SCIM and Automated Provisioning Guide is a useful contrast because it shows where automation can reduce that dependency on manual follow-through.
What good manual offboarding should leave behind
The goal is not just to disable a login. A sound manual process should leave no active path for the departed user to authenticate, no lingering role memberships, and no privileged standing access that can be reused later. It should also create a reliable record that the revocation happened and who completed it.
Where access is tied to signing keys or other identity material, deprovisioning can also require credential rotation or retirement so that old access paths cannot be reused after the human account is gone. That is especially important when offboarding is late, incomplete, or performed after a sensitive event. Coupang Signing Key Breach illustrates how unrevoked credentials after offboarding can leave a material exposure behind.
Risk and Threat Considerations
Manual deprovisioning creates exposure because it depends on human completion, handoffs, and accurate inventory. The main failure mode is orphaned access, where an account, role, token, or privileged path survives the leaver event and remains usable after the person should no longer have any authority.
Failure mechanism: A leave event is processed in one system but not propagated everywhere else, or the administrator removes the obvious account but misses inherited entitlements, privileged access, or non-obvious service-linked credentials.
Impact: Former users, insiders, or attackers who obtain stale access can continue to reach systems, actions, or data that should already have been revoked, increasing the risk of misuse, lateral movement, and delayed incident detection.
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 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Manual deprovisioning is the revocation side of account lifecycle control. |
| IA-5 — Authenticator Management | Offboarding often requires revoking or rotating credentials used for access. | |
| AC-6 — Least Privilege | Lingering access after deprovisioning conflicts with least-privilege expectations. | |
| Recommendation — Use AC-2 to ensure accounts are disabled and removed promptly when access is no longer authorized. Apply IA-5 to retire, rotate, or invalidate authenticators and related credentials during offboarding. Use AC-6 to remove unnecessary standing access and prevent over-retained privileges after role changes. | ||
| CIS Controls v8 | 5 — Account Management | CIS Controls addresses lifecycle management of user accounts and access removal. |
| Recommendation — Use CIS-5 to control account lifecycle and promptly remove access when it is no longer needed. | ||
| ISO/IEC 27001:2022 | A.5.16 — Identity Management | Identity management covers assigning and removing access as part of lifecycle governance. |
| A.5.18 — Access Rights | Access rights management directly covers revocation when access should end. | |
| Recommendation — Apply A.5.16 to govern identity lifecycle changes, including timely deprovisioning. Use A.5.18 to review and revoke access rights when users change role or leave. | ||
Practitioner Guidance
What to watch for: Manual deprovisioning deserves the most attention where the environment has many disconnected systems, privileged exceptions, or recurring leaver backlogs. In those settings, the main question is not whether access was “disabled somewhere”, but whether every meaningful access path was actually removed.
Governance implication: Treat deprovisioning as an accountable closure step with an owner, a timestamp, and a completion check. If the process relies on humans, the control should be measured by confirmed revocation, not by the mere existence of a ticket or request.
Related resources from NHI Mgmt Group
- What breaks when AI app provisioning and deprovisioning are manual?
- Why do manual deprovisioning workflows create more risk than slow onboarding?
- Why do delayed deprovisioning and manual provisioning create more access risk than many organisations expect?
- When should organisations use automated deprovisioning versus manual access removal after a review decision?
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 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org