Author: Ami DePierro | Co-Founder, 2 Dog Digital
Ami DePierro is Co-Founder of 2 Dog Digital and a former U.S. Marine Intelligence Analyst who brings analytical precision to cybersecurity strategy for small and mid-sized businesses across the Raleigh/Triangle area. Digit is the voice. Ami is the author.
Table of Contents
The Breach Nobody Planned For
A security incident does not always start with some hacker in a dark room doing things nobody understands.
Sometimes Bob quit four months ago and Bob’s account still works.
His Microsoft 365 account was never disabled. His phone may still have an authenticated session. He knew the password to the vendor portal because four other people know it too. Nobody thought to change it.
Bob does not even have to be the problem.
The problem is that Bob left and his access didn’t.
That is former employee cybersecurity risk in its least exciting and probably most common form. Nobody attacked anything. Nobody dramatically stole a password. Somebody simply forgot to close the door.
I spent enough years in the Marines to know you don’t secure a building by deciding the guy who still has the key seems trustworthy.
You get the key back.
Same principle.
The Real Problem With Employee Offboarding and Cybersecurity
The former employee does not have to be angry. They do not have to be malicious. They may have left on perfectly good terms and be happily working somewhere else.
That has nothing to do with whether their old access should still work.
Someone leaves in March. IT doesn’t find out until April. Sometimes July.
By then, their Microsoft 365 account may still be active, an old authenticated session may still exist somewhere, and the shared password they knew for the vendor portal hasn’t changed.
According to a 2022 Beyond Identity survey of more than 1,100 employees and business leaders in the United States, United Kingdom and Ireland, 83% of respondents said they retained access to at least one digital asset from a previous employer. The study was self-reported and exploratory, so don’t turn that into “83% of every former employee in America.” It does show how easily access can survive someone’s departure.
The former employee isn’t necessarily the threat.
The access you forgot about is.
The Account You Forgot About Is Still Active
They discover it later.
Someone is reviewing accounts and there it is: an employee who hasn’t worked there in six months.
Then you start looking.
There’s the Microsoft 365 account. A vendor portal. A cloud application. A shared folder that was also shared with someone’s personal email.
One forgotten account has an annoying habit of introducing you to its friends.
Digit’s Rule 21: The account you forgot about is the one an attacker is hoping you forgot about.
Cloud applications make this more complicated. Some applications can be centrally managed through identity platforms such as Microsoft Entra ID and included in automated offboarding workflows. Others maintain their own accounts, permissions or sessions.
Which means disabling one account and declaring victory is a little premature.
A dormant account doesn’t require the former employee to use it. If those credentials are later stolen through phishing, malware, a password breach or another attack, someone else may inherit access that should have disappeared when the employee left.
Disable access when the employee leaves.
Not when somebody eventually asks, “Wait. Does Bob still have email?”
Shared Passwords Don’t Retire When the Employee Does
Now we get to shared passwords.
Everybody’s favorite.
Vendor portals. Billing accounts. Old software that predates single sign-on. That one shared account six people have been using since approximately the invention of electricity.
If an employee leaves and still knows one of those passwords, rotate it.
This isn’t an accusation. You don’t have to distrust the employee. They no longer need access, so the credential they know should no longer provide access.
That’s the entire decision tree.
A business password manager makes this much easier because you can control who has access to credentials and rotate them when needed. It doesn’t magically fix bad processes, though. You still have to remove the person.
NIST cautions against sharing authenticators between users and recognizes that passwords and other authentication methods can still be deliberately shared despite technical controls.
Individual accounts are better wherever they’re possible. When credentials genuinely have to be shared, control who gets them and make credential rotation part of offboarding.
Trust is not an access-control system.
The IT and HR Offboarding Disconnect That Costs Businesses Real Money
Here is the failure we see over and over.
HR knows someone is leaving.
Their manager knows someone is leaving.
Payroll certainly figures it out eventually.
IT finds out when somebody notices the Microsoft 365 license is still active.
This isn’t a complicated technology problem. The people responsible for removing access need to know that there is access to remove.
Preferably before the employee’s last day.
Not three weeks afterward.
And, while we’re making requests, 4:57 Friday afternoon isn’t ideal either.
That notification starts the process: account deactivation, session revocation, authentication-method review, device recovery, license reassignment, data ownership transfer, shared credential rotation and an access review.
Some of this can and should be automated.
Automation doesn’t eliminate ownership. Somebody still has to trigger the process, make sure all the relevant systems are included and verify that it actually worked.
CIS Controls v8.1 recommends having a process, preferably automated, for revoking access immediately when an employee is terminated.
That’s the part businesses sometimes miss.
Offboarding isn’t complete because HR collected a badge and somebody carried a laptop back into the office.
The digital keys matter too.
What Needs to Happen | Who Owns It | When |
Block Microsoft 365 sign-in and revoke sessions | IT | At departure |
Remove or update authentication methods | IT | At departure |
Rotate shared credentials the employee knew | IT | At departure |
Recover company devices | IT + HR | Last day or before |
Revoke SaaS application access | IT | At departure |
Transfer business data ownership | IT + Manager | Before last day |
Revoke VPN and remote access | IT | At departure |
Update vendor portal access | IT + Operations | At departure |
The Former Employee Access Checklist
Every business will have a slightly different list because every business has different systems.
But this is a pretty good place to start.
- Block the user’s Microsoft 365 sign-in, reset the password and revoke active sessions.
- Remove or update authentication methods associated with the former employee.
- Review active sessions and access across other cloud applications.
- Audit and rotate shared passwords the employee knew or could retrieve.
- Review SharePoint, OneDrive and Teams permissions, including external sharing and personal accounts where appropriate.
- Preserve, transfer or redirect email according to the company’s business and retention requirements.
- Get the company equipment back.
- Revoke VPN and remote-access credentials.
- Remove or reassign software licenses.
- Remove or update the employee’s access to vendor portals and third-party systems.
- Transfer ownership of business data, files and other resources.
- Review personal and mobile devices that were authorized to access company resources.
- Verify that all of it actually worked.
Number 13 matters.
A checked box tells you somebody performed a task.
It doesn’t tell you the account can’t still get in.
What You’re Probably Getting Wrong About Insider Threats
Say “insider threat” and people immediately picture a disgruntled employee downloading the client list before storming out of the building.
Sure. That happens.
It’s also the interesting version, which is probably why everybody remembers it.
The boring version is an old account sitting there for months because nobody disabled it.
A former employee may genuinely forget they still have access. Credentials can later be stolen. A dormant account can sit unnoticed because nobody is looking for activity from someone who supposedly doesn’t work there anymore.
That’s why offboarding shouldn’t depend on whether you trust the employee.
You can like them.
You can throw them a going-away party.
You can send them home with leftover cake.
Close the account.
What to Do Now
Former employee cybersecurity risk isn’t something you clean up once and cross off the list.
Every employee departure creates an offboarding event.
IT should know before the employee leaves. Access should be removed at the appropriate time. Shared credentials should be rotated when necessary. Business data needs to be transferred. Company equipment needs to come home.
Then somebody needs to verify that the digital doors are actually locked.
That last part is worth repeating.
Verify.
Because “we’re pretty sure we disabled it” is not a security control.
If you’re wondering how many former employees still have access to something in your business, that’s probably worth finding out before one of them accidentally answers the question for you.
2 Dog Digital works with businesses across the Raleigh/Triangle area and throughout North Carolina to build and manage IT processes like this.
We offer a no-charge assessment. You will learn something either way.
The consultation is free.
The breach cleanup is considerably less fun.
FAQ
How long can a former employee’s Microsoft 365 account stay active after they leave?
Until somebody takes action to disable or delete it.
Microsoft 365 doesn’t know Bob quit Tuesday unless your processes tell the technology what happened. A documented offboarding process makes sure access is removed when employment ends instead of whenever somebody eventually notices the account.
What should be on an IT offboarding checklist for departing employees?
At minimum, block Microsoft 365 sign-in, reset the password, revoke active sessions, review authentication methods, rotate applicable shared passwords, review cloud and file access, recover company devices, revoke VPN and remote access, transfer business data and remove access to third-party systems.
Your actual checklist should reflect the systems your business uses.
If you don’t know all the systems an employee has access to, you’ve just discovered another problem worth fixing.
Does blocking someone’s Microsoft 365 account remove their access to OneDrive and SharePoint?
Blocking a former employee’s Microsoft 365 sign-in prevents that account from signing in to Microsoft 365 services, including SharePoint and OneDrive.
Don’t stop there. Revoke active sessions, preserve or transfer business data, and review sharing permissions, personal accounts, guest accounts and third-party applications where appropriate.
Offboarding is a process, not one button.
How do shared passwords create a former employee cybersecurity risk?
If a departing employee still knows a shared password, they possess a credential that may continue to provide access after their individual account is disabled.
Rotate it.
Better yet, use individual accounts whenever possible and a business password manager when credentials genuinely need to be shared.
Are Raleigh businesses required to have a formal offboarding security process?
There isn’t one general North Carolina law requiring every Raleigh business to maintain a particular IT offboarding checklist.
Specific regulatory and industry requirements may apply depending on your business and the data you handle. HIPAA requires covered entities and business associates to have procedures for terminating access to electronic protected health information when workforce access ends. PCI DSS requires access for terminated users to be revoked immediately. Organizations pursuing SOC 2 also need appropriate controls around granting, changing and removing logical access.
The exact requirements depend on your business, your data and the regulatory or contractual standards that apply to you.