Find the AI tools nobody approved
Skip to content
Resources

How do I automate user access reviews?

Learn how to automate user access reviews, from the data you need to connect to the access you should flag first, with a ready-made prompt to build your own.

Rob Jardine7 min read

To automate user access reviews, connect your identity provider (IdP) and HR system to one review, then route each entitlement to the manager or system owner who has to sign it off. The review should flag risky access first, record every keep or remove decision, and raise a ticket for each approved removal.

In Dimension by ThreatAware, the User Access Review application (opens in a new tab) does this on live data from tools you already use, such as Microsoft Entra ID or Okta for identity and Workday for HR. A person approves each revocation before Dimension raises a ticket in your IT service management tool, and every decision is written to the audit log.

You can run the application as it is, customize it in plain language, or build your own version from the prompt below.

Stolen credentials are still a common way in: credential abuse was the initial access vector in 13% of breaches with a known vector in Verizon’s 2026 Data Breach Investigations Report, second only to vulnerability exploitation at 31% (19,905 breaches, October 2024 to November 2025). Every account that should have been removed is one more set of credentials an attacker can use.

Why do manual user access reviews break down?

Manual user access reviews break down because they run on exported spreadsheets that are out of date before they reach reviewers. Someone exports group memberships, emails them to managers, then chases replies until the deadline.

Managers rubber-stamp long lists because nothing tells them which rows matter. Revocations get agreed but not actioned, and the evidence for the auditor sits in an inbox.

“Access reviews fail when the data is a spreadsheet export. By the time a manager opens it, people have moved teams, left the company or picked up new rights, and the manager signs off a list that is already wrong.” — Rob Jardine, CMO, ThreatAware

How do you run a user access review without a dedicated tool?

You can run a user access review without a dedicated tool by exporting access data, joining it to HR records in a spreadsheet and sending each owner their section. It works for a small team with a few systems, but it gets harder as the number of systems and people grows.

  1. Export group memberships and application assignments from each identity provider, using its admin console, reports or API.
  2. Join them to an export from your HR system of current staff, their managers and recent leavers.
  3. Split the list by manager or system owner and send each person their section.
  4. Chase replies, collect each keep or remove decision, then raise a ticket for each removal by hand.
  5. Save the spreadsheets and email trail as audit evidence.

Some identity providers include their own access reviews. Microsoft Entra ID, for example, can review group memberships, enterprise application access and role assignments, and the feature requires a Microsoft Entra ID Governance or Microsoft Entra Suite subscription, with some capabilities available on Entra ID P2. Dedicated identity governance and administration (IGA) platforms also run access reviews across many systems.

The manual route breaks down at scale: the export is out of date by the time it’s sent, owners can’t see which rows are risky, and approved removals don’t always get actioned.

What should a user access review include?

A user access review that will stand up to an audit covers five things: scope, an owner for each entitlement, risk context, a recorded decision and evidence of action.

  • Scope: every system in the review, including service accounts, contractors and shared accounts.
  • An owner for each entitlement: a line manager or system owner who is accountable for the decision.
  • Risk context: leavers, dormant accounts, admin access and conflicting duties, so reviewers know what to look at first.
  • A recorded decision: keep or remove, who decided and when.
  • Evidence of action: proof that each removal was actually carried out.

Who should approve access in a user access review?

In a user access review, line managers should approve whether a person’s access still fits their role, and system or data owners should approve access to sensitive systems and privileged roles. Nobody should review their own access.

Review admin access more often than standard access, because it carries more risk.

How do you automate a user access review in Dimension?

