Why we report redacted samples instead of full values

Imagine a security report that lists every Social Security number it found, in full, so that you can verify each one. It would be thorough. It would also be the most dangerous document in your office: a tidy, searchable list of exactly the data you were trying to protect, emailed around, exported and saved. A report about sensitive data must never become a new copy of that data. That single idea drives how MyVaultMate records what it finds.

The principle: report on the data, do not duplicate it

Every extra copy of a sensitive value is another place it can leak: in a backup, an export, a screenshot, a forwarded email, a support ticket. The way to avoid creating new copies is to never create them. So the design rule is simple. The files and the full values never leave the machine and are never stored, and no field in the product holds a raw value. Not in the database, not in the dashboard, not in the PDF.

It is an easier rule to keep when it is built into the structure, not when it depends on people remembering to be careful. If there is no place for a raw value to live, it cannot be exposed from there.

What a sample looks like

What the report keeps, at most, is a short redacted sample: the shape of the value with most of it masked and the last four characters visible. For a Social Security number, that looks like ***-**-1234. For a payment card, a masked sample ends in the last four digits. It is a hint, not the data.

There is also a hard limit: a sample can be at most 64 characters long. The cap means even an unexpected oddity, such as a very long value in a strange format, cannot turn into a pasted chunk of document text. The limit is part of the design, not a setting someone has to remember to apply.

Last-four samples also line up with how privacy laws tend to think. Under Nevada's NRS Chapter 603A, for example, encrypted data and last-four-digit samples are generally outside the definition of personal information. This is general information, not legal advice, and your attorney can tell you how it applies to you.

What a sample is good for

A sample has one job: confirming a hit. When you see a finding, you want to know whether it is a real Social Security number or an order number that looks like one. The last four digits, combined with the file path and the count, are often enough to tell. Some examples:

• A finding in Clients\Okafor\2022 with a sample ending in 4471 can be quickly checked against that client's file.
• A sample like ****-****-****-1111 in a developer's test folder is probably test data.
• Several findings in one spreadsheet, with different last-four endings, tell you it is a list of many people rather than a single stray number.

The report also gives an estimated count of different ID numbers, so you get a sense of scale without any of the values.

What a sample is not good for

It will not let you reconstruct the number. It will not let you contact or identify a person. On its own, it is far less useful to a thief than the full number. That is precisely the point, and it has an honest cost: you cannot work entirely from the dashboard. When you need the whole picture, you open the file yourself, on the machine where it lives, using the path from the report. Your files stay under your control, and the dashboard stays a map to them rather than a copy.

A sample also cannot settle every question. A masked, shortened string is sometimes ambiguous. The triage routine in our false-positive article shows how to combine the path, the count and the sample to decide quickly.

What this means when the report travels

Exposure reports get shared. You may hand a PDF to a partner, an IT provider, an insurance broker or an auditor, and exports to PDF, CSV and XLSX are there for exactly that. Because the report contains paths, types, severities, counts and short masked samples, passing it along does not mean passing along a database of identities. Remember that file paths can still contain names, so share the report with the same care you would give a client list. Our own staff's access to dashboards is role-gated and logged.

The same thinking applies to your own work: write down what you decided about a file, but do not paste the actual value into the note. If your habit is to put full numbers into tickets and emails, the redacted-sample approach is a good model to copy. For a full picture of what leaves the computer, read our plain-English walkthrough, or see the security page.