← ALL ARTICLES

AUDIT & FINDINGS (CAPA)3 MIN READ

What Evidence an Auditor Should Request for Access Reviews

The population, the reviewer decision, and the exception disposition an access review has to show before it counts as operating evidence.

An access review is operating evidence only when it shows the population that was in scope, the decision a named reviewer made, and what happened to the exceptions. A policy, a dashboard tile, or an export with no reviewer does not answer the request.

Ask for the population before the sample

The first object is the list of accounts that had access during the period, not a sample pulled from a system the team already knows looks tidy. The population should say who had access, to what, and over which dates. For privileged access, the population is the admin and elevated roles, not the full employee directory with those roles buried in it.

If the list is a screenshot of one user, or a filtered view that hides terminated and service accounts, the auditor cannot tell whether the sample was drawn from the whole set. Ask for the export the review started from, including the date it was generated and the system it came from.

Ask for the decision, not only the export

The export shows who had access. The review shows what someone did with that fact. Each row the auditor relies on needs a reviewer, the date of the decision, and the decision itself: retain, change, or remove. A name in a “manager” column is not a decision if nothing records that the manager looked.

Timeliness belongs in the same request. If the policy says quarterly, the evidence has to show that this review happened inside the quarter, not that a list was exported and signed three months later. The cadence is part of the operation of the control.

Ask what happened to the exceptions

Exceptions are the part of the review that can fail: a terminated user who still has access, a shared account, a privilege no one can explain, a review completed after the due date. The request should ask for those rows separately, plus the disposition. “IT is aware” is not a disposition. Removal, an approved exception with an owner and an end date, or a finding that is still open are dispositions.

If nothing was flagged, the evidence should still say that. An empty exception log is meaningful only when the population and the reviewer are also there, so the auditor can see that a complete list was examined and nothing met the exception criteria.

What does not answer the request

Often offered What it shows What is still missing
Access-control policy The rule the organization claims to follow That a review happened in this period
Dashboard count of reviews “complete” A status someone entered The population, the reviewer, and the decisions
User list with no sign-off Who had access at a moment in time That anyone decided to keep or remove it
Ticket that says “access reviewed” That a task was closed Which accounts were in the review and what changed

A request an auditor can send

For one system and one period, the useful request is short:

  • The population of accounts with access during the period, generated from the system of record, with the export date.
  • The privileged and service accounts called out from that population, not folded into a general user list.
  • The review record: reviewer, date, and the retain, change, or remove decision.
  • The exception rows and the disposition of each, including any that are still open.
  • The policy cadence, so the review date can be compared with it.

That set is the evidence. Collecting it, assigning it to an owner, and keeping the decision next to the control is a workflow question, and it is a different piece of work from deciding what the auditor is entitled to ask for.