Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Identity lifecycle management automates what happens to an account when someone joins, changes role, or leaves, driving access from an authoritative source rather than from tickets.

What Is Identity Lifecycle Management?
Three events define an identity: the person arrives, the person changes role, the person leaves. Identity lifecycle management is the discipline of making those three events drive access automatically, from a source of truth, instead of relying on someone remembering to raise a ticket.
The shorthand is joiner-mover-leaver, and of the three the mover is the one that quietly wrecks an access model.
Automation needs something to automate from. For employees that is normally the HR system—Workday, SAP SuccessFactors, iTrent—because it holds start dates, end dates, departments, and line manager relationships, and because HR has a business reason to keep them accurate.
The gaps are everyone else. Contractors engaged through a procurement process, agency staff, partner organisations, students on placement, and non-human identities all sit outside HR, and in most organisations they are managed by whoever set them up. Each population needs a nominated authoritative source and a nominated owner before automation can work; without that, lifecycle management covers 70% of the estate and the remaining 30% is where the stale accounts live.
A record appears in HR with a future start date. The identity platform creates the account, assigns birthright access based on department and job code—email, intranet, the standard productivity suite—and triggers credential enrolment. Role-specific access beyond birthright should be requested through an access package rather than copied from a colleague, which is the mechanism by which privilege creep spreads.
Two details repay attention. Pre-staging the account before the start date means day one works, but the account should not be usable until the start date arrives. And initial credential delivery is a genuine attack surface: an onboarding email containing a temporary password sent to a personal address is a route into the organisation that costs an attacker nothing.
This is where most programmes are weakest. When someone transfers from finance to procurement, the new access is granted promptly, because the person needs it to do their job and will chase it. The old access is not removed, because nobody is inconvenienced by its presence.
Repeat that over several internal moves and you have created, accidentally, the profile of an insider risk: a long-serving employee with access spanning functions that were deliberately separated. Segregation of duties controls that look sound on paper are defeated entirely, because the person who raises a purchase order can also approve the payment.
The fix is to model access as attached to the position rather than the person. When the position attribute changes, grants tied to the old position are revoked on a defined schedule. Build in a transition window—two to four weeks is typical—so handovers do not break, and report on every grant that survives it. Pair this with a targeted access review triggered by the move itself, rather than waiting for the annual campaign.
Speed matters, and the sequence matters more than people expect. Disable rather than delete first, so that evidence and mailbox content remain available. Then revoke active sessions and refresh tokens, because disabling an account does not invalidate tokens already issued—an attacker or a departing employee with a live session can continue for hours or days otherwise. Continuous access evaluation shortens that window substantially in Microsoft estates.
Then work outward: remove from groups, deprovision from downstream applications, transfer data ownership, retrieve devices, and revoke certificates and password vault entries. Shared credentials the leaver knew must be rotated, which is the strongest practical argument for not having shared credentials.
For involuntary departures, run deprovisioning before or during the conversation rather than afterwards. And apply the same rigour to contractor end dates, which are the most common source of orphaned accounts because no HR process marks them.
Downstream provisioning is best handled by SCIM where the application supports it, since it gives you a standard interface for create, update, and deactivate rather than a bespoke connector per system. Reconciliation matters as much as provisioning: run a regular comparison between accounts in each application and identities in the source of truth, and investigate anything present in one and not the other. That report is where orphaned accounts, local accounts created outside the process, and failed deprovisioning surface.
For UK organisations the evidence requirement is explicit. ISO 27001 Annex A 5.18 expects provisioning and removal of access rights to follow a documented policy, and Cyber Essentials asks directly about the process for removing access when someone leaves. Automated lifecycle management turns that from an assertion into a log.
At Privia Security, we review joiner-mover-leaver processes and their downstream coverage in our infrastructure and architecture review services.
Because nothing fails visibly when it is skipped. New access gets granted quickly since the person needs it to work, while old access stays because its presence inconveniences nobody. Over several internal moves this accumulates into cross-functional access that defeats segregation of duties. Tying grants to the position rather than the person, with a defined transition window, is the structural fix.
Account disablement and session revocation should happen on the last working day, and immediately for involuntary departures. Disabling alone is not sufficient, because access tokens and refresh tokens issued earlier remain valid until they expire. Revoke sessions explicitly, rotate any shared credentials the person knew, and verify removal from downstream applications rather than assuming it propagated.
Whatever system records the engagement and its end date, usually a procurement, vendor management, or contractor onboarding platform. The important thing is that one system owns the record and that every contractor identity has a named internal sponsor and a mandatory end date. Contractors managed only by the team that hired them are the most common source of orphaned accounts.
Reconciliation compares the accounts that actually exist in each application against the identities in your source of truth, and reports anything that appears in one but not the other. It catches accounts created outside the process, deprovisioning that failed silently, and local accounts in applications that do not support central management. Without it, lifecycle automation can fail for months unnoticed.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.