Cookie settings

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

Skip to content
Skip to content

Blog. Data security.

Why mid-market teams should start with a sensitive data inventory

Dipal Panchal

Co-founder and CEO · November 6, 2026 · 3 min read

On this page

A security team of a few people can’t do everything at once. The first project should be the list every other control depends on: where sensitive data lives, who owns it and what you don’t know yet. Build that sensitive data inventory before a tool rollout or a new set of policies.

Every other control assumes it

Access review needs to know which systems to review. Retention needs to know which copies exist. Incident response needs to know what a compromised system held. Each of these assumes someone knows where the sensitive data is.

NIST’s quick-start guide for small businesses, SP 1300, opens its Identify section in the same order: “Before you can protect your assets, you need to identify them.” It then advises businesses to “prioritize inventorying and classifying your business data.”

A system list is not a data list

NIST’s Cybersecurity Framework 2.0 keeps the inventories apart. ID.AM-01 covers hardware, ID.AM-02 covers software, services and systems, and ID.AM-07 covers “data and corresponding metadata for designated data types.”

A system list tells you a CRM exists. A data inventory tells you it holds customer phone numbers and scanned identity documents, and that an export copies them to a file share each night. NIST’s draft guide to data classification practices is direct about why this is hard: organizations “may not know the locations of all their data.”

A first inventory fits on one screen

Records
SystemBusiness ownerSensitive data typesCopiesHow we knowGap
CRMHead of salesCustomer names, phone numbers, scanned identity documentsNightly export to a file shareScanned November 4, 2026None recorded
HR systemHR directorEmployee identity and payroll dataMonthly extract to financeReported by the HR directorNot yet scanned
Core databaseHead of platformCustomer and payment dataCopy in the test environmentScanned November 4, 2026Test copy owner not named
Shared driveIT operations managerUnknownNot knownNot assessedContents never reviewed
Marketing platformHead of marketingNone: newsletter addresses held by a processorNoneOwner confirmed in writingExcluded from the first pass

The “how we know” column separates evidence from report. A line marked “reported by the HR director” is useful, and it isn’t the same as a line marked “scanned.”

Start with the systems that hold customer and employee data

In a company of a few hundred people the list is short: a core database or two, the CRM, the HR system, a shared drive and a warehouse. Read those systems properly, record what you couldn’t read and give each one a named owner. A short inventory that is true beats a long one that is guessed.

Then keep it current. Each new system, export or vendor goes on the list when it arrives, and that habit costs less than rebuilding the list before an audit.

An incident notice is answered from the inventory

In December 2020 SolarWinds told the US Securities and Exchange Commission that it believed fewer than 18,000 of its customers might have installed Orion product versions that contained a vulnerability. A customer holding an inventory of the software and suppliers that touch its data could check itself against that notice within a day. A customer without one had to start by finding out.

A first inventory needs no new tool and no new scheme

A first inventory is not a catalog project. Start with the few data types your contracts and regulators care about, and use the names your policy already has. A spreadsheet with named owners and a “how we know” column is a real inventory. A tool speeds the work up for a team that has decided the work matters, and the decision comes first.

The tool question gets easier once you can see which lines are guessed, because those are the lines worth scanning first.

The inventory makes four decisions concrete

  • Access reviews start with the systems that matter most.
  • Retention decisions attach to real copies.
  • Tool decisions get specific, because you can ask a vendor what it reads in your systems.
  • Customer security questions can be answered from a list.

NIST’s small business guide makes the access point itself. When switching on multi-factor authentication, it says to start with the accounts that can reach the most sensitive information. You can only do that if you know where that information is.

With IRIS

For the sources you connect and the data types IRIS detects, IRIS lists where sensitive and personal data sits, by source, table and column, or file, with the scan date on each finding.

Whatever a scan couldn’t read is listed with the reason, and an unread table shows as unknown, not as clean.

A free assessment covers one database you choose. See discovery and classification.

Fill the first five rows this week

Open a spreadsheet and list the five systems you would least want to explain after an incident. Give each an owner and a “how we know” entry, and write the gap in plain words. The glossary entry on the sensitive data inventory defines the terms, and the source coverage register guide shows how to record what each read covered.

Sources

Share this article

Protect your brand. Start with your data.

Book a demo, or start with a free assessment of one database.