Blog/How-to guides

Access Reviews: Checking Who Can Still Get In

Permissions only ever grow unless someone deliberately checks. A practical quarterly access review you can finish in an afternoon, and what it usually turns up.

CyberWatch AI1 November 2026 · 5 min read
A printed spreadsheet on a desk beside a pen and a laptop

Access lists only grow. There is a moment, every time someone joins a project or covers for a colleague, when adding a permission is the obvious thing to do. There is no equivalent moment for taking one away. Nobody's calendar says "today is the day Priya stops needing the payroll system." So the list grows, quietly, until somebody deliberately sits down and reads it.

That sitting down is an access review. It is one of the few security exercises that costs nothing but time and almost always finds something on the first attempt.

What you are actually checking

Three questions, in this order of importance:

  1. Should this person still have an account at all? This catches leavers, finished contractors and the agency you stopped working with last spring.
  2. Should this account still have this level of access? This catches the person who covered for finance for six weeks in 2024 and never came off the approvals list.
  3. Who owns this account that is not a person? Service accounts, shared mailboxes, API keys and the login created for a one-off migration.

The third question is the uncomfortable one. Accounts with no named owner are the ones nobody monitors, nobody rotates the password on, and nobody notices signing in at three in the morning.

Build the list of systems once

The hardest part of a first review is not checking the permissions. It is working out what to check. Most small businesses have more systems than they think, because tools arrive one at a time and never get written down anywhere central.

Make a single list and keep it. For a typical small firm it includes:

  • Email and office suite, including administrator roles. See securing your office suite.
  • File storage and any shared drives.
  • Accounting, payroll, invoicing and the online banking portal.
  • The customer database or CRM.
  • Website hosting, the content management system and the domain registrar.
  • Social media business pages and advertising accounts.
  • Collaboration tools, project trackers and anything with a free tier that quietly holds client data.
  • Remote access, VPN and the office router.
  • The password manager itself, and who can see which shared vaults.

Write it in a spreadsheet with one row per system and a column for who owns it internally. That document is useful for several other things, including insurance questionnaires and the asset list that most security frameworks ask for.

How to run it without it taking a week

Export, do not eyeball. Nearly every admin console will give you a list of users and their roles as a CSV. Pull them all into one place before you start making judgements, because comparing is faster than clicking through screens.

Then split the work. Whoever manages IT produces the lists. Each manager confirms their own team, because they know what the job actually requires and the IT person does not. Send a manager a list of nine names and ask them to reply with "keep", "reduce" or "remove" against each one. That is a five-minute task for them, which is why it gets done.

Review the high-consequence lists first and in more detail:

  • Administrator roles in every system, every quarter. This is the single highest-value check.
  • Anyone who can move money or change bank details.
  • External parties, including your IT provider. If you use one, ask them for the list of their staff who hold access to your tenant, and ask how they control it on their side. See whether you need an IT provider.

Everything else can be annual. Trying to review every folder permission quarterly is how an access review becomes a thing nobody ever does again.

What the first review usually turns up

Patterns repeat across small organizations. Expect some version of the following.

Someone who left is still active somewhere. Rarely in the main email system, because that one gets disabled. Usually in a supplier portal, a design tool, a shared social media page or the CRM. This is common enough to deserve its own treatment in former staff access.

More administrators than anyone expected. See least privilege for how to cut that back using narrower built-in roles instead of all-or-nothing admin.

Accounts nobody can explain. A login called "scanner", an integration user from a migration, a mailbox for a department that no longer exists. Do not delete these on sight, because some of them are genuinely running something. Find out what each one does, give it a named owner, then disable it and wait a week before removing it. If a review turns up a sign-in alert or an access notification you cannot place, paste it into CyberWatch AI Scan for a free check.

Paid seats for people who do not work there. Reviews pay for themselves surprisingly often.

Two habits that make the next review trivial

First, record the grant at the moment you make it. A one-line note saying who got what, who approved it and whether it has an end date turns the next review from an investigation into a comparison. Temporary access should always carry a date.

Second, do not use the review as your leaver process. A quarterly check means someone who left in week one keeps access for up to twelve weeks. Removal on the last working day is a separate, immediate task covered in joiners, movers and leavers. The review exists to catch what that process missed, not to replace it.

Prove it happened

Save each completed review with the date, the systems covered, the decisions and what actually changed as a result. Three reasons this matters. It makes the next one faster. It answers the access questions on cyber insurance forms and client security questionnaires honestly. And a review that produced no changes at all, repeatedly, is a sign that nobody is really looking.

If you are tracking whether your security is improving over time, the completion of a quarterly access review is one of the better indicators available to a small business, because it is binary and hard to fake. There are more like it in measuring security progress.

Start smaller if the full list feels daunting. Reviewing only the administrator roles in your email and office suite takes twenty minutes and removes more risk than reviewing everything else combined.

An access review is maintenance. It is the equivalent of checking which keys are still on the ring, and like most maintenance it is boring right up until the day it isn't. For how it fits with the rest, see administrator account security and protecting small businesses from digital threats.

Frequently asked questions

How often should a small business review access?

Every three months for administrator roles and anything touching money, and once a year for everything else. Leavers should be handled immediately rather than waiting for a review.

Who should do the review?

Whoever manages IT pulls the lists, and the manager of each team confirms their own people. The manager knows what the job needs; the IT person knows what the system shows.

How long does a review take?

For a team of twenty, an afternoon the first time and perhaps an hour after that, because most of the work is building the list of systems and that list barely changes.

What is usually found in a first review?

Former staff still active somewhere, more administrators than anyone expected, service accounts nobody can explain, and at least one tool still being paid for that nobody uses.

Do I need special software for this?

No. A spreadsheet works for a small organization. Some subscription tiers include automated access reviews, which help once you pass roughly fifty people.

What about accounts with no obvious owner?

Orphaned accounts are the most important finding. Do not delete one blindly if it might be running something. Identify what it does, give it a named owner, then disable or remove it.

Should contractors and suppliers be in the review?

Yes, and they are the group most often missed. Any external person or firm with a login to your systems belongs on the list, including your IT provider.

What do I do with the review afterwards?

Save the list with the date and what you changed. The next review becomes a comparison rather than a fresh start, and you can show a client or insurer that the process is real.

Sources

  1. Identity and access management, UK National Cyber Security Centre
  2. Asset management, UK National Cyber Security Centre
  3. What are access reviews?, Microsoft Learn
  4. Valid Accounts, Technique T1078, MITRE ATT&CK
  5. Insider Threat Mitigation, US Cybersecurity and Infrastructure Security Agency
  6. Security best practices for administrator accounts, Google Workspace Admin Help
  7. Cybersecurity Framework, NIST
  8. Small organisations guide to cyber security, UK National Cyber Security Centre
Share this article
LinkedIn WhatsApp X
For organizations

Your people get these messages at work too.

CyberWatch AI sends your staff realistic practice attacks, trains the gaps it finds, and shows management exactly where the organization stands.