Nobody Fired the Robot: The Credentials Your Offboarding Missed
Photo by Photo by Tyler on Unsplash on Unsplash
There is a specific moment in every offboarding that feels like closure. The laptop goes back to IT. The badge stops working. The identity provider flips the account to disabled and the SaaS seat gets reassigned. Someone marks the checklist complete and the manager sends a nice note to the team.
Somewhere in that same window, a personal access token created eighteen months ago by the person walking out the door is still valid, scoped to read an entire CRM, and attached to a cron job that has been failing silently since spring.
The Laptop Wiped. The Token Didn't.
The deprecation of a human account is a solved problem at most companies. The deprecation of everything that human manufactured is not. Employees leave behind a surprisingly long tail of machine identities: API keys in a shared vault, OAuth grants to third-party apps, service accounts for CI jobs, webhook endpoints pointed at personal projects, database users, SSH keys copied into a build script, and integrations created under their account because the platform made that the easy path.
None of those are tied to a person in a way your IAM system recognizes. They are tied to a name in a description field, if you are lucky, and to nothing at all if you are not.
How One Departure Becomes Eleven Live Keys
Trace a typical case. A backend engineer sets up a service account to run nightly syncs between the warehouse and a marketing tool. It is fine. Two years later she moves to a different team and the sync is quietly owned by whoever picks up the ticket. Then she leaves the company. Her human account dies. The service account, which never had a human owner, keeps running with the permissions it had on day one — which include write access to tables that have since grown to include customer PII.
Multiply that by every tool that ever needed a quick integration. Multiply again by the contractor who onboarded through a different path and never appeared in the standard checklist. The inventory grows in the dark, and it never shrinks on its own, because nothing about a working credential prompts anyone to look at it.
Why Nobody Notices Until It Matters
Orphaned credentials are invisible by design. There is no alert for a key that is used exactly as expected. The logs look normal because the behavior is normal — it is the ownership that is wrong. You find out during an incident, a penetration test, or the worst version of both: a former employee's token showing up in a breach dump alongside a list of systems it can reach.
The risk is not only malice. A stale token in a forgotten repo, a service account with a password that has not rotated since it was created, an integration pointed at a domain that expired and got re-registered by someone else — these are boring failures that produce very unboring afternoons.
An Offboarding Audit You Can Actually Run
You do not need a six-month program. You need one focused pass, done properly, then a habit. Start with the accounts of everyone who left in the past twelve months. That cohort is where the risk is concentrated and where the evidence is easiest to gather.
Inventory. Pull every credential associated with those identities from your secrets manager, cloud providers, CI system, and the admin consoles of your top SaaS tools. Search for their email, their username, and their display name in descriptions and owner fields. Expect to be surprised by the volume.
Classify. Sort each one into three buckets: still needed, not needed, and unknown. Unknown is the biggest bucket and the most important one, because unknown means no one can tell you what breaks if you revoke it.
Rotate or revoke. For anything still needed, rotate the secret to a new one held by a named owner. For anything not needed, revoke and delete. For unknown, set a date, watch the logs, and kill it — most of them will turn out to be doing nothing at all.
Assign ownership. Every machine identity gets a human owner of record and a team. Not a shared mailbox. A person, in the same directory your access reviews already read from.
Enforce least privilege. While you are in there, look at scope. A token that can read and write everything because scoping it took an extra ten minutes two years ago is a gift to whoever finds it.
Make the Next Departure Boring
The audit cleans up history. The habit prevents a sequel. Add three things to the offboarding checklist and mean them: a search for credentials created by the departing person, a transfer of ownership on any service account they touched, and a revocation sweep that runs two weeks after the last day rather than on it. That delay matters, because integrations break quietly and you want a window where someone still remembers the context.
Also worth doing: require an owner field at creation time for any new service account or API key, and refuse to issue credentials without one. It is a small friction that makes every future audit cheap.
The Part Everyone Skips
Offboarding is usually treated as a human resources process with a security attachment. That framing is backwards. The human part is easy and mostly automated. The machine part is where the residue lives, and it is where a company's actual posture gets decided — long after the farewell message has scrolled off the channel.