Skip to main content
Promotional banner for the pentest readiness checklist
Transfer or Leaver: Pick Your Access Revocation TriggerIdentity Lifecycle
5 min readFor Identity Governance Administrators

Transfer or Leaver: Pick Your Access Revocation Trigger

Someone moves from finance operations to treasury. The new manager approves the new access in a day. The old access stays. Six months later, a Certification Campaign asks the reviewer one question: "Do you still need this?" Nothing on screen says whether the entitlement was touched last week or last year. The reviewer clicks yes.

You're an Identity Governance Administrator, and you own the fix. The decision in front of you is which revocation trigger to build first, because you probably can't build all three at once.

The Decision You Are Facing

Granting access has an owner and a deadline. Removal has neither. Nobody opens a ticket when a permission stops being useful, and the cost of keeping it is invisible and deferred. Meanwhile, a wrongly removed permission produces an angry support ticket the same day.

NIST SP 800-53 Rev. 5 addresses this directly. AC-2 (Account Management) calls for account reviews and for handling transfers and terminations. AC-6 (Least Privilege) requires granting only the privileges a role needs. A transfer is a control event under both, not a courtesy.

So the question is: do you anchor revocation on HR events, on permission expiry, or on review-time visibility? Each path closes a different gap.

Key Factors That Affect Your Choice

Answer these before you pick a path.

Is your HR system of record trustworthy and reachable? If role-change events are reliable and your IGA platform can consume them, Path A is open to you.

Do you know who owns each permission? If direct grants, groups, and folder access have no named owner, nothing downstream works.

Can you pull last-used data? Your identity provider and application logs may expose last login and last activity timestamps. Not every application keeps usage logs, so check your most sensitive systems first.

Where does your exposure sit today? Leavers trigger offboarding. Transfers trigger nothing. If your offboarding checklist covers accounts but not the permissions and certificates people accumulated over years, you have a gap on both sides. Role-Based Access Control helps, but when a user's role updates, the direct access, groups, and folders acquired along the way often stay put.

The stakes are about blast radius. The 2026 Verizon Data Breach Investigations Report put vulnerability exploitation at 31% of breaches and credential abuse at 13%. That report doesn't measure stale permissions. But once an attacker holds a compromised account, the damage depends on how much that account can reach. Accumulated entitlements set that ceiling.

Path A: Treat Every Role Change as a Deletion Event

Choose this if: your HR system produces reliable transfer events, and transfers are your largest unreviewed population.

How it works: When HR records a role change, your IGA platform generates a task for both the outgoing and incoming manager. One question: what will this person no longer need? Show them the full access list. Give them ten minutes. Every entitlement acquired during the person's tenure needs an owner, so this task also surfaces orphans.

Requirements driving it: AC-2 requires handling transfers, not just terminations. This path is the most direct way to show an assessor you do.

If your HR integration is weak, then fix that first, or run the same task manually off a monthly transfer report. A manual version still beats nothing. If you only implement one path, make it this one.

Watch for: managers who rubber-stamp. Pair the task with last-used data (Path C) so the question isn't a blind guess.

Path B: Give Every Permission an Owner and an Expiry Date

Choose this if: your risk concentrates in project folders, special permissions, and production system access that outlive their purpose regardless of who holds them.

How it works: Each such permission carries a named owner (a person, not a mailbox) and an expiration date. Use the project end date, or default to three months after issuance unless the owner renews. Renewal should be one click. If the owner is unavailable, renewal routes to their manager so it doesn't fall through.

The default matters more than the mechanism. If doing nothing means the permission survives, inertia wins. Flip it so doing nothing means the permission lapses. Don't make renewal the default action.

Requirements driving it: AC-6 least privilege is hard to evidence without time-bounded grants. Expiry turns "we review periodically" into "access ends unless someone argues for it."

If your owners are unknown, then this path stalls. Model accounts, owners, and the applications they touch as a graph so one query shows what a departing or transferring person owns and what depends on them.

Watch for: break-glass and quarterly-close accounts. They're legitimately rarely used. Assign an owner and a note rather than letting expiry kill them.

Path C: Show Last-Used Data in Every Certification

Choose this if: you already run Certification Campaigns, but reviewers approve out of habit.

How it works: Pull last login and last activity timestamps from your identity provider and application logs and display them beside each entitlement. Sort so the least-used access sits at the top, pre-selected for removal. Make the reviewer justify keeping it. A line reading "not used in seven months" changes behavior, and reviewers will confirm removal readily when they can see it.

Keep attestation, Vault Rotation, and retirement in one workflow where you can. When confirmation lives in one tool and action lives in another, people confirm and skip the action.

If a system lacks usage logs, then flag those entitlements for owner justification instead of silently treating them as active.

Summary Matrix

Factor Path A: HR Event Trigger Path B: Owner and Expiry Path C: Last-Used Visibility
Best for Transfers Project and privileged grants Existing review programs
Prerequisite Reliable HR events Named owners Usage data from IdP or app logs
Primary control AC-2 transfers and terminations AC-6 least privilege AC-2 account review
Main risk Manager rubber-stamping Legitimate rare-use accounts Apps without usage logs
Effort Medium Medium to high Low to medium

Where to Start This Quarter

If you can't decide, skip the matrix and run a pilot. Pick one system holding sensitive data. Run a last-used report. Filter to users who changed roles in the past year, since nobody has reviewed their access since the move. Send the system owner everyone who hasn't touched it in six months and ask: do they still need this?

The results will make the case for the other two paths better than any framework document will.

promotional banner for evidence for every CC6 control checklist

You Might Also Like