"We anonymized the file, then encrypted it" is a sentence. Written in an email or a shared doc, it's a claim a reviewer either trusts or doesn't — there's nothing stopping someone from editing it after the fact, or writing it before the work was ever done. Calling that record "audit-ready" doesn't change what it is.
An audit-ready report, as FileX builds it, is different in one specific, checkable way: it's tamper-evident. Understanding exactly what that does and doesn't prove is the difference between using it well and overselling it.
What the report actually is: an attestation, not a verification
FileX's Audit-Ready Report tool lets you record what was done to a file — classified, anonymized, metadata-scrubbed, encrypted, password-protected, watermarked, securely erased, or another action you specify — along with when it happened and any notes. It's important to be precise about what this is: it's an attestation the operator builds, not an independent audit. FileX doesn't watch you do the work and verify each action actually happened. It records what you entered. The report's disclaimer says this directly: it "attests to actions the operator recorded for this file... it is not an independent audit and not a compliance certification — it is only as accurate as what was entered."
That's not a limitation to hide — it's the honest boundary of what a client-side tool can promise. FileX never sees your infrastructure, your ticketing system, or your actual workflow. It can't independently confirm a file was really encrypted somewhere else. What it can do is turn your attestation into something that can't be silently edited later.
Where the actual value is: the integrity hash, and the optional signature
The report does one more thing on top of your attestation: at generation time, FileX scans supported text files (plain text, and text extracted from PDF and Word documents, entirely in your browser) using the same detectors as the Data Classification tool — patterns for emails, phone numbers, card numbers, and other personal or financial data — and attaches a suggested sensitivity level to the record.
Then the whole record — your recorded actions, the file's SHA-256, the classification scan, your notes — gets hashed with SHA-256 into an integrity hash. Recompute that hash later over the same data and compare it to the one in the report: if they match, nothing has been altered since the report was generated. That check needs no key, no server, and no trust in FileX itself — anyone can redo the arithmetic.
Signing is a separate, optional layer on top. You can sign the report's integrity hash with your FileX ID using ML-DSA-65, the same NIST-standardized (FIPS 204) post-quantum signature algorithm FileX uses for its erasure certificates — a fixed context string keeps the two signature types from being interchangeable. An unsigned report is still fully tamper-evident — the hash check works regardless. Signing adds attribution: proof of who generated the report, tied to a specific FileX ID, verifiable independent of FileX's own systems.
Reading a report
Each report bundles a few things: a plain-text summary, the machine-readable JSON record, and a formatted HTML or PDF version with the same data embedded so it stays independently verifiable — open the HTML report and the underlying JSON is right there to re-check. The report lists your file's name, size, and SHA-256; your recorded actions; the classification scan (if one ran); your notes; and finally the integrity hash and signature status.
That structure is deliberate. It separates "what the operator says happened" (the actions and notes — trust these the same way you'd trust any human-entered record) from "what can be mathematically checked" (the hash, and the signature if present). A reviewer who understands that split gets real information out of the report instead of false confidence.
When this is worth using
If you're the only one who'll ever see the record, a plain note is fine. An audit-ready report earns its place when the record needs to survive contact with someone else — a client, an auditor, a compliance reviewer, or your future self trying to reconstruct what happened to a file six months later. The tamper-evidence means the report can't be quietly edited after review without the hash breaking; the optional signature means it can be traced to a specific identity years later, even against a future with quantum computers capable of breaking today's non-post-quantum signatures.
Try the Audit-Ready Report Generator on a file — nothing is uploaded, the classification scan and the report itself run entirely in your browser.
Top comments (0)