Cookie settings

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

Skip to content
Skip to content

Access mapping. Access review.

Review who can reach sensitive data, and keep each decision.

IRIS links accounts to the sensitive data they can reach and flags excessive and stale access. Your reviewers record a decision and a reason for each.

The challenge

Why access reviews start from spreadsheets

Spreadsheet prep for each review

Dipal Panchal: “At CBRE, I managed three to five applications with a team of over 200 people.” He remembers the prep each access review took, tracked in manual Excel sheets of who needed what.

Approvals in four places

In Dipal Panchal’s enterprise roles, approvals sat in Okta, Azure, ServiceNow and custom steps inside single applications, so people didn’t know where to ask.

IT lacks the business context

When Dipal Panchal asked who could reach a dataset, the answer was “IT handles that,” though IT didn’t know which analyst needed payroll data, or for how long.

Six rows from one access review, decided

Records from a quarterly review on November 8, 2026: each decision names who made it, and no one reviews their own access. Last-used dates come from the sources that record activity, and the stale-access card below gives the PostgreSQL condition.

Records
IdentityRole or groupObjectPrivilegeLast usedDecision
svc_reporting (service account)bi_readerscbs.customer_master (PAN, India’s tax ID; date of birth)SELECTNovember 6, 2026Keep: the nightly report needs it. Reviewed by the core banking data owner
priya.ops@example.comops_supportcards.card_accounts (card status, last four digits)SELECT, UPDATEAugust 2, 2026, past the 90-day defaultDowngrade to SELECT by November 22. Reviewed by the cards product owner
contractor.dev@example.comDirect grantanalytics.customer_snapshot (PAN)SELECTJune 30, 2026, past the 90-day defaultRevoke by November 15: the contract ended. Reviewed by the data platform lead
r.mehta@example.comfinance_adminsfinance.payroll (bank account number)SELECT, UPDATEOctober 29, 2026Reassigned: the reviewer holds this access, so the finance data owner decides it
hr_analysthr_readershr.employee (salary)SELECTPer database account only: audit logging is offKeep for one more quarter; turn on audit logging first. Reviewed by the HR data owner
HR system usersApplication rolesHR system (SaaS)Not readUnknownExcluded: the HR system isn’t connected, so its own review runs in that tool
Requirements

What the standards ask of a review

PCI DSS v4.0.1, Requirement 7.2.4, calls for a review of all user accounts and their privileges, third-party accounts included, at least once every six months, with inappropriate access addressed and management acknowledging the result. ISO/IEC 27001:2022 control A.5.18 has access rights provisioned, reviewed, modified and removed under your access control policy.

For SOC 2, the Trust Services Criteria of the American Institute of CPAs (AICPA) cover removing access no longer authorized (CC6.2), and least privilege with segregation of duties (CC6.3). Each row in the sheet above names who decided, and each downgrade or revoke names the date it is due.

Our rule on top: the data owner signs each row, never the account holder, and a revoke is due no later than two weeks after the decision. A re-scan once that date has passed shows whether the grant is really gone from the source.

What you get

Where IRIS fits in a review you already run

Beside an identity governance tool

An identity governance and administration (IGA) tool certifies the roles and groups it has connectors for. IRIS adds the sensitive tables and files each account can reach in the source itself.

A re-scan after the due date

After your team changes the grant in the source, run a new scan. It records the grants as they stand on its own date, so the revoke can be checked against the decision.

Capabilities

What IRIS reads and flags for the review

Access comes from each source’s own permission data, read with the account you create for IRIS.

Who can reach sensitive data

Links users, service accounts, roles and groups to sensitive data: from table and view grants on databases, and from sharing on OneDrive and Google Drive.

Excessive access

Flags accounts with admin rights on sensitive data, so the review can open with them.

Stale access

Access unused past the 90-day default, or a period you set, is flagged where the source records activity. On PostgreSQL, activity is tracked per database account unless audit logging is turned on.

Files open to anyone with the link

Flags OneDrive and Google Drive files holding sensitive data that anyone with the link can open.

Decisions with a reason

Reviewers keep access, or mark it for downgrade or revocation, with a reason. Each decision is kept against the account and source it covers.

A fresh read each quarter

Scans run on demand or on a schedule, so each quarterly review starts from grants read in that quarter.

Capabilities vary by edition.

Overview

What the review can’t show

IRIS shows who can reach the data and, where the source keeps an audit log, who accessed it and when. It doesn’t grant or revoke access: your team makes the change in the source.

It reads permissions on the data sources themselves, so a role defined only inside an application, such as an enterprise resource planning (ERP) finance role, is reviewed in that application. Today reviews run per scope, with the decision and reason kept in the audit history. Scheduled campaigns and reminders aren’t in v1, so your team keeps the review calendar.

Frameworks

The laws and frameworks behind each review

HIPAA §164.308(a)(4): access authorization policies. GDPR and UK GDPR Article 32: security fit to the risk. DPDP Act section 8(5): reasonable safeguards.

For SOC 2, ISO/IEC 27001, PCI DSS and UK GDPR, IRIS maps the review sheet to their controls. A scored readiness view for access reviews isn’t in v1; ask us if you need one.

How it works

Start the first review on one database

Pick a database your auditor sampled last time and run one scan; access mapping runs after it. The how-it-works page shows where the grants are read, and the access mapping page shows the access view your reviewers decide from.

FAQ

Questions about access review

Protect your brand. Start with your data.

Bring the spreadsheet from your last access review. We’ll show the same rows built from your grants.