Cookie settings

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

Skip to content
Skip to content

Sensitive data discovery. Shadow data.

Find the copies of sensitive data your inventory missed.

A restored staging database holds production’s customers and is often missing from the inventory. IRIS finds such copies in the sources you connect.

The challenge

Where the inventory and the data part ways

The report covers declared systems

In Dipal Panchal’s talks with chief information security officers (CISOs), the systems missing from their reports are test and development environments, small applications and tools bought on a card.

Copies leave the consent behind

Consent is stored in the application that collected the data. Of carrying it into replicas and the warehouse along with the data, Dipal Panchal says: “Ideally, no company does this.”

Test databases sit outside the program

Test and development databases are generally left out of the compliance program, as Dipal Panchal puts it. A restore from a production backup brings real customer records into that test database.

Six places copies collect, and each decision

Records from one scan across six places copies collect. IRIS finds the sensitive columns and files; your team adds the reason each is a copy, and the owner’s decision.

Records
SourceLocationDetected typeWhySensitivityDecision
Staging databasecrm_staging.person.emailEmail addressRestored from a production backup for testing; the rows match crm.personConfidentialOwner: CRM lead. Replace with test values, then re-scan
Analytics warehouseanalytics.customer_snapshot.aadhaarAadhaar numberLoaded nightly from the core banking database, without its consent fieldsRestrictedOwner: data platform lead. Keep; limit reads to two named roles
Amazon S3 bucketops-exports/2026-10/cards_reconcile.csvPayment card numberA support export for a reconciliation whose ticket closed in OctoberRestrictedOwner: payments operations. Delete the file and re-scan the bucket
SharePoint siteFinance/Shared/loan_extract_q3.xlsxBank account numberCopied out of the loans system for a quarter-end reviewRestrictedOwner: finance controller. Move it back into the loans system
QA databaseqa_checkout.payments.card_numberPayment card numberThe values are processor test numbers such as 4111 1111 1111 1111, not customer cardsNoneRejected by the reviewer, with that reason
LaptopsDownloads and Desktop foldersNot scannedIRIS doesn’t scan endpoints; files in synced OneDrive folders are scanned insteadUnknownExcluded: recorded as a gap for the endpoint team
What you get

What each owner gets from the scan

What the scan couldn’t read

Tables and files IRIS couldn’t read are listed as not read, with the reason, which keeps a locked spreadsheet from passing as clean.

A dated re-scan after cleanup

Once the owner deletes or moves a copy, a re-scan of the same source is a new scan with its own date, and the scan history keeps the earlier one.

Capabilities

How IRIS finds sensitive data in copies

Point it at the places copies collect, such as staging databases, export buckets and SharePoint sites, and at the system of record.

Databases and warehouses

Covers 12 database and warehouse engines, including PostgreSQL, SQL Server, Oracle, MySQL, Snowflake, Databricks, BigQuery and SAP HANA. IRIS reads a sample of each table, and small tables in full.

Files in storage and shared folders

Reads PDF, current Word, Excel and PowerPoint, HTML, text, CSV and JSON files in connected cloud storage, Microsoft 365 and Google Workspace.

Identifiers checked by checksum

Validates nine identifier types by checksum before reporting them, such as Luhn for payment cards and Verhoeff for Aadhaar. Its 103 built-in data types cover Indian, US and global formats.

Scanned documents

Text recognition reads scanned PDFs and images in English and Hindi, on the IRIS host. A file it can’t read gets a reason and is never counted as clean.

Capabilities vary by edition.

Overview

What discovery can’t tell you

IRIS finds sensitive data where it sits. It doesn’t trace lineage, so it can’t say which table a copy was loaded from; the owner records that, as in the “why” column above.

It sees only the sources you connect, and it doesn’t scan laptops. Because it reads a sample of each large table, a value held in a handful of rows can be missed in any one scan.

Frameworks

Laws and standards that ask what you hold

GDPR Article 30: personal data categories. HIPAA §164.308(a)(1)(ii)(A): health data locations. PCI DSS 12.5.2: account data locations, at least every 12 months.

For UK GDPR, UAE PDPL, Saudi PDPL and PCI DSS, IRIS maps discovery findings to their controls. A scored readiness view for discovery work isn’t in v1; ask us if you need one.

How it works

Start with the store your exports land in

Scan the bucket your exports land in, then the database they come from, and compare the two scans’ findings: each customer table found in both is a copy to add to the inventory. The how-it-works page follows one scan from connection to findings.

FAQ

Questions about finding copies

Protect your brand. Start with your data.

Name the database your exports are cut from. We’ll show what IRIS finds in it, and in a demo, the copies around it.