Offboarding: The 48 Hours That Decide Whether a Departure Becomes an Incident

Firms rehearse for hackers and improvise for departures. The pattern in insider cases is remarkably consistent: the damage was done either in the window between resignation and access removal, or through an access path nobody remembered existed. Both are controllable, and neither requires security tooling, just a procedure that runs in hours, not weeks.

Why the window matters more than the person

Most departing employees take nothing. The procedure exists because you cannot know in advance which departure is the exception, and because what departing people take is rarely dramatic. It is the client list exported “for reference,” the deal files forwarded to personal email “to finish something,” the still-synced Dropbox on a home machine. Innocent intent and a Reg S-P problem look identical in the logs. The control is the same either way: close the paths fast and verify what moved.

The 48-hour checklist

Before the last day (or within the hour, if the departure is hostile):

  1. Identity first. Disable the SSO/identity-provider account and the email credential. This severs everything federated in one move, which is also the argument for federating everything.
  2. The long tail. Custodian portal, CRM, portfolio system, file sharing, password manager, the firm’s social accounts, vendor portals where the person was the named contact. This list comes straight from your data inventory’s “who can touch it” column: offboarding is where that document earns its keep.
  3. Sessions and devices, not just passwords. Revoke active sessions and OAuth tokens; a changed password does not end a logged-in session. Wipe or recover firm data from mobile devices per the Technology Use Policy.
  4. Mail handling with a decision, not a default. Forwarding rules checked (both directions: attackers and departing employees both love auto-forwards), mailbox delegated to a supervisor, auto-reply set.

Within 48 hours:

  1. A look back. Review the final 30 days of activity for the obvious: bulk downloads, mass emails to personal addresses, unusual export volume. If audit logging is properly enabled and retained in your M365 tenant, this is a short review that converts “we think nothing left” into a documented conclusion. If it isn’t, the absence of usable logs is itself a finding; fix it before the next departure.
  2. The paper. Confirm the signed confidentiality agreement is in the file and provide a copy at exit. People behave differently when reminded, in writing, of what they signed.
  3. The record. A completed checklist, dated and signed, into the compliance file. This is the artifact your examiner, your carrier, and, if it ever comes to it, your lawyer will each want.

The supervised-person wrinkle

The departures that go worst are senior ones, because nobody wants to treat a partner’s exit like a security event. Write the procedure so it runs on role, not rank, and adopt it while everyone currently employed expects to stay. A procedure adopted the week of a contentious exit reads, accurately, as improvisation.

BrainTrust members: the Access Control and MFA Policy carries the deprovisioning requirements, and the confidentiality agreement set provides the paper for step six. The look-back in step five pairs with the M365 configuration guidance in the library’s security baseline.

The BrainTrust, free

This article is public. A free BrainTrust account opens every Insight, the 13 Sample Deliverables, the full Mock SEC Cyber Exam and the core compliance briefs. Name and email, no card.

Create Free Account →
Outside Testing

Want an outside test of your program? One-time engagements are available only to BrainTrust Premium members →