To automate a user access review in Dimension by ThreatAware, a governed workspace for security applications, connect your identity and HR data, start from the User Access Review application in the App Library (opens in a new tab), and let it route each entitlement to its owner.

  1. Connect your data. Add feeds from your identity providers (group memberships and application assignments) and your HR system (each person’s role, manager and status). Dimension connects through each tool’s API and reads the data without changing it.
  2. Start from the App Library. Open the User Access Review application (opens in a new tab) and point it at your data, or paste its prompt into AI Composer to build your own version.
  3. Track the deadline. The review shows when sign-off is due and how many days are left.
  4. Route entitlements to owners. Every entitlement is routed to its owner for sign-off, with the highest-risk items first.
  5. Record every decision. Owners keep or remove each entitlement, and each decision is written to a tamper-evident audit log.
  6. Approve and action revocations. A person approves each removal before Dimension raises the ticket in your IT service management tool, and the review summary can be emailed when it closes.
  7. Hand over the evidence. The audit log gives your assessor a record of who decided what, and when.

The only changes Dimension makes outside itself are the tickets and emails a person approves. Access held inside an application rather than in your identity provider, such as local admin accounts or roles in a finance system, needs that application’s own data feed.

Which systems does an automated access review need data from?

An automated user access review needs data from three kinds of system: your identity provider, your HR system and your IT service management tool.

Tool category Common examples Used for
Identity provider (IdP) Microsoft Entra ID, Okta, Google Workspace, Ping Identity Group memberships, roles and application assignments for each person
HR system (HRIS) Workday, BambooHR, HiBob, SAP SuccessFactors Role, manager, team and leaver status
IT service management (ITSM) ServiceNow, Jira Service Management, Freshservice Raising a revocation ticket once approved (action)

Dimension connects to your systems through their APIs, so you can point the application at the tools you already run. The tools named here are common examples, not requirements.

Which access should a user access review flag first?

A user access review should flag leavers with active accounts, leftover access after team moves, conflicting duties, unusual access for a role, dormant accounts and admin access first.

  • Leavers with active accounts: people marked as left in your HR system who can still sign in.
  • Access left over after a team move: permissions from a previous role that were never removed.
  • Conflicting duties: combinations of groups or roles you define as conflicting, such as the access to raise and to approve payments.
  • Access unusual for the role: access that’s unusual for the person’s role.
  • Dormant accounts: accounts that haven’t been used for a long period.
  • Admin access: privileged roles, including contractors with admin rights.

How do you start with the User Access Review application?

To start with the User Access Review application, open it in the App Library of Dimension by ThreatAware and run it on your own data with a 14-day free trial, with no credit card. Dimension is ThreatAware’s governed workspace for security applications, and nothing changes in a live system without a person’s approval.

To build your own version, paste this prompt into AI Composer, or into Claude Code or another AI coding agent over MCP. The prompt names example tools, so swap in the ones you use:

Pull group memberships from Entra ID and application assignments from Okta, and match each person to their record in Workday. Owners keep or revoke each entitlement, with leavers, dormant and privileged access flagged first, every decision recorded for audit and a ServiceNow ticket raised for each revocation.

Run this application free (opens in a new tab)

Related

Frequently asked questions

About the author

Rob Jardine is Chief Marketing Officer at ThreatAware (opens in a new tab), the cybersecurity software company that builds Dimension. ThreatAware was founded in 2018, is ISO/IEC 27001:2022 certified and provides security software to more than 100 enterprise organizations across Europe and North America.

Sources

Statistic or fact Source
Credential abuse was the initial access vector in 13% of breaches Verizon 2026 Data Breach Investigations Report, executive summary: 19,905 breaches with a known initial access vector, October 2024 to November 2025
Microsoft Entra access reviews cover group memberships, enterprise applications and role assignments, and require Microsoft Entra ID Governance or Microsoft Entra Suite Microsoft Learn, “What are access reviews?”, last updated 12 March 2026
Review accounts at an organization-defined frequency (AC-2(j)); identify and document duties to separate (AC-5) NIST SP 800-53 Rev. 5, as reproduced in FedRAMP’s 2026 access control reference

Build it. Approve it. Run it.

Try Dimension free for 14 days on your own data, with no credit card. Plans start from $49 per month.