Call Join free
Tech Lab Miami
Tech Lab MiamiTECH LAB MIAMI
← Back to Automation & Operations

The Offboarding Gap: Revoking Access When Employees and Contractors Leave

Use this manually entered title as the article direction.
The Offboarding Gap: Revoking Access When Employees and Contractors Leave

Picture a familiar scene. Searched the web  Searched the web

The Offboarding Gap: Revoking Access When Employees and Contractors Leave

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.

A team gathered around a conference table in a naturally lit office, reviewing how access is removed when employees and contractors leave
Offboarding is a cross-team job. HR, operations, and whoever administers your tools all need to work from the same list.

Why access outlives the person

Most small and mid-sized companies don't have a single front door anymore. Access is scattered across many places:

  • SaaS sprawl: Each tool has its own user list, admin roles, and billing owner. Some were signed up with a personal email or a company card nobody tracks.
  • Contractors outside HR: Employees usually leave through payroll, which triggers at least some process. Freelancers and agencies often leave by simply not sending another invoice.
  • Shared credentials: A team password for social accounts, a Wi-Fi key, or a shared admin login doesn't disappear when one person loses their own account.
  • Non-human access: API keys, OAuth app connections, personal access tokens, and automation accounts keep working even after the person who created them has gone.

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.

What the frameworks actually expect

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 Controls: make revocation a process, not a favor

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: tie account management to people changes

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:

  • Disable system access within a time window the organization defines
  • Revoke the person's credentials and authenticators
  • Recover security-related property
  • Keep the organization's access to the information that person controlled

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: by the day they leave, contractors included

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.

Five decisions to make before the next departure

1. Disable first, delete later

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.

2. Put a clock on it

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.

3. Treat contractors as first-class users

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.

4. Centralize identity where you can

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.

5. Assign one owner

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.

The employee and contractor offboarding checklist

Adapt this list to your stack. Then keep it somewhere everyone involved in a departure can find it.

  1. Trigger: A resignation, termination, contract end, or role change opens an offboarding task with a named owner and a deadline.
  2. Identity provider and email: Disable the primary account, end active sessions, and remove MFA devices and app passwords.
  3. Apps outside SSO: Work through your inventory of tools that aren't behind SSO. Remove the user or downgrade them, and check whether they were a workspace admin or billing owner.
  4. Tokens and integrations: Revoke API keys, personal access tokens, and OAuth connections the person created. Move automations to a service or team account.
  5. Shared credentials: Rotate every shared password, Wi-Fi key, and vault secret the person could see. Moving shared logins into a password manager makes this step much easier.
  6. Data ownership: Transfer documents, drives, calendars, and mailboxes before any deletion. Set up mail forwarding if clients will keep writing to that address.
  7. Devices and physical access: Recover laptops, phones, security keys, badges, and keys. Wipe or reassign devices, and remove personal devices from mobile device management.
  8. External surfaces: Remove the person from domain registrars, DNS, hosting, ad accounts, social profiles, and payment processors.
  9. Verify: Have someone other than the person who did the work confirm the key accounts are disabled.
  10. Record it: Log what was revoked, when, and by whom. This record is your evidence if a customer, insurer, or auditor asks.

SaaS access management between departures

A checklist only works if you know what to check. Three habits keep the list honest:

  • Keep an account inventory. Track every tool, who has access, at what level, and who owns billing. This is the foundation that CIS Control 5 asks for.
  • Review access on a schedule. NIST AC-2 expects periodic account reviews. A quarterly pass through admin roles and dormant users will catch what the offboarding process missed.
  • Require MFA everywhere. CISA's small and medium business guidance on MFA recommends phishing-resistant methods where you can use them. It also advises requiring MFA for all remote and administrative access. MFA doesn't replace revocation, but it makes a forgotten password much less useful. CISA also points cloud-heavy businesses to its Secure Cloud Business Applications (SCuBA) resources for checking SaaS configurations.

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.

FAQs

What should I do if someone leaves unexpectedly?

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.

Should I delete a departed user's account right away?

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.

How do I revoke access for contractors who were never in our HR system?

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.

What tools help with offboarding?

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.

Close the gap before you need to

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.

← Back to Automation & Operations
Chat with us