Join our Newsletter — 33% off our NHI Course

Access reviews: how do teams stop rubber-stamping and fatigue?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 18346
Topic starter  

TL;DR: Access review fatigue turns certifications into rubber-stamping when managers are asked to approve too many entitlements with too little context, according to Saviynt. The governance problem is not review volume alone but the assumption that broad, periodic certification is enough to manage risk across human and non-human identities.

Editorial analysis by NHI Mgmt Group, based on content published by Saviynt: “Access Reviews Done Right”.

Key questions

Q: How should security teams reduce access review fatigue without weakening governance?

A: Security teams should reduce review fatigue by shrinking entitlement lists, grouping stable access into lean roles, and using contextual signals to highlight exceptions.

Q: Why do access reviews still fail even when reviewers approve or revoke items correctly?

A: Because a correct decision does not guarantee the downstream entitlement changed.

Q: Should organisations apply the same access review process to human and non-human identities?

A: No. Human access reviews can work on periodic certification cycles, but non-human identities often change faster and need event-based review tied to deployment, rotation, or decommissioning. The better model is shared governance with different review mechanics, so the process matches how each identity class is created, used, and retired.

Practitioner guidance

  • Define risk-based review scope Replace universal review cadences with risk-shaped campaigns that distinguish routine access from privileged, sensitive, or anomalous access.
  • Add plain-language reviewer context Present business descriptions, entitlement meaning, and flagged exceptions so approvers can decide without interpreting technical role IDs.
  • Enforce closed-loop revocation Verify that a revoke decision changes the underlying entitlement source, including role membership and inherited access paths.

Bottom line: Access review fatigue turns certification into a low-confidence control when scope, cadence, and context are not aligned to risk.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 17926
 

Certification fatigue is a control failure, not a user-behaviour problem: When reviewers are overloaded with too many entitlements and too little context, access reviews stop functioning as a governance gate and become a throughput exercise. The article shows that the failure mode is predictable, which means the programme design is the issue, not reviewer discipline. The implication is that access certification has to be risk-shaped, not calendar-shaped.

A few things that frame the scale:

A question worth separating out:

Q: What is the difference between a review that records approval and a review that actually reduces risk?

A: An approval-only review captures a decision, while a risk-reducing review changes the entitlement state and leaves an auditable trail. If the workflow does not validate that access was removed at the source, the organisation has evidence of review but not evidence of control.

👉 Read our full editorial: Access review fatigue undermines identity governance and audit defence



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.