Cookie settings

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

Skip to content
Skip to content

How it works. Read-only discovery.

Follow one scan from the connected source to evidence you can check.

IRIS reads your sources, classifies locally and records what it couldn’t read. The coverage record below is one scan of sources, filled in.

The coverage record from one scan

One run across a six-source estate. One table and two files went unread and one source failed, so IRIS marks the whole run partial.

Records
SourceStatusReasonOwner
Core banking databaseScanned: 3 of 3 tablesEvery table readCore banking DBA
Cards databaseScanned: 2 of 2 tablesEvery table readCards platform owner
CRM databasePartial: 1 of 4 tables unreadcrm.person_archive timed out; its columns stay unclassified until a re-scan reads themCRM application owner
HR document libraryPartial: 2 of 148 files unreadOne file is password-protected and one is too large to readHR operations lead
Loans archive databaseFailedThe host was unreachable from IRIS, so no table was readLending platform owner
Treasury databaseExcluded by scopeLeft out at scoping; listed so the gap stays on the recordTreasury systems owner
Capabilities

What each scan does

Dipal Panchal’s rule for the report: show which sources are connected and which were scanned, and say that the results come only from those.

Classify sensitive data

Classifies sampled values and column names with pattern rules, checksums such as Luhn for payment cards, and local name recognition.

Map who can reach it

Maps who can reach each sensitive location from the source’s own grants, where it exposes them. Flags excessive access, and stale access where activity is recorded.

Check how it is protected

Checks sampled values in each sensitive column for encryption, masking or hashing, once the check is activated on your install, and flags plain values to fix.

Record the coverage

Records each source’s outcome, scanned, partial, failed or excluded, with the reason for each table and file IRIS couldn’t read.

Capabilities vary by edition.

How it works

The path from source to evidence

This reflects IRIS v1 as checked on November 8, 2026. Scans run on demand or on a schedule, and each run is dated.

  1. Scope and connect

    Sources in scope, gaps recorded, each connection tested

  2. Inventory

    Schemas, tables, columns and files

  3. Classify

    Sensitive data and signs of protection

  4. Map access

    Who can reach each sensitive location

  5. Review

    Your team verifies or dismisses each finding

  6. Evidence

    Evidence for audits; re-scan after a fix

  7. Evidence register
  1. Scope and connect

    Sources in scope, gaps recorded, each connection tested

  2. Inventory

    Schemas, tables, columns and files

  3. Classify

    Sensitive data and signs of protection

  4. Map access

    Who can reach each sensitive location

  5. Review

    Your team verifies or dismisses each finding

  6. Evidence

    Evidence for audits; re-scan after a fix

  7. Evidence register
Six steps from source to evidence, ending at the evidence register. Steps 02 and 03 run inside your IRIS deployment.
Classification and checks run within your own IRIS deployment.
In the product

What your team sees after a scan

Real IRIS screens.

Connect and inventory

Every connected source in one place

Connect supported databases, cloud storage, Microsoft 365, Google Workspace and selected SaaS and code platforms, with read-only access. Each connection is tested before use.

  • Each connection reports connected, partial or failed
  • We confirm what IRIS can read before any scan
Explore integrations
IRIS connected sources panel listing PostgreSQL, OneDrive, Google BigQuery and SharePoint connections with their connection counts and last use
The connected sources, each with its connection count and last-used date.
Discover and classify

Each finding tied to its source

Findings by source, schema, table and column. Each carries a confidence level and a review status, and stays pending until a reviewer decides it.

  • Each scan lists what was scanned, what failed and what was excluded
  • Files IRIS couldn’t read listed with the reason
Explore discovery
IRIS results table listing classified columns with their database, schema and table
A finding shown with the source, schema and table it was read from.
Questions

Questions your IT team asks

What does IRIS read and keep?

It reads a sample of each table, and small tables in full, plus the files in scope. It keeps findings and coverage records in your deployment.

What connects outbound?

From IRIS: the license service at activation and validation, the sources you scan, a time source, and emailed reports if you turn them on. The security pack lists the rest.

What does it need from you?

A host in your environment, an account for each source that can read the catalog and the data in scope, and one online license activation.

Which access counts as stale?

Access with no recorded use past the 90-day default, or a period you set. On PostgreSQL, activity is tracked per database account unless audit logging is turned on.

Overview

Classification you can verify

IRIS matches values and column names against patterns for global and regional identifiers. For the nine identifier types with a checksum, such as Luhn for payment cards or Verhoeff for Aadhaar, IRIS validates it. A column whose sampled values all fail is rejected for that type.

Name recognition runs on a local model inside your deployment. Each machine finding starts as pending, and a reviewer approves, reclassifies or declines it, giving a reason for a decline.

To plan the install that runs these steps, read the deployment page: the host, a read-only account for each source and the activation step.

FAQ

Questions about how IRIS works

Protect your brand. Start with your data.

Take the product tour, or book a demo and bring the source your auditor asks about most.