Glossary. Sensitive data inventory.
What is a sensitive data inventory?
An inventory lists where sensitive data sits, who owns it and how each entry is known, because a row nobody has checked is only a claim.
By Dipal Panchal, co-founder and CEO · Updated November 7, 2026
A dated list, and how each row is known
A sensitive data inventory is a list of where sensitive data sits, by system and location, with each entry’s owner, how it is known and when it was last checked. Unlike a data catalog, which helps people find and understand data assets, an inventory covers only sensitive data and is checked against the systems themselves, so it includes copies nobody listed. Each row says how it is known, and a declared row stays a claim until a scan reads the source.
It is narrower and deeper than a general data inventory: it covers only the data with legal, contractual or security weight, and it goes down to the table, column or folder where that data sits.
Six inventory rows after one scan
A declared register compared with one generic scan, not IRIS output; rows 1 to 4 were read on October 28, 2026. The first words of the Why column give each row’s status.
| Source | Location | Detected type | Why | Sensitivity | Decision |
|---|---|---|---|---|---|
| Payroll database, UK | payroll.employee_bank | Bank account, salary | Declared and confirmed: the scan read a sample of the table and found both types | Restricted | Kept; the payroll lead stays owner |
| CRM, US | crm.contact | Email address, phone number | Declared and confirmed: the scan found both declared types in a sample of the table | Confidential | Kept; sales operations stays owner |
| Data warehouse, India | analytics.kyc_snapshot | Aadhaar number, PAN (Indian tax ID) | Found, not declared: the register has no entry for this table | Restricted | Added; the data platform lead becomes owner |
| Microsoft 365, US | Finance > Exports > q3_customers.xlsx | Email address, payment card number | Found, not declared: a spreadsheet in a OneDrive folder | Confidential | Added; finance names an owner by December 1, 2026 |
| HR database, UAE | visa_tracking.passport_holder | Declared: passport number | Declared, unverified: in HR’s 2025 register; not scanned, since the database isn’t connected | Not determined | Open: HR connects it or shows evidence by December 15, 2026 |
| Legacy billing database, US | billing_old.cards | Declared: payment card number | Declared, not found: in the 2024 register; the scan found no such table | Not determined | Open until the deletion log, a second approver and a clean re-scan close it |
Four ways a row can be known
Rows 1 and 2 are declared and confirmed: someone listed them and a scan read them on a date. Rows 3 and 4 are found, not declared: the copies a register built from interviews misses. Row 5 is declared, unverified: a claim nobody has tested. Row 6 is declared, not found, and needs evidence from the system before it leaves the list.
Dipal Panchal, Sylox’s co-founder and CEO, saw the gap between declared and found in his last enterprise role. He wrote in a November 2026 LinkedIn post: “I would have sworn I knew where our sensitive data was.” The audit, he wrote, found something new each time.
In his conversations with CISOs since, the systems missing from the declared list are the same kinds: test and development environments, small applications and tools bought on a company card. On a recorded call in 2026 he said many security leaders “blindly trust” the sources their teams declare.
Where the rules and standards ask for an inventory
None of these uses the phrase “sensitive data inventory”, and each binds a different organization.
| Rule | Provision | What it asks for |
|---|---|---|
| GDPR and UK GDPR (law; binds controllers) | GDPR Art. 30(1)(c); UK GDPR Art. 30(1)(c) | The categories of data subjects and of personal data in each processing record; not where the data sits |
| NIST SP 800-53 Rev. 5 (US federal systems; others by choice or contract) | PM-5(1)) | An inventory of systems, applications and projects that process PII, updated at a frequency the organization defines |
| PCI DSS v4.0.1 (card-brand contract; merchants and service providers) | Requirements 12.5.2 and 12.5.2.1 | Scope confirmed every 12 months (six for service providers) and on significant change, for all account data locations |
| ISO/IEC 27001:2022 (certifiable standard; by choice) | Annex A 5.9 | An inventory of information and other associated assets, with owners |
Flows, purposes and access live elsewhere
An inventory doesn’t show how data moves between systems; a data map does. It doesn’t record why the data is processed, who receives it or how long it is kept; a record of processing activities does.
It also doesn’t decide who should have access; data access governance does.
Label every row by how it is known
A declared row stays “declared, unverified” until a scan reads the source. A declared row the scan can’t find leaves the list only on evidence from the system itself, such as its deletion log, approved by a second person and followed by a clean re-scan. A found row with no owner gets one before the next review, or it goes on the risk register under the data team’s name. Owners confirm the rows a scan produced; they don’t compile the list from memory.
IRIS records findings by source and location in the sources you connect, for the data types it detects, each with its scan date. Capabilities vary by edition.
Findings by source and location, with the scan date: IRIS produces part of this, in the sources you connect, for the data types IRIS detects.
An owner, purpose and retention for each asset: IRIS produces part of this, as your stewards record them in the IRIS catalog, for the assets IRIS discovers.
Tables and files it couldn’t read, with the reason: IRIS produces part of this, for the tables and files the scan account can list.
Rows for SaaS apps and other systems nobody connected: Not produced by IRIS.
Explore the data catalogReconcile one system against a scan
Start the list of systems from an independent record, such as your single sign-on app list, cloud accounts or card spend, so the systems nobody declared show up too. Pick the one your auditor asks about most and scan it. Mark every row with one of the four statuses and add every finding the register lacks.
Keep each reconciliation as a dated record: the scan and its scope, who compared and who approved, and every open row with an owner and a due date.
The inventory feeds the record GDPR Article 30 asks for; the guide on Article 30 records against the data estate shows the two side by side.
Where to get the PCI DSS and ISO texts
- PCI DSS v4.0.1, requirements 12.5.2 and 12.5.2.1 (free after accepting the PCI SSC license), PCI Security Standards Council. Opened November 7, 2026.
- ISO/IEC 27001:2022 (sold by ISO), Annex A control 5.9 Inventory of information and other associated assets, ISO. Opened November 7, 2026.
Records the inventory works with
What is sensitive data discovery?
The step before the inventory: the scan that finds where sensitive data sits and records what it couldn’t read.
Data catalog vs sensitive data inventory
A catalog lists the assets people registered; the comparison runs one system through both.
What is a record of processing activities?
The next record: why each category of personal data is processed, for whom and for how long.
What owners and auditors ask
No. It holds locations, data types, owners and dates. An inventory full of real values becomes one more copy of the data it describes.
It confirms the detected types in the values it read, on the scan date. It doesn’t show what the unread rows hold, so the row records how the source was read: in full or from a sample.
It has to, wherever files hold sensitive data. Row 4 is a spreadsheet in a OneDrive folder, and an inventory that lists only databases misses copies like it.
Protect your brand. Start with your data.
Pick the systems your auditor always asks about. We’ll show the inventory IRIS builds from the ones it can connect to.