Cookie settings

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

Skip to content
Skip to content

Data security governance

Your sensitive data. See it. Control it. Protect it. Prove it.

IRIS shows what sensitive data you have, who can reach it and where protection is missing. After your team’s fix, a re-scan shows whether the state changed.

  1. Your sourcesDatabases, cloud storage, Microsoft 365, Google Workspace and selected SaaS. Read-only access, in your environment.
  2. IRIS checksSensitive data found. Excessive and unused access flagged. Unprotected values flagged. Every scan dated.
  3. Your team acts in the sourceEncrypt, mask or hash values. Remove or downgrade access.
  4. Protected, and confirmed on re-scanValues now encrypted, masked, hashed or tokenized. Unwanted access removed.The same dated record is your audit evidence
Re-scan
A stack of three layers, read from the bottom up: your sources, IRIS checks, and the protected result once your team acts in the source. A dashed re-scan loop runs from the top layer back to IRIS checks.

Teams we’ve worked with

  • Operlity
  • SecComply
  • SecureKal
  • WITS Innovation Lab
  • Zucol
Proof

Used in paid work and proofs of concept

  • 4

    paid engagements

  • 3

    proofs of concept

  • 100+

    years of combined experience

    In data, security and enterprise technology, across the team

The challenge

From sensitive data to a confirmed fix

IRIS answers four questions in order: what sensitive data you have, who can reach it, where protection is missing, and whether the fix changed the result.

First scan: what IRIS records

EmailPlain: jane.doe@example.com
Card numberPlain: 4111 1111 1111 1111
PassportPlain: K8306152
Health notePlain: Type 2 diabetes
Your team fixes it, then IRIS re-scans

Re-scan: the new state

EmailMasked: j•••@example.com
Card numberMasked: •••• •••• •••• 1111
PassportEncrypted
Health noteEncrypted
The same record in two scans. In the first scan its email, card number, passport number and health note are stored in plain form. After your team protects them and IRIS re-scans, it records the email and card number as masked and the passport number and health note as encrypted.

Data nobody listed

“Every quarter in my last enterprise role, I would have sworn I knew where our sensitive data was. Every quarter, the audit found something new.” Dipal Panchal, CEO

Access nobody reviewed

Shared service accounts and permissions granted for one project still work after it ends, and nobody has reviewed them since.

Fixes nobody confirmed

A closed ticket isn’t proof that the risk changed. A successful re-scan is.

Platform

Four pillars, one question each

Use cases

Before AI tools reach your data

Mark the accounts your AI tools use, and IRIS shows what data they can reach.

Accounts AI tools use

Your team marks the accounts your AI tools use. IRIS shows the sensitive data each one can reach and flags admin rights and broad access. It doesn’t read prompts or outputs.

Files shared too widely

Before you switch on an AI assistant, find sensitive files in Microsoft 365 shared through public links or broad groups.

Data before it feeds AI tools

Scan the store a dataset lives in to see what sensitive data it holds, and check its sampled values for encryption, masking or hashing.

How it works

How IRIS works, in five steps

The table follows six findings through the same sequence, from the first scan to the re-scan after a fix.

  1. Scope

    Choose sources; gaps are recorded

  2. Connect

    Read-only where the source allows; each tested

  3. Scan

    Classify, map access, check protection

  4. Review

    Approve or decline; a decline needs a reason

  5. Evidence and re-scan

    Export, fix, re-scan

    Re-scan after a fixRe-scan after a fix
What a first scan flags, what it rejects or couldn’t read, and what a re-scan records after your team’s fixes.
Data typeWhereWho can accessFoundAfter the fix and re-scan
Email addressAWS S3 · customer-exportsSupport, FinanceNot protectedMasked
Passport numberMicrosoft 365 · HR folderHR team, all staffExcessive accessAccess removed
Card numberPostgreSQL · billingbilling-svc (service account)Not protectedEncrypted
National IDGoogle Workspace · onboardingAnyone with the linkShared by linkLink removed
Card number (candidate)PostgreSQL · ordersNot assessedRejected by the reviewer: order numbers that pass Luhn by chanceNo action needed
Not classifiedMicrosoft 365 · payroll folderNot assessedNot read: the file is password-protectedListed as a gap until it’s readable
In the product

What you’ll have after the first scan

Every record carries its scan date, and a re-scan adds the new state beside the old one.

Discover and classify

An inventory you can check

Sensitive data by source, schema, table and column, with the source recorded for each finding. Each one carries a confidence level and a review status for your reviewers to check.

  • Coverage on the record: scanned, failed and excluded
  • Files IRIS couldn’t read are listed with the reason
Explore discovery
IRIS results table listing classified columns with their database, schema and table.
Each finding is tied to its exact source, schema and table.
Access mapping and protection checks

An access and protection view

