Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Someone who left my company may still have access to my systems

Short answer

Disable the leaver's own accounts first, then change every password they knew, then look for access that is not tied to a person: shared logins, API keys, server keys and apps connected through their account. The NCSC advises removing accounts for staff, suppliers or contractors who no longer need access, and reviewing who has access every few months.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A person left and I am not sure which accounts they still have.
  • They knew the shared passwords and those have not been changed.
  • My email, website or app stores were set up under their personal login.
  • Customers or staff mention something odd done by an account that should be dormant.
  • Nobody wrote down which systems the person used.

Why does this happen?

  1. Leaver accounts are forgotten

    The NCSC says to remove or disable accounts for staff, suppliers or contractors who no longer need access, because these often keep outdated passwords and settings. It also advises reviewing who has access to important accounts every few months.

  2. Shared passwords stay known

    If the team shares logins, removing the person's own account does nothing about the passwords they remember. Every shared password has to be changed.

  3. Access is attached to the person, not the company

    Domain registrations, store accounts, cloud accounts and ad accounts are often created under one person's email. When they go, you may not be able to prove ownership, or receive security emails.

  4. Removing a person does not always remove everything they hold

    On GitHub, removing a member of an organisation takes away access to private forks of its private repositories, but they may keep local copies. Forks in other organisations can still give access, and the organisation is responsible for making sure confidential information is deleted.

  5. Tokens and keys keep working

    API keys, access tokens, server keys and webhook secrets are not tied to a person's login. They keep working until someone replaces them.

What can I do about it today?

  1. Disable first, delete laterSuspend or disable the person's accounts rather than deleting them. Deleting an account can lose emails, files and the history you need.
  2. Start with email and the main admin accountsEmail is how passwords get reset everywhere else. Remove the person's access there first, then to payments, website host and app stores.
  3. Change every shared password they knewDo it from a trusted device, and give the new ones out only to people who need them.
  4. Write down what they usedGo through their email, calendar invites and the list of tools your company pays for. The list is the checklist.
  5. Check connected apps and devicesLook for apps authorised through their account, forwarding rules on their mailbox, and company devices they still hold.
  6. Do not accuse anyone without evidenceIf you think data was taken, keep the logs and talk to a lawyer before contacting the person.

When should I bring someone in?

  • The person managed servers, code, the app or the website and you do not know what exists.
  • You find activity after their last day.
  • Domain, store or hosting accounts are in their personal name.

How do I handle it?

  1. Build the list of what they could reachFrom your systems, billing and the person's email history, I draw up each account, key and server they could use.
  2. Remove in a safe orderAccounts are disabled, passwords rotated and keys replaced one by one, with a backup first, so that nothing live breaks by surprise.
  3. Look for access that is not tied to a personAPI keys, deploy keys, tokens and webhook secrets are replaced, and the old ones are revoked.
  4. Check the logsI look for sign-ins and changes after the leave date, and report what I find without guessing at motives.
  5. Make ownership belong to the companyAccounts are moved under company emails and roles, and a short leaver checklist is written for next time.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Should I delete their accounts?

Disable first. Deleting can destroy mail and files that you need, and it cannot always be undone.

How often should I review who has access?

The NCSC advises reviewing who has access to important accounts every few months.

What if they took a copy of the code?

On GitHub, a removed member may keep local copies. Contracts and the law decide what they may do with them, so speak to a lawyer.

Can you find out whether they did anything?

I can read the logs the systems keep. Where logging was off, there may be nothing to read.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.