Last updated
Most identity risk appears at transitions. A lifecycle event records a change in a person's state. Events are tracked at the identity level, not per account. There are four kinds.
Fires when an identity is created: the first user or account links to a new person. Means a new person exists in the graph and may need access provisioned.
Fires when an identity changes in a way that affects access: new department, role change, different group membership. Recorded at the identity level even when the change came from one account. Movers are where excess access accumulates, because new access is granted but old access is rarely removed.
Fires when all of an identity's login-capable users become disabled or staged for disablement.
Fires when a previously inactive identity becomes active again (a returning employee or contractor). Not a new joiner: the history is still there, and old access may still be attached and need review.
AOH Sync records the transitions, not just current state, for accountability. "This person left on this date and these accounts were still active" is only answerable if the leaving was an event, not an absence in the latest sync. Lifecycle events feed the audit trail and inform posture.
Last updated