Skip to content
Black Fox Security

04 / Managed security

Access reviews: who still has the keys

We review, on a schedule, who can get into your directories, cloud accounts and key applications, and whether they still should. You get the clean-up and the evidence an auditor asks for.

Overview

Why access drifts

People join, change roles and leave. Contractors finish their projects. Service accounts outlive the systems that needed them. Each change is small, and nobody removes access with the same urgency as they grant it. After a year, the list of who can reach what rarely matches anyone's intent.

Black Fox runs periodic access reviews across the systems that matter: your directory, your cloud platforms and the applications that hold your data or your money. We collect the accounts and permissions, compare them with your records of who works where, and put each questionable entry in front of the person who can decide.

Privileged access gets more attention than the rest. Administrator, root and owner rights are where a single forgotten account does the most damage, and where auditors look first.

Who it is for

Organisations preparing for or maintaining ISO/IEC 27001, SOC 2, PCI DSS or similar, where periodic access review is an expected control, and any team that has grown, reorganised or changed systems and is no longer sure who can reach what.

The work, from scoping to evidence.

What we do

  1. Systems in scope

    We agree which systems are reviewed, for example your identity directory, cloud accounts, source code platform, finance and HR applications, and how often.

  2. Account and permission extracts

    We collect who has access and with which rights, from exports or read access you provide, and match accounts to real people.

  3. Joiners, movers and leavers

    We compare access against your HR and contractor records: leavers who still have accounts, movers who kept their old rights, joiners with more than their role needs.

  4. Privileged access

    Administrator and owner rights, shared and break-glass accounts, and service accounts reviewed one by one, with their owners named.

  5. Owner attestation

    Managers and system owners confirm or revoke each entry, and their decisions are recorded with dates.

  6. Process review

    We look at how access is requested, approved and removed, and recommend changes so the next review finds less.

How the engagement runs

  1. Kickoff

    We agree the systems, the review frequency, the owners and the evidence your auditors expect, and sign an NDA first if you need one.

  2. Collection

    We gather the account and permission data and your records of current staff and contractors.

  3. Analysis

    We match, compare and flag: orphaned accounts, excessive rights, segregation of duties conflicts and unexplained privileged access.

  4. Attestation

    Each owner receives their list, confirms or revokes, and we follow up on the answers that do not come.

  5. Clean-up and evidence

    Your teams remove what was revoked, we verify it, and the review is packaged as evidence. The cycle then repeats on the agreed schedule.

What you receive

  • Inventory of accounts and permissions per system
  • Findings report: orphaned accounts, excessive rights, conflicts
  • Privileged access register with named owners
  • Owner attestation records with decisions and dates
  • Verification that revoked access was removed
  • Process recommendations for joiners, movers and leavers

Questions

How often should access be reviewed?

It depends on the system and your framework. Privileged access and systems in scope for an audit are commonly reviewed more often than the rest. We help you set a frequency you can defend and actually keep.

Do you remove the accounts?

Your teams do, because they own the systems and the change process. We tell them what to remove, follow up and verify that it was done.

Will this satisfy our auditor?

We cannot speak for your auditor. We produce the evidence that access reviews are usually tested with: who was reviewed, by whom, what was decided and that the decision was carried out. Your auditor decides whether it meets the requirement.

Do you need administrator access to our systems?

No. Exports or read-only access are usually enough, and we agree how the data is handled and deleted before we receive it.

Find out who still has the keys

Tell us which systems matter most and when your next audit is. We will propose a review that fits both.

Request a meeting

Send us a request to arrange a meeting, so you can tell us about your project and we can introduce ourselves and our experience properly.

§ A

Reading preferences

Adjust how this site looks and reads. Your choices apply at once and are kept on this device only.

Specimen

Good engineering is shown, not claimed. Read this line to judge your settings.

§ A.1Text

Text size
Line height
Letter and word spacing
TypefaceAtkinson Hyperlegible was designed for low vision; OpenDyslexic for some readers with dyslexia.
Align text leftRemoves justified text and hyphenation.

§ A.2Reading aids

Reading aidFollows your pointer to help you keep your place.
Highlight links
Highlight headings
Stronger focus outlineFor keyboard navigation.

§ A.3Colour and contrast

Contrast
Colour saturation
Hide decorative patternsRemoves the engraved line patterns behind content.

§ A.4Motion and pointer

Stop animationsAnimations are already reduced when your system asks for it.
Large pointer