Offboarding that actually ends access.
When someone leaves, their access should leave with them: laptops, servers, cloud, code and every key they registered. Here’s a checklist you can use today, how Bastyx does it in one step, and exactly what that step covers.
Why offboarding leaves access behind
Most teams disable the identity provider account and consider the job done. But at a technical company, much of the access that matters never went through the identity provider in the first place.
- SSH keys live on servers, not in your directory. Suspending an account doesn’t remove them.
- Tokens outlive accounts. Cloud access keys and personal access tokens keep working until someone revokes them explicitly.
- Shared secrets can’t be un-shared. Anything a person could read in a shared vault has to be rotated.
- Nobody has the full list. Access was granted by different people in different tools over months or years.
The access offboarding checklist
Work through every area, even if you think it doesn’t apply. The access that gets missed is usually the access nobody remembered granting.
Identity and sign-in
- Suspend the identity provider account and end active sessions
- Remove the person from groups that grant access elsewhere
- Revoke registered passkeys and security keys
Devices
- Disable sign-in on every laptop and workstation they used
- Recover company hardware, or lock and wipe it remotely
- Remove local admin accounts created for them
Servers and SSH
- Remove their public keys from every authorized_keys file
- Rotate any shared account keys they had access to
- Check jump hosts and bastions separately
Cloud
- Delete or disable IAM users and their access keys
- Remove role assignments and federated access
- Review resources they created that grant access, such as keys and service accounts
Code and CI
- Remove them from the source-control organization
- Revoke personal access tokens and deploy keys they created
- Check CI secrets and runners they configured
Shared secrets
- Rotate passwords in shared vaults they could read
- Rotate API keys and database credentials they handled
- Update break-glass credentials if they knew them
Records
- Record what was revoked, when and by whom
- Keep the record where your next security review can find it
One action instead of a checklist
With Bastyx, the access on that checklist is granted through one identity in the first place. That makes revoking it a single step:
Offboard the person
Now, or scheduled for their last day.
Connected paths are revoked
Laptop unlock, SSH sessions, app sign-ins, registered keys and owned AI agents.
The record is kept
What was removed, when and by whom, ready for review.
What revocation covers, and when
“Immediately” means as soon as you confirm the offboarding, or at the time you scheduled it. Anything not connected to Bastyx is listed as a manual step rather than assumed.
| Access path | Takes effect | Details |
|---|---|---|
| SSH | Immediately | New connections are refused, and the bastyx agent closes sessions that are already open. |
| Laptop login | Next unlock | Every unlock is checked with Bastyx, so the next one is refused. A laptop that’s offline can’t be unlocked. |
| Security keys and passkeys | Immediately | Deregistered, so they no longer work with anything Bastyx protects. |
| Apps behind the access proxy | Immediately | Every request passes through the proxy, so the next one is refused. |
| Vaulted legacy-app passwords | Immediately | Bastyx stops filling them in. The person never saw the password, so there’s nothing for them to reuse. |
| SAML and OIDC apps | New sign-ins immediately | A session already open in the app lasts until the app’s own session timeout. Keep that short for sensitive apps. |
| AI agents they own | Immediately | Paused, so they can’t keep acting on the person’s behalf. |
| Anything not connected to Bastyx | Not covered | Local accounts, personal tokens and apps outside Bastyx are untouched. The access inventory lists them as manual steps. |
If Bastyx is unreachable
During an outage, new SSH and app sign-ins wait, and nothing already open is cut off.
- Laptops
- An online laptop that can’t reach Bastyx unlocks with a cached credential. An offline laptop can’t be unlocked.
- Open sessions
- SSH and app sessions that are already open keep running.
- New SSH and app sign-ins
- Wait until Bastyx is reachable again.
- Emergencies
- Each protected resource can keep a break-glass account for use during an outage.
Offboarding questions
How quickly should access be revoked?
For a planned departure, at the end of the last working day. For an involuntary departure, before or during the conversation. The goal is that access ends when employment does, not days later.
Can we schedule an offboarding in advance?
Yes. Set a date and time, and Bastyx revokes everything then, so nobody has to remember at 5pm on a Friday.
What about access Bastyx doesn’t control?
Bastyx revokes what it manages. The access inventory shows what’s covered, so any remaining manual steps are explicit rather than forgotten.
What happens to SSH sessions that are already open?
They’re closed. When revocation is confirmed, new connections are refused and the bastyx agent on each server ends the person’s open sessions.
What if their laptop is offline?
It can’t be unlocked. Every unlock is checked with Bastyx, so an offline laptop stays locked, and the next unlock after revocation is refused.
Does offboarding delete the person’s audit history?
No. Their event history stays intact after offboarding, because that history is exactly what you need if questions come up later.
Revoke once. Every connected system follows.
Your developer left Friday. Their access should end Friday. Book a demo and see it happen in one step.