Wealth management

Disabling the account isn't the same as ending access

A retailer with 33 million customers traced a massive data breach back to someone who didn't work there anymore.

1 min readOriginally posted on LinkedIn

A retailer with 33 million customers traced a massive data breach back to someone who didn't work there anymore.

That's the headline version. The version I see at small firms is quieter. An advisor leaves on a Friday, and three weeks later their personal phone is still pulling mail, because the account "was disabled" and everyone moved on.

Here's the part most people get wrong: disabling a Microsoft 365 account blocks new sign-ins. It does not end sessions that are already running. A browser or phone app already signed in keeps working until its token expires. Revoking those sessions is a separate step, and it's the step that gets skipped.

Then there's everything that was never the account. The OneDrive folder shared to a personal address two years ago. An app they connected to your tenant once and forgot. Delegated access to a partner's mailbox. Client files on a laptop nobody wiped.

For a wealth management practice, the damage isn't technical. It's the call you have to make to a client about who could still see their statements.

The fix isn't clever. It's a written leaver checklist, run the same day, every time: account, sessions, devices, shares, connected apps.

Worth testing yours before your next cyber renewal.

ShareLinkedInEmail

Want the next one in your inbox?

One practical Microsoft 365, Copilot, Azure, or security move per week — plain English, no pitch.

Subscribe via email

All editions