Cookie settings

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

Skip to content
Skip to content

Data security governance. Evidence-first DSPM.

Find sensitive data, map who can reach it and keep the evidence.

IRIS finds sensitive data in the sources you connect, shows who can reach it and checks whether it’s protected. Every finding links to its source.

Platform

How the platform fits together

From the sources you connect to the evidence you hand an auditor. Classification and checks run inside your IRIS deployment.

Sources you connect

  • Databases
  • Cloud storage
  • Microsoft 365
  • Google Workspace
  • SaaS and code
IRISRead-only access · Each connection tested

See it

Discover and classify
Data catalog

Control it

Access mapping and review
Access review decisions

Protect it

Protection checks
Risk scoring

Prove it

Audit evidence and compliance
DSAR and purpose
  • What you get
  • Coverage record
  • Evidence register
  • Framework reports
  • Re-scan after a fix
  • Deployed in your infrastructure
  • Read-only access
  • Dated, repeatable scans
  • Scope and gaps on the record

Sources you connect

  • Databases
  • Cloud storage
  • Microsoft 365
  • Google Workspace
  • SaaS and code
IRISRead-only access · Each connection tested

See it

Discover and classify
Data catalog

Control it

Access mapping and review
Access review decisions

Protect it

Protection checks
Risk scoring

Prove it

Audit evidence and compliance
DSAR and purpose
  • What you get
  • Coverage record
  • Evidence register
  • Framework reports
  • Re-scan after a fix
  • Deployed in your infrastructure
  • Read-only access
  • Dated, repeatable scans
  • Scope and gaps on the record
Sources you connect (databases, cloud storage, Microsoft 365, Google Workspace, selected SaaS and code) feed IRIS, with read-only access and each connection tested. IRIS branches directly into four pillars, in no order: See it (discover and classify, data catalog), Control it (access mapping and review, access review decisions), Protect it (protection checks, risk scoring) and Prove it (audit evidence and compliance, DSAR and purpose). What you get: coverage record, evidence register, framework reports, re-scan after a fix. Deployed in your infrastructure; read-only access; dated, repeatable scans; scope and gaps on the record.
Capabilities vary by edition.
Capabilities

One platform, four pillars

Each pillar answers a question an auditor, a regulator or a customer will ask, within the sources you connect.

See it

Find and classify sensitive data in the sources you connect, with pattern rules, checksums and local name recognition.

  • Discovery and classification across databases and files
  • A data catalog with owners, purpose and retention
  • A coverage record: scanned, partial, failed and excluded

Control it

See who can reach your most sensitive data, from the grants in each source that exposes permission data.

  • Users, service accounts, roles and groups linked to findings
  • Excessive-access rules, such as public access to sensitive data
  • Stale access flagged where the source records activity

Protect it

Check sampled values for encryption, masking or hashing, once the check is activated on your install, so your team can close the gaps.

  • Values stored in plain form, flagged column by column
  • Risk scored from sensitivity, protection and access
  • Encryption-at-rest settings checked on 9 database engines

Prove it

Turn the sensitive-data part of an audit into an evidence register, each row traced to its scan and source.

  • An evidence register you can export as CSV or XLSX
  • Six frameworks mapped through one unified control framework
  • Re-scans that record the condition after a fix
Compare

Where IRIS sits in your security program

Data security posture management (DSPM) tools find sensitive data and show where the risk sits. Data security governance and management (DSGM) adds what an auditor asks next: what was checked, what was left out, who owns it and how you know.

IRIS builds that record from the connected systems. Each scan is dated, each finding links to its source, and the sources and tables it couldn’t read stay on the record.

Data security has four parts: people and skills, policy and process, technology, and assurance. IRIS is one component of the technology, alongside the tools you already run.

Read the DSGM guide
In the product

The platform

Real IRIS screens, from the first finding to the evidence for an audit.

Discover and classify

Find out what data you hold and where it sits

Personal-data records grouped by category across the sources you connect. Each finding behind a category links to its source and scan, for your reviewers to check.

  • 103 built-in data types for Indian, US and global formats
  • 9 identifier types checked by checksum, such as Luhn for cards
Explore discovery
IRIS data categories chart splitting personal-data records into financial, contact, personal, location and health data
Personal-data records by category, from financial and contact data to health.
Access mapping and review

See who can reach sensitive data

IRIS links users, service accounts, roles and groups to the sensitive data they can reach. On PostgreSQL, activity is tracked per database account unless audit logging is turned on.

  • Excessive-access rules, such as public access to sensitive data
  • Access unused beyond the 90-day default, or a period you set, where the source records activity
Explore access
IRIS access overview card counting the users and accounts with sensitive-data access, split into users, service accounts, roles and groups
The users, service accounts, roles and groups that can reach sensitive data, with counts.
Audit evidence and compliance

Map findings to your frameworks

Findings map to controls in one unified framework, with a score per framework. Mapping shows relevance; your auditors judge whether a control is met.

  • A score per framework, and the gaps that affect several
  • Reports for executive, technical, compliance and risk readers
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 cut across several frameworks.
Capabilities

Built into IRIS today

Coverage differs by source. We confirm what IRIS can read in your environment before any scan.

  • 12

    database and warehouse engines

    Including PostgreSQL, MySQL, BigQuery, Databricks and SAP HANA

  • 103

    built-in data types

    For Indian, US and global formats

  • 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.

How it works

One finding, from scope to re-scan

One column traced through the five steps every scan follows, first assessment or re-scan.

  1. Scope

    Core banking database in scope; the treasury database left out and recorded as a gap.

  2. Connect

    The read-only login for the core banking database is tested and shows as connected.

  3. Scan

    cbs.customer_master.pan: PAN (India), restricted, stored in plain form, readable by two roles.

  4. Review

    The data owner approves the finding on November 3, 2026, with the reason “live customer PANs”.

  5. Evidence and re-scan

    The register row is exported. After the team masks the column, a re-scan detects it as masked.

FAQ

Where to start, and where IRIS stops

Protect your brand. Start with your data.

Book a demo to walk through IRIS, or see what an evidence record holds in the sample report.