Onboarding and offboarding are the identity lifecycle processes for granting and removing access as people join, change roles, or leave an organisation. They must be tightly governed because delays or manual steps can create overprovisioning, orphaned access, and operational friction. Effective lifecycle control reduces both risk and administrative burden.
What onboarding and offboarding control in identity lifecycle
Onboarding and offboarding are the control points where organisations create, change, and remove access as people join, move roles, or leave. The lifecycle is not just administrative, it determines whether access is granted on time, removed on time, and tied to an accountable business process rather than ad hoc requests.
In practice, the term sits within joiner-mover-leaver governance. The value is consistency: the same process that grants productive access at entry should also remove stale access at exit, and update entitlements when a role changes. When that does not happen, access drift starts to accumulate.
Why onboarding and offboarding matter for security
These processes directly shape the organisation’s attack surface. Overprovisioning, lingering accounts, and forgotten entitlements can leave former staff, contractors, or transferred employees with access they should no longer have. That can expose data, business systems, SaaS platforms, source code repositories, and secrets.
Offboarding is especially important because access removal must be complete across every place an identity can be used, not just the main directory. A useful reference point is the Employee Offboarding Security Guide, which focuses on practical leaver controls such as session revocation, SaaS cleanup, and access parity. On the onboarding side, the Joiner-Mover-Leaver Guide helps frame onboarding as part of a broader lifecycle, not a one-time account creation task.
Lifecycle control also matters for non-employee populations such as contractors and service-linked access paths. Where access is not removed cleanly, orphaned permissions and standing privilege become easier to abuse and harder to audit.
What good lifecycle control looks like
Effective onboarding starts from an authoritative trigger, usually HR or another trusted source of record, and translates that change into the right entitlements with minimal manual intervention. Access should be role-based where possible, with exceptions clearly owned and reviewed. That reduces both delays for new starters and accidental privilege creep over time.
Offboarding should be treated as a completion process, not a single ticket closure. It should remove application access, terminate sessions where needed, revoke tokens or keys, and confirm that shared systems, admin panels, and special-purpose tools no longer recognise the departing user.
The strongest programmes also use the lifecycle to force periodic cleanup. A mover event is often where old-role access should be removed, because role changes frequently leave behind the largest collection of unnecessary entitlements.
Operational signals and common failure modes
Lifecycle problems usually show up as delays, exceptions, and mismatches between systems. Common signals include leavers who still have active sessions, accounts that remain enabled after departure, requests handled outside the standard workflow, and mismatched access between the directory and downstream applications.
Another common failure mode is fragmented ownership. If no one owns the full path from hire date to termination date, access removal becomes dependent on individuals noticing the right event at the right time. That is where offboarding drift develops, especially in environments with many SaaS services, developer tools, and cloud consoles.
Monitoring should therefore focus on completeness, not just ticket volume. A closed request does not necessarily mean the identity has been fully deprovisioned everywhere it mattered.
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 | PS-4 — Personnel Termination | Defines termination and access removal as a control outcome for departing users. |
| AC-2 — Account Management | Covers account provisioning, modification, disabling and removal across the identity lifecycle. | |
| Recommendation — Use PS-4 to ensure departing personnel lose access promptly and completely across assigned systems. Apply AC-2 to automate account lifecycle actions and verify timely deprovisioning. | ||
| ISO/IEC 27001:2022 | A.5.16 — Identity management | Requires managed identities across joiner, mover and leaver lifecycle events. |
| A.5.18 — Access rights | Directly governs granting, review and removal of access rights during lifecycle changes. | |
| Recommendation — Implement identity management procedures that keep onboarding and offboarding consistent and auditable. Review and revoke access rights promptly when roles change or employment ends. | ||
| CIS Controls v8 | CIS-5 — Account Management | Covers lifecycle control for accounts, including provisioning and removal of access. |
| Recommendation — Standardise account lifecycle handling so joiners, movers and leavers are processed consistently. | ||
Related resources from NHI Mgmt Group
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 October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org