Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an Access Review?

An access review is a periodic check in which a named person confirms, in writing, that each user still needs the access they hold. It is the control that undoes privilege creep.

Illustration for the cybersecurity term Access Review
Home / Blog / Cybersecurity Terms / What Is an Access Review?
17 November 2026

What Is an Access Review?

What Is an Access Review?

Provisioning is easy to get right because somebody is waiting for it. Deprovisioning is hard because nobody is. An access review—also called access certification or recertification—is the periodic check that corrects for this: a named reviewer looks at each grant, decides whether it is still justified, and records the answer.

It exists because of a predictable drift. People change teams and keep the old permissions. Projects finish and the project group survives. A temporary elevation granted during an incident is never reversed. Nothing about that drift is detectable from a single access request, which is why it needs a periodic sweep rather than better gatekeeping at the front door.

Anatomy of a Campaign

A campaign defines a scope, a reviewer, a deadline, and a default. Scope might be a single privileged group, every member of a high-value application, or all guest accounts in the tenant. The reviewer is usually the resource owner or the user’s line manager, and that choice matters more than any other decision in the design.

The default is the part teams forget. What happens to grants nobody reviewed by the deadline? Options are usually keep, remove, or take the recommendation the system offers. Defaulting to keep makes the campaign optional, which is how organisations end up with 97% completion rates and no reduction in standing access. Defaulting to remove forces engagement, but it needs a tested rollback path and a grace period before you try it on anything production-facing.

Who Should Review What

ScopeBest reviewerTypical cadence
Privileged and administrative rolesResource owner, plus second approverMonthly or quarterly
Business application rolesApplication ownerQuarterly to half-yearly
Guest and partner accountsInviting sponsorQuarterly
Everyday group membershipLine managerAnnually
Service accounts and workload identitiesNamed technical ownerQuarterly

Self-review, where users certify their own access, is worth running once as a data-gathering exercise and never as a control. People approve themselves at close to 100%, which tells you nothing. Service accounts are the awkward category, because they have no manager and often no documented owner; that gap is addressed in our entries on service account security and machine identity.

How Reviews Fail

The dominant failure is rubber-stamping. A manager receives 340 rows in a spreadsheet, recognises every name, and approves the lot in four minutes. The campaign completes, the evidence pack looks immaculate, and nothing was actually examined.

Three changes measurably help. Give the reviewer context next to each row—last sign-in date, how the access was granted, whether it is unusual compared with peers in the same role—so that the decision takes judgement rather than name recognition. Cut the batch size by scoping campaigns narrowly and running them more often. And sample the results: pick ten approved rows at random afterwards and ask the reviewer to explain them. That audit of the audit changes behaviour faster than any reminder email.

The second failure is reviewing the wrong thing. Certifying group membership while the real privilege sits in a nested group, a directory role, or a just-in-time elevation path produces a clean report and an unchanged risk. Map effective permissions before you design the scope.

What Auditors Expect

ISO 27001 Annex A 5.18 requires access rights to be reviewed in line with a documented policy, and an ISO assessor will ask to see the policy, the campaign records, and evidence that revocations actually happened. PCI DSS v4.0 requirement 7.2.4 is more prescriptive for in-scope environments: review user accounts and access privileges at least once every six months, with documented management sign-off that the access remains appropriate. Financial entities in scope of DORA face similar expectations through its ICT risk management requirements.

The evidence that stands up is not the completion percentage. It is the list of grants removed, the date each removal took effect, and a reconciliation showing that what the reviewer rejected is genuinely gone from the target system. Pair the campaign with an identity lifecycle process so that the same answers are enforced automatically next time.

At Privia Security, we assess identity governance and access certification maturity through our cyber risk analysis services.

FAQ – Frequently Asked Questions

How Often Should Access Reviews Run?

Match the cadence to the risk. Privileged and administrative access warrants monthly or quarterly review, business application roles quarterly to half-yearly, and ordinary group membership annually. PCI DSS v4.0 sets a floor of every six months for in-scope accounts. Running everything annually at once produces a single overwhelming campaign that reviewers cannot engage with properly.

What Is the Difference Between an Access Review and an Audit?

An access review is an operational control performed by the business owner or line manager who understands the job in question. An audit is an independent assessment that checks whether the control exists and works. Auditors frequently sample access reviews, so weak reviews surface as audit findings, but the review itself is a management activity rather than an assurance one.

How Do I Stop Reviewers Approving Everything?

Reduce batch size so each campaign is small enough to read, present decision support beside every row such as last sign-in date and peer comparison, and set the no-response default to remove rather than keep once the process is stable. Then sample approved decisions afterwards and ask reviewers to justify a handful. Being spot-checked changes behaviour more than any reminder.

Do Access Reviews Cover Service Accounts?

They should, and this is where most programmes have a gap. Service accounts have no line manager, so they need a named technical owner recorded in advance. Review them quarterly against what the application genuinely calls, check whether the credential has been rotated, and treat any account with no identifiable owner as a candidate for disablement rather than automatic renewal.

Related Terms

You May Be Interested In These

What Is Volatile Data Collection?

Cybersecurity Terms

17 November 2026

What Is Volatile Data Collection?

Read More
What Is Mobile Forensics?

Cybersecurity Terms

17 November 2026

What Is Mobile Forensics?

Read More
What Is the OWASP IoT Top 10?

Cybersecurity Terms

17 November 2026

What Is the OWASP IoT Top 10?

Read More