
True offboarding requires more than just unchecking an active user box. While disabling an account blocks new sign-ins, existing sessions and personal access tokens can remain valid until they expire or are manually revoked. Meeting frameworks like the NIST personnel termination controls means actively hunting down overlooked local accounts, rotating shared credentials, and terminating active sessions across all platforms. The following guide details the critical access management steps standard offboarding tends to skip.
Why Does Former Employee Access Linger After Offboarding?
Former employee access lingers because offboarding usually focuses on the main account, while access also lives in sessions, tokens, shared passwords and connected apps. Each of these can keep working after the account is disabled, which is why a separate verification step matters.
A 2026 federal case shows what’s at stake. According to the U.S. Attorney’s Office for the Southern District of Iowa, a school district IT worker downloaded more than 300 usernames and passwords before he was fired in 2023. He used them for over a year and a half to disrupt district systems, and one series of attacks suspended classes for hours.
What Should Offboarding Remove?
Offboarding should remove system access, revoke every credential tied to the person, and recover company property, while keeping your own access to the systems they managed. NIST’s personnel termination control lists these steps, so it makes a practical baseline to check your process against.
The NIST personnel termination control (PS-4 in SP 800-53) asks organizations to disable access within a set time, revoke authenticators and credentials, hold exit interviews, and retrieve security-related property. It also says to keep access to systems the person controlled. If a departing admin held the only login, disabling their account can lock you out too.
How to Find Overlooked Accounts
Find overlooked accounts by comparing your list of departures against every system that keeps its own user list, not just your main identity provider. Apps with separate logins, local admin accounts, and service accounts are easy to miss, because disabling the central account doesn’t remove them.
Microsoft recommends removing users from each application directly, with a manual process for apps that can’t do it automatically. List the systems each role used, then confirm the account is gone from every one.
How to Confirm Active Sessions Are Closed
Confirm sessions are closed by revoking them on purpose, not just by disabling the account. Tokens that were already issued can stay valid until they expire, and some apps run their own sessions, so each one may need a separate sign-out.
In Microsoft Entra ID, access tokens last one hour by default, according to Microsoft’s revocation guide. Entra also can’t revoke a session token that an application issued itself. Google’s offboarding guidance likewise includes resetting the user’s sign-in cookies. Once you’ve revoked sessions, review sign-in logs for any later activity on the account.
How to Track Down API and Personal Access Tokens
Track down tokens by reviewing every platform where staff can create them, such as code repositories, cloud consoles, and automation tools. A token can keep working after its owner leaves, so revoke any the former employee created and replace the ones your systems still need.
GitHub is a good example. Organization owners can view and revoke fine-grained personal access tokens, but classic tokens don’t appear in that view and can reach organization resources until they expire, unless the organization restricts them. Before revoking a token, check which scripts depend on it.
Why Shared Credentials Must Be Rotated
Shared credentials must be rotated because disabling someone’s own account does nothing to the passwords they already know. Shared admin logins, vendor portals, Wi-Fi keys and service account passwords all stay usable until someone changes them, whether the person left on good terms or not.
The Iowa case involved a list of more than 300 district usernames and passwords. Keep a record of each shared credential and who knows it, so you can rotate the right ones the day someone leaves.
How to Review Third-Party App Access
Review third-party app access by listing every app the former employee authorized with their work account and revoking the grants that remain. These connections let outside apps reach company data on the user’s behalf, and some survive a password change.
Google notes that changing a user’s password revokes OAuth tokens for certain products only, so admins should review all authorized access and revoke the rest. Its checklist also covers app-specific passwords, security keys, and recovery details. If you can only do a few checks today, start with shared credentials and admin accounts.
Protect your company data from lingering access vulnerabilities. Contact our IT security team today to audit your offboarding procedures, secure your shared credentials, and implement robust identity and access management controls.
