A data catalog is enough when
Your goal is helping people find and trust data for analytics, and the privacy team keeps its record of sensitive data another way.
Category comparison. Data governance.
What each one records, who keeps it current and what it shows an auditor, shown on one table recorded both ways.
By Dipal Panchal, co-founder and CEO · Updated November 8, 2026
A data catalog helps people find, understand and trust the data they use. It describes datasets with metadata: what they hold, what they mean and who looks after them. A sensitive data inventory answers a narrower question: which stores hold personal, financial, health or credential data, and who can reach them.
If you must answer to an auditor for where regulated data sits, you need the inventory, and a catalog can feed it. NIST’s Cybersecurity Framework 2.0 names the outcome: inventories of data and corresponding metadata for designated data types are maintained (ID.AM-07).
Explore sensitive data inventoryEach cell describes a typical catalog or inventory tool. Compare the one you run against it.
| Aspect | Data catalog | Sensitive data inventory |
|---|---|---|
| Acts on | Every dataset people should be able to find, sensitive or not | Sensitive or regulated data, wherever it sits, including copies nobody listed |
| Question it answers | What data do we have, what does it mean and can I use it? | Where is our sensitive data, who can reach it and is it protected? |
| Main strength | Meaning, ownership and trust: definitions, stewards and usage notes | Finding sensitive values wherever they sit, including places nobody described |
| What it cannot do | Say a free-text column holds card numbers when its description says otherwise | Explain what a dataset means to the business or who uses it for analysis |
| Best fit | Helping analysts and engineers find and trust data | Showing an auditor where regulated data sits and who could reach it |
| A typical scenario | An analyst searches for the customer table and reads its definition | A privacy lead checks which stores hold health data before a privacy review |
| Where it runs | Connects to systems to collect metadata | A scanner that reads sampled content from each source with an account you grant |
| Main users | Analysts, data engineers, data scientists and data stewards | Security, privacy, data owners and auditors |
| Reads the data itself | Mostly metadata: schemas, names, descriptions and statistics. Some tools also profile values | Yes, when built by scanning: it samples values, so the decision doesn’t rest on column names alone |
| How it goes stale | Stewards stop curating, or new systems are never harvested | Scans stop, or new stores are never connected |
A customers table in a billing database. The card number is a processor test number.
| Column | Catalog entry | Inventory row |
|---|---|---|
| Contact email. Business term: Customer contact. Steward: Finance data | Email address in sampled values. Sensitivity: personal. Owner confirms why it is kept | |
| notes | Agent notes. Free text from support calls | Sampled value 4242 4242 4242 4242 passes the Luhn check. Card number. Sensitivity: financial. Owner to decide |
| ref_code | Internal reference code | Rejected: a 16-digit value failed the Luhn check, so it is not a card number. The reason is recorded |
| Who can reach it | Not recorded; access sits in another system | Two roles and one service account hold read access, as of the scan date |
| Who keeps it current | The steward, when someone edits the entry | The scan on its schedule; the owner reviews changes |
Your goal is helping people find and trust data for analytics, and the privacy team keeps its record of sensitive data another way.
You must show where regulated data sits and who can reach it, and nobody is asking for a catalog of every dataset yet.
The catalog names owners and meanings, and the inventory shows where sensitive data actually is. Link them so an owner confirms what a scan found.
Before you call your catalog the inventory, put a table you know through it.
IRIS gives you an inventory by source, table, column and file, with each finding linked to its source and scan date.
Across the sources you connect, IRIS records where each finding sits. A source it could not read is listed with the reason.
The IRIS catalog keeps owners, purpose, retention and legal hold for each discovered asset. Stewards certify each asset, and every change is kept.
Where a source exposes permissions, IRIS reads them and flags excessive access.
Each scan carries a date, and each finding links back to its source. A re-scan after a fix records the new condition.
Capabilities vary by edition.
What the inventory records, how it is built and what an auditor expects to see in it.
One governed record for every data asset IRIS discovers: owners, purpose, retention and legal hold.
How IRIS finds sensitive data in the sources you connect, with the source recorded for every finding.
No. A catalog describes data so people can find and use it. A sensitive data inventory records where regulated data actually sits and who can reach it.
The data owner for each system, with privacy or security running the process. A scan can find the data; only an owner can confirm why it is kept.
No. DSPM is a category of tools, and a sensitive data inventory is one of the records they produce. DSPM also assesses who can reach the data and how it is protected.
Yes, partly. Some catalogs tag sensitive columns, and some discovery tools keep a record for each asset. Test each one against the questions in the table, not its category name.
No. The IRIS catalog governs the data assets IRIS discovers, for security and privacy work. It has no lineage, business glossary or data quality scores.
Plant a test card number in one table this week, then book a demo to see the inventory.