Cookie settings

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

Skip to content
Skip to content

Protection checks. Encryption checks. Masking checks.

Find sensitive values stored in plain form, column by column.

IRIS checks sampled values in each sensitive column and records whether they’re encrypted, masked, hashed or in plain form, so you know which gaps to close.

Eight values and the state IRIS records

Values as they sit in the source, with the state IRIS detects for each. Row six is the limit: a token shaped like a card number reads as plain.

Records
ValueDetected typeLabelReasonKept or rejected
4111 1111 1111 1111Card numberDetected: plainReadable digits that pass the Luhn checkKept: fix needed
**** **** **** 1111Card numberDetected: maskedMask characters detected in all but the last four digitsKept: form confirmed; strength is yours to judge
j•••••••••@example.comEmail addressDetected: maskedMask characters detected in the part before the @Kept: form confirmed; strength is yours to judge
GB82WEST12345698765432IBANDetected: plainA readable account number that passes the mod-97 check (a published example IBAN)Kept: fix needed
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd6…PasswordDetected: hashedIRIS detects a 64-character hex value, the form of a SHA-256 digest; NIST SP 800-63B-4 requires salted hashingKept: the reviewer checks how the password is hashed
5555 5555 5555 4444Card numberDetected: plainDigits shaped like a card number that pass the Luhn check; IRIS can’t tell a format-preserving token from a real numberKept as plain: the reviewer notes the token in the review reason
AQICAHhr4X…7Lw==Government ID (column named nino)Detected: encryptedA recognized encrypted-value format detected, with no readable numberKept: form confirmed; strength is yours to judge
2222 2222 2222Aadhaar number (candidate)NoneA repeated-digit placeholder that also fails the Verhoeff check (not issued)Rejected: not an Aadhaar number
Capabilities

What a status records, column by column

Dipal Panchal’s first priority: restricted data that is not encrypted and has no access policy, “the biggest risk you have to solve right now.”

Protection status by column

Checks sampled values in each sensitive column, once the check is activated on your install, and records them as encrypted, masked, hashed or plain.

Encryption-at-rest checks

Checks the encryption-at-rest setting of the database itself on 9 database engines, beside the state IRIS detects in the sampled values.

Risk scoring

Combines each column’s protection status with its sensitivity and who can reach it into a risk score, so your team sees which gaps to close first.

Re-scan after a fix

Records the new state with its date when your team re-scans after a change in the source, beside the state the first scan found.

Capabilities vary by edition.

How it works

From classification to a dated re-scan

Checked on November 8, 2026 against IRIS v1.

  1. Classify

    IRIS finds and classifies sensitive data in the sources you connect.

  2. Check samples

    IRIS checks the form of sampled values in each sensitive column: encrypted, masked, hashed or plain.

  3. Score

    Protection status, data sensitivity and access feed the risk score.

  4. Fix at source

    Your team fixes the gap in the source system, with its own tools.

  5. Re-scan

    A re-scan records the new state, dated like the first scan.

In the product

Screens behind the check

Protection checks

A protection status on each sensitive column

Each classified column shows its pattern, sensitivity, confidence and protection status. The check runs once it is activated on your install.

  • A status checked on sampled values
  • Reviewers approve, reclassify or decline each finding
Explore discovery
IRIS results table listing classified database columns with their detected pattern, sensitivity and protection status
Each classified column with its pattern, sensitivity and protection status, ready to confirm or correct.
Classification summary

Which patterns recur

The summary lists the personal-data patterns found most often. Protection status then feeds a risk score that also weighs data sensitivity and who can reach it.

  • Matches and estimated records for each pattern
  • A dated record of the state after each fix
Explore access
IRIS classification summary of the personal-data patterns found most often, with columns and files, matches and estimated records for each
The personal-data patterns found most often, with matches and estimated records.
Questions

Questions the status column answers

Is each sensitive column protected?

IRIS checks the values in each sensitive column, so a readable access token stored beside hashed passwords shows up as its own finding.

Which personal data is in plain form?

Each personal-data column shows the state of its sample, so the columns in plain form are the first your team fixes.

Did the fix change anything?

Each protection finding carries its scan date, and a re-scan after a fix records the new state beside the old one.

Overview

How IRIS checks, and where it stops

IRIS reads sampled values in each sensitive column and checks their form. The state it records describes how a value is stored, and judging whether that protection is strong enough stays with your team. Stored samples are masked by default for personal-data columns, so reviewers see only part of each value.

Format-preserving tokens look like the values they replace, so IRIS records them as plain, as in row six. Password-protected files can’t be opened, so they’re listed as not read, and counted neither clean nor protected.

Your team makes each change in the source system, and a re-scan records the new state. The password row follows NIST SP 800-63B-4, section 3.1.1.2; to see where the check sits in a full scan, follow one on the how-it-works page.

FAQ

Limits of the check, answered

Protect your brand. Start with your data.

Get a free assessment of one database and see which sensitive values are stored in plain form.