Series 1, March 23, 2026

Drift Is What Happens When Identity Is Not Aligned

1 minute read, by Becky Sandberg

Drift is what happens when identity moves away from the intended state over time. It is not a failure of tools or users. Drift is the natural outcome of an operating model that is not aligned. It appears slowly, accumulates quietly, and becomes normal without anyone noticing.

Drift is the widening gap between how identity is designed to work and how it actually behaves. When drift grows, identity becomes unpredictable.

The Issue

Drift appears when lifecycle is inconsistent. Transfers do not update access. Terminations do not remove access. Contractors and vendors remain active after their work ends.

Drift appears when entitlements are unclear. Roles accumulate privileges. Groups expand. Permissions are added but never removed. Reviewers approve access without understanding it.

Drift also appears when legacy logic and outdated integrations create inconsistent behavior.

Drift is the predictable result of misalignment across governance, process, technology, and behavior.

How to Fix It

Treat drift as a system signal.

Identify where drift appears across lifecycle, entitlements, and integrations.

Align lifecycle with the truth of the organization.

Strengthen entitlement clarity so drift becomes visible and correctable.

Govern privileged access intentionally with time-bound elevation and monitoring.

Reduce exceptions by making the intended path work.

Address technical debt so identity behaves consistently.

Validate behavior through logs and analytics to see where drift is growing.

How to Measure It

  • Number of identities with access that does not match their role
  • Number of entitlements assigned outside approved workflows
  • Number of lifecycle events that do not propagate
  • Alignment between documented entitlements and observed usage
  • Number of audit findings related to inconsistent access

How to Audit It

Ask how drift is identified and monitored.

Ask how lifecycle changes propagate.

Ask how entitlements are documented and maintained.

Ask how privileged access is reviewed.

Ask how exceptions are analyzed.

Compare documented processes to observed behavior in logs and configurations.

Drift is not optional. It is the natural outcome of an operating model that is not aligned. When drift is governed intentionally, identity becomes predictable. When ignored, identity becomes unpredictable.

Put it to work. The free toolkit turns ideas like this into templates, a five-minute assessment, and a first move you can finish.

Open the free toolkit