How to prepare a user access review
Prepare a user access review with a dated inventory of grants, evidence of who still needs them, and a decision queue for application owners.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What user access review is
A user access review checks whether people and automated identities still need the permissions they hold in a defined set of systems. Start with a dated inventory of access grants, the records that give an identity a permission. Trace each grant to its source and gather the evidence a reviewer needs to decide whether it should stay. The deliverable is a queue of specific decisions, each tied to the account, permission, and route that gave the account access.
An entitlement review is another name for this work. An entitlement is a specific permission or role. An access attestation is the reviewer's recorded decision about that access, including when they made it and why. A good review distinguishes a proposed decision, a recorded decision, and a completed change verified in the application. The preparation pack is a draft for qualified IT and security reviewers. Reach a conclusion only for the systems and permissions your evidence covers.
What it does for the business
- Give owners decisions they can makeApplication owners can work through specific grants with the relevant evidence beside each one. They can spend their time judging business need instead of asking an administrator which account a row refers to.
- Find privileges that survived a job changeA join between role assignments and dated personnel changes helps you find people whose access may still reflect their old duties. You can bring the specific grants to the owner and adjust the transfer checklist if the same pattern keeps appearing.
- Protect access people and services still needRecording the sponsor and purpose gives reviewers grounds to keep permissions that support necessary work. Keeping the scope down to a particular grant also lets administrators plan a narrow change when other permissions should be preserved.
- Prepare evidence you can reuseA record of the population, reviewer decisions, and exceptions helps you answer later questions about what was checked. When you repeat the exercise, you can prioritize changes since the prior cutoff while keeping the earlier decisions tied to their original evidence.
User access review, step by step
Set the cutoff and inventory each grant path
A review covers the population you can trace to a defined set of records.
What to do
- Name the tenant, applications, and resources included in the review. Agree on a cutoff with a time zone and record when each export was taken, so the reader can see which records describe the cutoff and which need confirmation.
- Gather directory identities, application account lists, direct grants, and group membership. Include nested groups where your evidence supports the chain. Note where the application has local roles or accounts that the directory export cannot show.
- Make one row for each distinct identity, resource, permission, and assignment path. If two groups give a person the same role, keep both routes so an owner can see what remains after changing either one.
- Record native identifiers and evidence locators, such as file names and row references. Save any prior decision alongside the snapshot it applied to and record unknown coverage explicitly.
Why
Two exports taken at different times may describe different states of the same system. A group role could have changed between snapshots, leaving you unable to tell what a member held at the cutoff. Capturing the times, resources, and route lets a reviewer distinguish a real inconsistency from a difference in export scope.
Match identities and apply approved policy
The case for keeping or removing a grant starts with evidence about the correct identity.
What to do
- Use the directory's stable identity ID and the application's account ID to make the match. Treat display names and email addresses as clues to follow up, especially for contractors, rehired staff, and renamed accounts.
- Compare hire, transfer, departure, and contract dates with the review cutoff. A future departure belongs in the timeline as a future event. Flag current grants held by people who already left for the owner's attention under your existing policy.
- Review service accounts and other automated identities using their sponsor, purpose, expected lifetime, and the system that depends on them. Mark missing sponsor evidence for follow-up instead of trying to match the account to a personnel record.
- Check approved roles, separation of duties rules for incompatible responsibilities, rules for privileged access, and exception expiry. Use last-use evidence as context and flag the policy gap where no rule settles the issue.
Why
An old email on an account can look like a match to a new employee with the same address. The reviewer needs the actual account mapping and the status effective at the cutoff. Least privilege means giving an identity only the access needed for its purpose. Apply that principle through your approved role requirements and documented exceptions.
Put proposed decisions in the reviewer queue
A reviewer should be able to decide from the row and the evidence it points to.
What to do
- Assign each row to the accountable application reviewer. When you need a manager or sponsor to explain the business need, identify that input and keep responsibility for the final decision clear. Mark rows without an accountable person as unassigned.
- Write the observed grant, the policy or exception that applies, and a short reason for your proposal. For a transferred employee, name the role and ask whether their new duties still require the access.
- Give the reviewer the decision options and fields for justification and decision date. Include approved exceptions with their expiry. Bring expired exceptions back for review, with the earlier approval still visible.
- Keep responses separate from proposals. If the response leaves the scope unclear, ask the reviewer which account and grant they mean before recording a final decision.
Why
A bare list of names pushes the investigation onto the reviewer and makes answers hard to interpret. A row that names the permission, explains the proposal, and asks about specific work gives the reviewer a decision they can document and an administrator a clear reference if a change follows.
Reconcile the counts and check the decisions
Every removal proposal should identify a permission precisely enough for an administrator to act on it.
What to do
- Account for each raw line as a unique grant path, an exact duplicate, or an exclusion with a reason. Break out unresolved identities and application coverage so the reviewer can see what remains outside the decision queue.
- Reopen the evidence for consequential proposals. Confirm that the native account, resource, role, and route agree with the source and that the source is current enough for the stated decision.
- Check residual access before describing a removal. A person may have a direct assignment, a role through a second group, or an existing session. Write down which of those still needs a separate check.
- Check what the pack exposes. Provide the identifiers and source references the reviewer will need, and keep credentials, tokens, and unnecessary personal details out of the deliverable.
Why
Duplicate export rows can make a review appear broader than it is, while collapsing separate routes can hide continuing access. Reconciling each stage makes the population defensible. A source-to-queue check also catches records whose dates or identity mappings make a proposed action too uncertain to carry out.
Hand off the draft and track what happens next
A recorded decision and a verified access change belong in separate records.
What to do
- Lead with the highest-consequence item that has enough evidence for review. Give the reviewer the complete scoped queue and a concise summary of uncovered systems, unresolved identity matches, and unsettled decisions.
- Route approved changes through your authorized process. Carry forward the exact account, grant path, reviewer decision, and intended effect, including any permissions the account should keep.
- Read the provider again after the change and record what access remains. Check other inheritance routes and verify session handling separately where it matters. Save the relevant readback alongside the action and its date.
- File outstanding issues with an owner and the evidence needed to close them. For a missing application export, specify which roles or resources it must cover and what snapshot date you need.
Why
A reviewer may approve removing one role from one account. The administrator still needs to perform the approved change and check effective access in the provider. Keeping these events separate lets you see where work stopped when a later check still finds the grant.
Common mistakes
- Counting accounts as grantsOne account can hold multiple roles, and each role can have multiple paths that require separate evidence.
- Treating email as an immutable identifierReused or changed addresses can tie the permission to the wrong person.
- Using inactivity as the removal testSparse sign-in evidence leaves the business purpose and emergency use of the grant unresolved.
- Carrying exceptions forward indefinitelyAn expired approval needs a fresh decision about the current grant.
- Closing a row on approvalRecord the approval first and follow it with evidence of the resulting access state.
What a good result looks like
- A named tenant, dated cutoff, in-scope resource list, and clear coverage gaps.
- A traceable row for each grant path, with stable identity and resource identifiers.
- A named reviewer and a reasoned proposal tied to evidence and policy.
- Separate fields for prior decisions, pending responses, approved exceptions, and new decisions.
- A handoff that names the next owner action and identifies what still requires provider verification.
And then what? Using the result
- Ask application reviewers to resolve the highest-consequence items first, starting with the grant and evidence listed in the pack.
- Assign someone to close gaps such as missing app exports and unresolved ownership, then refresh the affected rows with dated evidence.
- Route reviewer-approved changes to authorized administrators and attach the provider readback to the change record.
- Add expiring exceptions to the team's review schedule and give their sponsors a date to provide renewed justification.
- Use recurring findings to improve onboarding, transfers, and offboarding so the next queue starts with cleaner role and ownership records.
When to run it
- Before an assurance reviewUse the pack to give the reviewer a scoped population, recorded decisions, and evidence paths. Check with the control owner on the required period and supporting records.
- After a reorganization or staff transferReview the grants tied to old responsibilities and ask current owners which ones still support the person's work.
- When a sensitive application changes ownersGive the incoming owner a dated inventory with the privileged roles, external accounts, and exceptions that need their attention.
- Before retiring an integrationTrace its automated identities to the resources they can reach, then ask the technical sponsor which grants support workloads that will keep running.
Questions people ask
How do you prepare a user access review?
Fix the scope and cutoff, inventory each grant path, match identities, and give named reviewers a proposed decision with evidence for each row. Record gaps and keep the reviewer's decision separate from the administrator's action.
Who should review application access?
Give the decision to the accountable application reviewer who can judge the access against approved policy and business need. Bring in a manager or workload sponsor when the reviewer needs context about what the account does.
How do you review access inherited through groups?
Trace each membership and role assignment from the account to the resource. Keep multiple routes separate so you can see where effective access would persist after one route changes.
What evidence belongs in an access review for SOC 2?
Start with the scoped grant population, dated source records, reviewer decisions, and evidence of how approved changes were handled. Ask the control owner or assurance reviewer which systems, dates, and records are required for your review.
Does reviewer approval remove access?
Approval records a decision, and removal requires a separate authorized change. Read the provider afterward to confirm the resulting access and check remaining routes or sessions where relevant.
How do you handle a missing grant export?
Record the affected application and permissions as a coverage gap and ask for the specific dated export. Continue reviewing the grants supported by the evidence you already have.
More jobs in Cybersecurity
Prepare a user access review, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac