Picture a familiar scene.
Searched the web
Searched the web
Picture a familiar scene. The freelancer who built your automations wrapped up three months ago. Everyone was happy, and the final invoice was paid. Her login to your CRM still works, though, and so does the API key she connected to your email platform. She also still has editor access to the shared drive with your pricing models. Nobody did anything wrong. Nobody did anything at all. That is the offboarding gap. Access rarely leaks because of a dramatic breach. It leaks because nobody owns the moment when a person stops working with you. Their accounts keep living after they're gone. For founders, operators, and service businesses running on dozens of SaaS tools, that gap grows every time someone leaves. This guide skips the generic advice. It covers what the major security frameworks actually expect, the decisions you need to make, and an employee offboarding checklist you can put to work this week. Most small and mid-sized companies don't have a single front door anymore. Access is scattered across many places: The Center for Internet Security names this pattern directly. Its guidance for CIS Control 6 (Access Control Management) notes that many organizations handle departing employees consistently, but are much less consistent with contractors. It says contractors belong in the standard de-provisioning process. You don't need to adopt a full compliance program to borrow from the best-known frameworks. On offboarding, they agree to a degree that's almost boring. CIS Safeguard 6.2 asks organizations to set up and follow a revocation process, automated where possible. That process should disable accounts as soon as someone is terminated, loses rights, or changes roles. It's part of Implementation Group 1, the baseline CIS considers appropriate for every organization (CIS Controls Assessment Specification). The companion CIS Control 5 (Account Management) covers the groundwork. That means keeping an inventory of accounts and disabling dormant ones so forgotten logins don't pile up. NIST SP 800-53 Rev. 5 (official publication) covers offboarding from two directions. Control PS-4 (Personnel Termination) calls for several actions when employment ends: PS-7 extends personnel security expectations to external providers. Control AC-2 (Account Management) asks that account processes line up with termination and transfer processes. It also calls for changing shared or group credentials when a member leaves, and for reviewing accounts on a regular schedule. CISA's original Cybersecurity Performance Goals described a defined administrative process for departing employees. Applied by their last day, it would recover badges and tokens and disable all accounts. The updated CPG 2.0 widens that goal from "employees" to departing "staff," explicitly including contractors and vendors. It also flags that attackers can use former staff's inactive accounts to avoid being noticed. Deleting accounts right away feels decisive, but it can destroy evidence and data you still need. CIS notes that disabling may be necessary to keep audit trails intact. NIST PS-4 likewise expects you to keep access to the information the departing person controlled. A practical default is to disable on day one, transfer file and mailbox ownership, and delete after a set retention period. NIST leaves the time window up to you, which means you have to pick one. CISA's performance goal points to the day of departure. For involuntary exits, NIST's guidance on PS-4 suggests that in some cases organizations may disable accounts before telling the person. Write your target down, such as "by end of last day" or "within one hour of a for-cause termination." A target nobody wrote down is one nobody meets. If contractors don't appear in your HR system, they need another trigger. That could be the contract end date, the final invoice, or a project close-out step. Whatever you choose, it should start the same revocation checklist employees get. When you set up contractor access, give it an expiration date from the start. NIST's AC-2 enhancements describe automatically disabling temporary accounts after a defined period. Most identity providers and many SaaS admin panels support some version of this. Every app connected to single sign-on is one less account to chase. Centralized access control is a CIS Implementation Group 2 safeguard (6.7), so it isn't a day-one requirement. For a company with more than a handful of SaaS tools, though, it's usually the biggest step up. For tools that can't connect to SSO, keep them on a short, named list. Those are the ones your checklist has to cover by hand. CISA's cyber guidance for small businesses recommends naming a Security Program Manager. That person doesn't have to be a security expert or even an IT professional. Their job is to make sure the program actually runs. Offboarding is a good first responsibility for that role. In a small team, the owner might be an operations lead rather than an engineer, and that's fine. Adapt this list to your stack. Then keep it somewhere everyone involved in a departure can find it. A checklist only works if you know what to check. Three habits keep the list honest: If you're starting from scratch, CISA's Cyber Essentials is a reasonable place to begin. It's written for leaders of small organizations rather than security specialists. Start with the systems that touch money, customer data, and your domain. Disable the identity provider account and email, end sessions, and remove admin rights in payment, hosting, and DNS tools. Then work through the rest of the checklist. For a contentious exit, NIST's PS-4 guidance supports disabling access before the person is notified. Usually not. Disable it first, transfer ownership of their data, and delete it after a retention period you've defined. CIS notes that disabling rather than deleting can preserve audit trails. Use the contract end date or final invoice as the trigger, and run the same checklist you use for employees. Going forward, give contractor accounts an expiration date when you create them. Prefer guest or limited roles over full seats. An identity provider with single sign-on handles the most ground, especially if it can deprovision users in connected apps automatically. A password manager makes rotating shared credentials practical. A simple tracker or ticket template keeps the record. For any tool that can't be automated, keep it on the manual checklist and review it every quarter. Offboarding usually only gets attention after something goes wrong. The fix isn't expensive. It takes an owner, a deadline, an inventory, and a checklist that includes contractors and API keys, not just employees and laptops. Pick a recent departure and walk it through the list above. Whatever is still active is your starting point.The Offboarding Gap: Revoking Access When Employees and Contractors Leave

Why access outlives the person
What the frameworks actually expect
CIS Controls: make revocation a process, not a favor
NIST: tie account management to people changes
CISA: by the day they leave, contractors included
Five decisions to make before the next departure
1. Disable first, delete later
2. Put a clock on it
3. Treat contractors as first-class users
4. Centralize identity where you can
5. Assign one owner
The employee and contractor offboarding checklist
SaaS access management between departures
FAQs
What should I do if someone leaves unexpectedly?
Should I delete a departed user's account right away?
How do I revoke access for contractors who were never in our HR system?
What tools help with offboarding?
Close the gap before you need to
