Glossary. DSPM.
What is DSPM (data security posture management)?
DSPM tools find sensitive data and judge its exposure. Whether that data should exist at all is a decision the tool leaves to its owner.
By Dipal Panchal, co-founder and CEO · Updated November 7, 2026
Data first, then who can reach it
Data security posture management (DSPM) is a category of tools that find sensitive data across databases, cloud storage and SaaS and check who can reach it and how it’s protected. Unlike cloud security posture management (CSPM), which checks how infrastructure is configured, DSPM starts from the data itself and works outward to the accounts and settings that expose it. A report is only as good as its last column: the tool ranks the exposure, and an owner decides what happens to each finding.
The output is a list of findings: each one a place where sensitive data sits, with its type, its exposure and its protection state.
Six findings from one estate
A tool fills in the first five columns. It can settle row 6 itself and suggest the fix for rows 1, 3 and 4; rows 2 and 5 need the owner to say whether the copy should exist.
| Source | Location | Detected type | Why | Sensitivity | Decision |
|---|---|---|---|---|---|
| Customer database, US | billing.customer.ssn | US Social Security number | SSN-format values in plain form (not shown), with no access policy: every role in the database can read them | Restricted | Owner limits the column to the billing team; column-level encryption follows, keys held by security |
| Analytics warehouse, UK | marketing_ext.contacts_2024 | Email address, UK mobile | A 2024 copy of the CRM contact table, phone numbers included (masked here); no owner on record | Confidential | The CRM owner finds no current purpose; the copy is deleted |
| Cloud storage bucket | ops-exports/payroll_2025_06.csv | Bank account, salary | The bucket policy lets every account in the cloud organization read the file | Restricted | Owner narrows the policy to the payroll team |
| Microsoft 365, UAE office | HR site > Onboarding > passport_scans | Passport number | Scanned passports in a folder anyone with the link can open | Restricted | Owner removes the link and checks the audit log for its use; the next scan confirms it is gone |
| Test database, India | qa.customer_kyc.pan | PAN (Indian tax ID) | PAN-format values beside customer names, in a test copy of the KYC table | Restricted | Owner swaps in synthetic values, then has the copy re-scanned |
| Application database | app.request_log.order_ref | None (card candidate) | 16-digit order numbers: about one in ten pass Luhn, the rate chance alone gives | None | Rejected: order references, dropped from the card count |
What the sixth column asks of a person
Rows 2 and 5 turn on purpose, which no scan can read. A scan can show that a full copy of the contact table sits in the warehouse, or that a test database holds PAN-format values beside real names. Whether the copy should exist is for the data’s owner to decide, within the law’s limits on purpose, minimization and storage, such as GDPR Article 5(1)(b), (c) and (e).
Row 6 is the tool’s own decision. A column of order numbers passes the card checksum in about one row in ten, so the tool drops it before it reaches anyone’s queue.
How a DSPM tool builds that table
A DSPM tool connects to each data store, with read access or through a snapshot. It lists what is there: schemas, tables and columns; buckets and files; SharePoint sites and drives. It reads a sample of the values and classifies them with patterns, checksums and context, the method our data classification entry shows value by value.
Then it joins three more facts to each sensitive location. Who can reach it: grants, roles, group membership, sharing links. How the values are stored, checked as encrypted, masked, hashed or plain. How far the store is exposed: one team, the whole organization, anyone with a link. Restricted data that is readable widely and stored in plain form ranks first.
A store the tool can’t connect to, or a table it couldn’t read, has to show as a gap. A report that leaves those out reads as clean in places nobody checked.
What DSPM does not replace
DSPM doesn’t replace data loss prevention (DLP), which inspects data in use, in motion and at rest and can block a transfer. It doesn’t run joiner, mover and leaver changes or access certification; identity governance and administration (IGA) tools do. It doesn’t check cloud infrastructure settings the way a CSPM tool does.
It also leaves two decisions with people: whether a copy should exist at all, which is the data owner’s call, and whether a control is met, which is your auditor’s.
Read a DSPM report by its decision column
Dipal Panchal, Sylox’s co-founder and CEO, called tools such as data security posture management “just enablers” in a May 2026 interview. The work starts, he said, with ownership and accountability.
Our rule: every restricted finding gets a named owner and a decision before the next scan. The four decisions are restrict access, protect the values, delete the copy, or accept it with a written reason. A finding still undecided at the next scan goes on the risk register under the owner’s name.
Start with what Panchal calls “the biggest risk you have to solve right now”: restricted data with no encryption and no access policy. Rows 1 and 4 are that case, so they come first.
IRIS runs dated point-in-time scans of the sources you connect, scheduled or on demand. Capabilities vary by edition.
Find and classify sensitive data: IRIS produces part of this, in the sources you connect.
Map who can reach it: IRIS produces part of this, for supported sources that expose permission data.
Check how values are stored: IRIS produces part of this, on sampled values, once the protection check is activated on your install.
List what it could not read, with the reason: IRIS produces this.
Make the owner’s decision or apply the fix: Not produced by IRIS.
See how a scan runsTest a DSPM tool on a source you know
Before you buy or extend a tool, run it with the read-only account its vendor asks for against a source whose contents you know. Seed one table with ten test card numbers, keep one table you know is clean, and add a second store with a login that can’t read it. The test passes when the report finds all ten seeded values, shows the clean table as read with nothing found, and lists the second store as not read.
Data security governance and management (DSGM) adds the record of what was checked and who decided, and the guide to building a source coverage register shows that record filled in.
Before DSPM, beside it and after it
What is data classification?
The step every DSPM finding depends on: how a matched value becomes a type and a level.
DSPM vs DLP vs CSPM
The three categories most often mixed up: what each acts on, and one scenario run through all three.
What is DSGM?
What comes after the findings: coverage on record, an owner for each decision, and evidence an auditor can retest.
What buyers ask about DSPM
No. Laws require outcomes, such as records of processing under GDPR Article 30 and appropriate security under Article 32. A DSPM tool can supply evidence toward parts of those; your auditor, and under GDPR the supervisory authority, judges whether they are met.
Read access to each data store in scope, or to snapshots of it, plus read access to permission data if it maps who can reach what. Snapshot-based tools also need rights on the snapshots and their keys, so ask each vendor for the exact list.
After each new source is connected, after each fix, and on a schedule that matches your access review cycle. A scan is a dated picture, so the evidence is the series of scans.
Protect your brand. Start with your data.
See how IRIS finds sensitive data in connected sources, maps who can reach it where supported and records its checks.