Cookie settings

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

Skip to content
Skip to content

AI access. Data access review.

See what sensitive data the accounts behind your AI tools can reach.

AI assistants and agents read data through accounts you already granted. List those accounts, and IRIS shows the sensitive data each one can reach.

The challenge

An AI tool inherits the access behind it

The model is rarely the risk

Dipal Panchal, co-founder and CEO, puts the risk in the data an AI tool can reach and the access around it, not in the model.

Grants made for another job

A service account set up for a nightly report can be handed to a new assistant, and every grant it holds comes with it.

Uploads nobody sees

Dipal Panchal notes that many companies give enterprise AI licenses to every employee, who may then upload spreadsheets and PDFs holding company data without the company knowing.

Six accounts reviewed before an AI rollout

Four AI accounts, one rejected and Copilot excluded. Last-used dates come from sources that record activity; on PostgreSQL, activity is tracked per database account unless audit logging is turned on.

Records
IdentityRole or groupObjectPrivilegeLast usedDecision
svc_support_bot (support assistant)support_readerscrm.person (email, mobile)SELECTNovember 7, 2026Narrow to a view without mobile numbers. Reviewed by the CRM owner
svc_rag_indexer (document search assistant)Direct grantcbs.customer_master (PAN, date of birth)SELECTOctober 30, 2026Revoke by November 22: it answers product questions and needs no customer IDs
svc_fraud_model (model training pipeline)ml_feature_readerscards.card_accounts (card number)SELECTNovember 5, 2026Keep: the protection check, activated on this install, found the sampled card numbers masked
svc_analytics_agent (warehouse agent)analytics_writersanalytics.customer_snapshot (date of birth)SELECT, INSERTPer database account only: audit logging is offDowngrade to SELECT: the agent has no reason to write
svc_etl_nightlyetl_writerscrm.person (email)INSERT, UPDATENovember 8, 2026Not an AI account: it runs the nightly load, so the normal access review covers it
Microsoft CopilotEach user’s own permissionsSharePoint and OneDrive filesNot an account IRIS mapsNot applicableExcluded: it answers with each user’s access, so the review moves to the files’ sharing
Questions

The first question before go-live

Before an AI assistant or agent goes live, Dipal Panchal’s first question is what data it can reach, at what permission, and whether it reads the values in full. The table above answers it one account at a time, with the reviewer’s decision beside each.

Our rule for a rollout: no assistant goes live on an account that can write, or that reaches restricted data stored in plain form. Each exception gets a named owner and a review date before the launch, written into the review sheet.

What you get

What the review gives you

The grants behind each account

For each account you list, the sensitive tables and files it can reach, and whether it holds admin rights over them.

How the data in reach is stored

Whether the sensitive values it can reach are stored in plain form, from a check on sampled values that runs once it is activated on your install.

How it works

Review the accounts before the launch date

List the accounts your AI tools run as, then run one scan of the sources they read: the how-it-works page follows that scan, and the access review page shows the sheet your reviewers sign.

Capabilities

What IRIS checks for each account

An account an AI tool runs as is mapped like any other account, from the permissions each source exposes.

Data in reach

Links each service account to the sensitive data it can reach, from table and view grants on databases and sharing on OneDrive and Google Drive.

Admin rights on sensitive data

Flags admin rights on sensitive data, which an agent shouldn’t hold unless administering that data is its job.

Protection of what it reads

Checks sampled values for encryption, masking or hashing, once the check is activated on your install, and flags sensitive values stored in plain form.

A decision for each account

Reviewers keep the access, or mark it for downgrade or revocation, with a reason; your team makes the change in the source, and a re-scan records the new grants.

Capabilities vary by edition.

Overview

What IRIS doesn’t do for AI

IRIS doesn’t discover AI tools or agents, and keeps no inventory of models. It doesn’t read prompts or outputs, it can’t see what staff upload to an AI service, and it blocks nothing.

Nor does it connect to Microsoft Copilot (formerly Microsoft 365 Copilot). Copilot surfaces only the data each user already has permission to view, as Microsoft documents it, so its review is a review of who can open which files.

FAQ

What teams ask before an AI rollout

Protect your brand. Start with your data.

Bring the list of accounts your AI tools run as. We’ll show what each one can reach today.