Excessive access is flagged, and stale access where the source records activity. On PostgreSQL, activity is tracked per database account unless audit logging is turned on.

  • Protection checked on sampled values, once activated on your install
  • Findings ranked by risk, so your team fixes the worst first
Explore access
IRIS access overview card counting the users and accounts with sensitive-data access, split into users, service accounts, roles and groups.
Who can reach sensitive data, counted by users, service accounts, roles and groups.
Audit evidence and compliance

An evidence register

Findings mapped to controls, for your team to review and share with an auditor, a regulator or a customer. Every scan is dated, and a re-scan records what changed.

  • Mapped to GDPR, CCPA/CPRA, HIPAA and the other supported frameworks
  • Executive, technical, compliance and risk reports
Explore evidence
IRIS compliance overview with scores for CCPA/CPRA, India’s DPDP Act and GDPR, and a control gap that affects several frameworks.
Framework scores, and the control gaps that affect several frameworks at once.
Capabilities

What IRIS covers today, with the conditions

Applies to IRIS v1; checked November 8, 2026. Coverage differs by source; we confirm what IRIS can read before any scan. Capabilities vary by edition.

  • 12

    database and warehouse engines

    Including PostgreSQL, SQL Server, Oracle, Snowflake and SAP HANA

  • 103

    built-in data types

    Global, US and Indian formats, from IBAN to NPI and Aadhaar

  • 15 min*

    to scan a structured source

  • 373

    controls in one unified framework

    Mapping shows relevance; your auditors judge whether a control is met.

  • *About 100 tables, reading a sample of each table. Time depends on the number of tables and columns, not table size.

Deployment

Runs where your data lives

IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment.

Sources you connect

Databases
Cloud storage
Microsoft 365
Read-only

Your environment

Web app
Scan worker
IRIS database
Audit trail
Occasional

Outbound connections

License serviceAt activation and validation
SaaS sources you scanDuring their scans
Time sourceHost clock; can be your own
Your sources connect through read-only accounts where the source offers one, to your environment, which runs the IRIS web app, scan worker, IRIS database and audit trail. Outbound, IRIS reaches the license service at activation and validation, and the cloud and SaaS sources you scan during their scans; the host also syncs its clock with a time source.
Read-only accounts where the source offers one. Outbound connections are shown by kind; the architecture page gives each one’s evidence status.
Who it’s for

What each role gets from the same scan

CISOs

See what was assessed, what was missed, what’s exposed and what you can defend.

DPOs and privacy teams

A source-linked record of the sensitive data you hold and where it sits, refreshed with each scan.

Compliance and audit

Audit the data itself, not only the spreadsheet describing it.

IT and data teams

Read-only accounts where the source offers them, deployable in your environment, agentless where the source supports it.

Frameworks

Findings mapped to six frameworks

Six frameworks mapped through one unified control framework, from GDPR and HIPAA to India’s DPDP Act and SEBI CSCRF.

The chips link to our law guides. For UK GDPR, UAE PDPL and Saudi PDPL, IRIS produces evidence that supports your assessment; a dedicated pack isn’t available today.

Use cases

Where sensitive data hides, sector by sector

Four situations where a copy sits outside the inventory, and what a scan of the connected sources shows in each.

Logistics

Find data in scanned papers

Branch teams scan bills of lading, customs papers and driver documents into shared folders. Each branch names them differently, and nobody keeps a list.

With IRIS

Text recognition reads the scanned PDFs and images in connected drives and cloud storage, and files it couldn’t read are listed with the reason.

Healthtech

Check a de-identified extract

Teams remove names from a patient extract before reuse, but dates of birth, postal codes and rare diagnoses can still point to one person.

With IRIS

IRIS lists the sensitive fields left in the extract, column by column, so the team can decide what else to remove.

Insurance

Limit what each partner gets

Full claim files go to medical reviewers and payment processors, though each one needs only part of the file.

With IRIS

The claims owner sees which sensitive fields sit in the claims source and the partner exchange folder, and agrees a field list for each partner.

Professional services

Find client extracts left behind

Consultants copy a client’s HR extract into a project workspace for an analysis. When the project ends, the extract stays.

With IRIS

A scan of the connected workspace finds the extract, its sensitive fields and who can reach it.

Partners

IRIS in a partner’s words

Prashant BahugunaProgram Manager, WITS Innovation LabTechnology partner and IRIS user
FAQ

Common questions about IRIS

IRIS finds sensitive data in the supported sources you connect, shows who can reach it where permission evidence is available, and checks whether it’s protected. It also produces source-linked evidence you can put in front of an auditor, a regulator or a customer’s security team.

Protect your brand. Start with your data.

Start with a free assessment of the one database your auditor asks about most, or book a demo.

Video: a technology partner on IRIS

The video plays in YouTube’s privacy-enhanced player once you accept Functional (video) cookies.