Cookie settings

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

Skip to content
Skip to content

Access mapping. Access governance. Access review.

Map who can reach your sensitive data, and record each decision.

IRIS links users, service accounts, roles and groups to the sensitive data they can reach, from each source’s grants, and records what your reviewers decide.

Six access records and the decision on each

Records from one scan dated November 7, 2026. Last-used dates on databases are per database account; the two file rows have no activity data.

Records
IdentityRole or groupObjectPrivilegeLast usedDecision
svc_loader (service account)etl_writerscbs.customer_master (PAN, mobile)INSERT and UPDATENovember 5, 2026Downgrade to SELECT; a second reviewer approved the task
hr_reportinghr_readershr.employee (SSN)SELECTJuly 16, 2026, past the 90-day defaultRevoke; the team moved to a new report
PUBLICEvery database rolecrm.person (email, mobile)SELECTNot applicableRevoke from PUBLIC; grant to a named role
ana.reviewer@example.comDirect grantcards.card_customer (holder name)SELECTOctober 21, 2026Keep: used within the 90-day default
Finance teamMicrosoft 365 groupFinance/Payroll folder (bank account numbers)EditNot measured: no activity data from this sourceKeep; the folder owner confirmed the members
Anyone with the linkOneDrive sharing linkHR/Offers/offer_letters.xlsx (salary)ViewNot measuredRemove the link
Capabilities

What access mapping covers

Dipal Panchal reads permissions on the data, because an application role tells you little: a “finance admin” could mean anything underneath.

Who has access

Links users, service accounts, roles and groups to sensitive data, from the grants each source exposes, as of the scan date.

Excessive access

Flags admin, owner and modify rights on sensitive data, broad groups and access granted to every role, with the identity and the data each one reaches.

Stale access

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

Open sharing links

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

Review decisions by scope

Reviewers record whether to keep, revoke, downgrade or time-limit access, with a reason. A second person approves each follow-up task.

Ranked by risk

Ranks access by the type of sensitive data and where it sits, so your reviewers start with the records that matter most.

Capabilities vary by edition.

How it works

How access mapping works

  1. Connect

    Connect each source with an account that can read its grants and the data in scope.

  2. Read permissions

    IRIS reads users, service accounts, roles, groups and grants where the source exposes them.

  3. Flag

    IRIS flags admin rights, broad groups and open links, and stale access where activity is recorded.

  4. Review

    Reviewers record whether to keep, revoke, downgrade or time-limit access, with a reason.

  5. Change and re-scan

    Your team changes access in the source system. A re-scan records the new grants.

In the product

Access mapping and review

Access mapping and review

Admin and modify rights on sensitive data

Users, service accounts, roles and groups with access to sensitive data, counted and linked to the data they reach. Review progress shows for each identity and scope.

  • Stale access past the 90-day default or a period you set, where the source records activity
  • Review progress for each identity and scope
Explore access review
IRIS access overview card counting the users and accounts with sensitive-data access, split into users, service accounts, roles and groups
Access to sensitive data counted by users, service accounts, roles and groups.
Sources

Permissions read from the sources you connect

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

  • Databases such as PostgreSQL, SQL Server, Oracle and Snowflake
  • Sharing on OneDrive, SharePoint and Google Drive
Explore integrations
IRIS connected sources panel listing PostgreSQL, OneDrive, Google BigQuery and SharePoint connections with their connection counts and last use
Your connected sources in one place, with their connection counts and when each was last used.
Questions

Three questions an access review must answer

Which accounts can read customer data?

Service accounts, users, roles and groups, each linked to the sensitive tables and files it can reach, including grants made to every role.

Is this access excessive or unused?

Rights beyond read are flagged on sensitive data, and unused access where the source records activity.

Who approved this access, and why?

Each review decision is recorded with the reviewer, the reason and the date, and follow-up tasks need a second approver.

Overview

What the access view can’t tell you

IRIS shows who can reach sensitive data. Where the source keeps an audit log, IRIS reads it and shows who accessed that data and when. Activity data also feeds the stale-access flag.

A grant shows up only if the source exposes it to the account IRIS reads with, so give that account read access to the grant catalogs. Where a source records no activity, the record says not measured.

To see where access mapping runs in a scan, follow one on the how-it-works page.

FAQ

Questions about access mapping

Protect your brand. Start with your data.

See access mapping, or start with a free assessment of one database.