Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Category comparison. Access governance.

Identity governance vs data access governance: where access reviews belong

What each one governs, what it reads and what a reviewer signs off, traced through one leaver and one service account.

By Dipal Panchal, co-founder and CEO · Updated November 8, 2026

Overview

One starts from the person, one from the data

Identity governance and administration (IGA) manages identities and their access across the organization: who joins, moves and leaves, and which accounts, roles and entitlements each one holds. Data access governance knows who can reach sensitive data and decides whether they should, with a record of each decision.

Keep manager reviews of roles in your IGA program, and add owner reviews of who can reach each sensitive store. An IGA review asks a manager whether a person still needs a role. A data access review asks a data owner whether this access to this data is still right.

Explore data access governance
Compare

IGA and data access governance side by side

Cells describe the typical IGA or access governance tool, and the NIST Cybersecurity Framework (CSF) row is our reading.

IGA and data access governance side by side
AspectIdentity governance (IGA)Data access governance
Acts onThe identity: a person or service, and the accounts it holdsThe data: a sensitive table, bucket, folder or file
Question it answersDoes each person have the right accounts and roles for their job?Who can reach this sensitive data, and should they?
Main strengthJoiner, mover and leaver processes and role-based requests at scaleSeeing the rights inside each data store, including grants made outside any workflow
What it cannot doSee rights inside databases and file shares, below the application roleExplain why a person was given access, or run the joiner, mover and leaver process
Best fitOrganizations that grant access through application rolesTeams that must show who could reach specific sensitive data
A typical scenarioA manager certifies that an analyst still needs a reporting roleA data owner removes a direct grant on a claims table
Where it runsConnects to directories, HR systems and applicationsA scanner that reads permissions in each data store with an account you grant
What it readsIdentity directories, HR records and application entitlements, often at role or group levelPermissions inside each data store: grants, roles, groups, sharing links and inherited rights
Service accountsNot managed through joiner, mover and leaver events, so they need a process of their ownTreated like any other identity: which data the account can reach, and who owns it
Closest NIST CSF 2.0 outcomePR.AA-01 identities and credentials, and PR.AA-05 access permissionsPR.AA-05 access permissions and least privilege, applied to the data itself
Use cases

A leaver and a service account, traced

Suppose an analyst left on October 31 and a reporting service account has run for years. Both can reach a claims database.

A leaver and a service account, traced
CaseIGA seesData access governance sees
The leaver’s roleThe HR feed ends the person; directory account and application roles are removedThe same, read from the data side: no role-based access remains
A direct grant the leaver heldNothing, because the grant was made in the database outside any workflowA login still holding read on the claims table, with the scan date
The service accountListed only if someone onboarded it with an ownerListed with the sensitive tables it can reach, for the data owner to keep, downgrade or remove
The decisionA manager certifies or revokes a roleThe data owner records keep, revoke, downgrade or time-limit, with a reason
What the auditor retestsWho held which role and who certified itWho could reach the data on a scan date, and the owner’s decision for each identity
Who it’s for

When one is enough, and when you need both

IGA alone is enough when

Access to sensitive data is granted only through application roles, and your role definitions already say which data each role can reach.

Data access reviews alone fit when

You have no IGA program yet, and the question in front of you is who can reach a handful of sensitive databases or shared drives.

You need both when

IGA manages who joins, moves and leaves. Data access governance checks what that access reaches inside each store, including grants made outside IGA.

Requirements

What to test in a proof of concept

Create the leaver case on purpose, then ask each tool to find it.

  • Create a test database login with read on one table, and give it no directory account.
  • Ask whether the tool lists the login and the table it can reach.
  • Add a service account and check who the tool shows as its owner.
  • Revoke the grant, re-run the tool and check that the change is dated.
Capabilities

How IRIS fits

IRIS links users, service accounts, roles and groups to sensitive data they can reach.

Who has access

IRIS reads permissions where the source exposes permission data, and links users, service accounts, roles and groups to sensitive data.

Excessive and stale access flagged

IRIS flags broad rights on sensitive data, and stale access past the 90-day default or a period you set, where the source records activity. PostgreSQL tracks it per account unless audit logging is on.

Review decisions by scope

For each grant, the reviewer picks keep, revoke, downgrade or time-limit, and writes the reason. Another person signs off every follow-up task.

Decisions on the record

Review decisions are kept in the audit history with their reasons, and every scan is dated.

Capabilities vary by edition.

Official sources

  1. The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, NIST. Opened November 8, 2026.
FAQ

IGA and data access governance questions

Protect your brand. Start with your data.

Create the leaver test on one database this week, then book a demo to see the same review in IRIS.