Skip to content
ENExplore Calculators

Identity Lifecycle Calculator

Score identity lifecycle hygiene from deprovisioning delay, orphan accounts and dormant identities across your estate.

About Identity Lifecycle Calculator

Deprovisioning delay converts a leaver rate into a standing population of orphan accounts, in the same way arrival rate times service time gives queue length. The score penalises that population, the dormant tail and the delay itself, because a long delay is a risk even in a month with few leavers. Orphan and dormant accounts are the credentials nobody will notice being used — no owner to report a phish, no manager to spot the login, and frequently no MFA either.

Formulas

Identity Lifecycle

orphan identities live at any moment = leavers per day × average deprovisioning delay, and each drags its application accounts with it.

leavers per day
Monthly leavers ÷ 30
deprovisioning delay
Days between the last working day and the account actually being disabled
orphan account
A live account with no active owner

Annual exposure

exposure = leavers per year × delay, expressed in account-days of unowned live access.

account-days
One live orphan account for one day — the unit auditors and attackers both care about

Worked example

With the default values below, Identity Lifecycle Calculator returns Lifecycle Hygiene Score of 84. Change any input above and every figure here is recalculated in your browser.

Inputs used

Employeesaccepts 0–2,000,000 people
12,000 people
Contractors and third partiesaccepts 0–500,000 people
1,800 people
Leavers per monthaccepts 0–100,000 people
180 people
Average delay from exit to disableaccepts 0–180 days
6 days
Application accounts per identityaccepts 1–500 accounts
14 accounts
Accounts unused past the dormancy thresholdaccepts 0–1,000,000 accounts
420 accounts

Results

Lifecycle Hygiene Score
84 / 100
Rating
B — Good
Orphan Identities Live Right Now
36
Orphan Application Accounts
504
Exposure per Year
12,960 account-days
Orphan Rate
0.26%
Dormant Account Rate
3.04%

Step by step

  1. 1Values used
  2. 2Identity Lifecycle
  3. 3Annual exposure
  4. 4Lifecycle Hygiene Score= 84 / 100
  5. 5Rating= B — Good
  6. 6Orphan Identities Live Right Now= 36
  7. 7Orphan Application Accounts= 504
  8. 8Exposure per Year= 12,960 account-days
  9. 9Orphan Rate= 0.26

Assumptions and limits

  • The result is derived only from the 6 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How is Identity Lifecycle calculated?

orphan identities live at any moment = leavers per day × average deprovisioning delay, and each drags its application accounts with it. Deprovisioning delay converts a leaver rate into a standing population of orphan accounts, in the same way arrival rate times service time gives queue length. The score penalises that population, the dormant tail and the delay itself, because a long delay is a risk even in a month with few leavers.

Why does Identity Lifecycle matter?

Orphan and dormant accounts are the credentials nobody will notice being used — no owner to report a phish, no manager to spot the login, and frequently no MFA either.

What values do I need to enter?

This calculator takes 6 inputs: Employees, Contractors and third parties, Leavers per month, Average delay from exit to disable, Application accounts per identity, Accounts unused past the dormancy threshold. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

What is a realistic deprovisioning target?

Same-day disable for employees and within the hour for involuntary terminations, driven by HR being the authoritative source rather than by a ticket. Contractors need an explicit end date on the account at creation, since nobody files a leaver ticket for a contract that simply lapses.

How is a dormant account different from an orphan?

An orphan has no valid owner at all; a dormant account has an owner who has stopped using it. Both are unmonitored attack surface, but dormancy is also a signal for right-sizing — an account unused for 90 days usually indicates access that was never needed.

Identity Lifecycle Calculator | Calcrivo