Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
SHA-256 Evidence Sealing, Explained for Audit Teams
Short answer
SHA-256 sealing means the platform computes a cryptographic fingerprint of each artifact at the moment it is imported or uploaded, stores the artifact immutably, and records that fingerprint in the room manifest. Later, anyone can recompute the fingerprint of the file in hand and compare: a match proves the file is byte-for-byte the file that was sealed; a mismatch proves it is not. It turns 'we believe this is the original' into a check anyone can run.
What is SHA-256 evidence sealing?
SHA-256 evidence sealing is the practice of hashing an artifact with the SHA-256 algorithm at intake and preserving that hash as part of the record. In AI Audit Exchange every artifact's manifest entry carries its sha256 value alongside its filename, source product, format, size in bytes, import date and source retention note — and the artifact itself is stored immutably, so the sealed hash and the stored file can be checked against each other at any time.
What a hash fingerprint actually is
SHA-256 takes a file of any size and produces a 64-character fingerprint with two properties that matter for evidence. First, it is deterministic: the same file always produces the same fingerprint, on any machine, at any time. Second, it is exquisitely sensitive: change one byte — one character in a document, one pixel in an image — and the fingerprint changes completely. Those two properties together give audit evidence something paper never had: a test for sameness that does not depend on trusting the person presenting the file. You do not believe the file is unchanged; you recompute and compare.
Sealing happens at intake, not at audit time
The evidentiary value of a hash depends entirely on when it was computed. A hash computed the week before the audit proves the file has not changed since that week — which invites the obvious question about the year before it. Sealing at intake closes that gap: the hash is taken at the moment the artifact enters the room, when it is imported from a suite product or uploaded directly, and the import date is recorded beside it. This is also why the monthly filing habit matters — an artifact sealed in the month it was produced carries a year's less doubt than one sealed at period-end. The filing pattern is described in preparing for an independent audit.
The manifest is where the seal lives
A hash kept in a separate spreadsheet can be edited as easily as the file it describes. Here the seals live in the room manifest: one structured record listing every artifact with its hash, source, format, size, import date and retention note, plus the room's regime, period, retention and hold status. The manifest can be exported at any time, and the export moment itself is recorded on the room. When an auditor samples evidence, the workflow is: read the manifest, choose artifacts, re-verify each hash against the stored record, and note the results. The manifest's anatomy is covered in what an evidence manifest is.
What a match proves — and what it does not
Precision here is a virtue. A matching hash proves the artifact is byte-identical to the artifact sealed at intake. It does not prove the artifact's contents are true, complete or well-made — a flawed report seals just as beautifully as a sound one. Sealing answers the integrity question so the audit can spend itself on the quality questions: whether the evidence is the right evidence, whether it covers the period, whether it supports the claims. Teams that understand this distinction stop overselling their hashes and start benefiting from them: the auditor's trust conversation moves from 'can I trust these files?' to the substance in a single step.
Immutability is the seal's partner
A hash detects change; immutability prevents the quiet kind. Artifacts in a room are stored immutably — the stored record is the intake record — and imports from suite products are held read-only and unchanged, exactly as the generating product produced them. Pair that with scoped access (only the owner and a granted auditor can read the room) and the threat model shrinks to something manageable: for a file to be wrong, someone would have to change it and its recorded hash together, inside a system that records access. The platform's wider security posture is described on the security page.
Verifying a hash yourself
Verification is deliberately unglamorous: open the room, choose an artifact, ask for its verification, and the platform recomputes the stored file's hash and compares it with the sealed value from intake. Do it in rehearsal, do it when the auditor arrives, do it when a record is questioned in year four. Three sample verifications during a monthly review take minutes and are the cheapest integrity assurance in the entire audit programme — far cheaper than the meeting that happens when nobody can answer 'is this the original?' See how to verify an artifact hash for the step-by-step.
Five actions to take
- Import or upload evidence during the period so sealing happens close to production, not at audit time.
- Confirm each new artifact appears in the manifest with its sha256, source, size and import date.
- Sample-verify hashes monthly — three random artifacts per review is enough to keep the habit honest.
- Never describe a hash match as proof the contents are correct; it proves the file is unchanged, which is a different and valuable thing.
- Export the manifest at close-out so the seals travel with the record for the full retention period.
Worked example
A fictional benefits-administration firm, Copper Canyon Benefits, files 47 artifacts into its CPPA room across a year. At the pre-audit rehearsal, the auditor-of-record-to-be samples 8 artifacts and re-verifies each hash against the manifest: 8 of 8 match. One direct upload, however, draws a question — not a mismatch, but a file whose contents look like a later revision of a policy summary.
The room answers the question without argument: the sealed hash and import date show the file entered the room on 14 March, byte-identical to what is stored. Whether the March revision is the right one is a substantive discussion the team can now have calmly — the integrity question is already closed. That separation, integrity in minutes and substance in the meeting, is what sealing buys a fictional firm with 47 files and a real one with 4,700 alike.
Frequently asked questions
Can two different files produce the same SHA-256 hash?
For practical evidence purposes, no — SHA-256 is designed so that finding two different inputs with the same fingerprint is computationally infeasible. Auditors treat a hash match as proof of byte-identity.
When exactly is the hash computed?
At intake: the moment an artifact is imported from a suite product or uploaded directly into the room. The import date is recorded in the manifest beside the hash.
What does a mismatching hash mean?
It means the file being checked is not byte-identical to the file sealed at intake — it was edited, regenerated, corrupted or substituted. The correct response is to work from the stored, sealed record and investigate the copy, not the room.
Does sealing change or compress my files?
No. Imports are stored read-only and unchanged, exactly as the generating product produced them; direct uploads are stored as received. The hash is computed over the file as it arrived.
Where can I see an artifact's hash?
In the room manifest, which lists each artifact's filename, source product, format, sha256, size, import date and source retention note — and the manifest can be exported at any time.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: What Is a Legal Hold on Audit Evidence? · Next: What Is an Audit Evidence Manifest?
How to Choose an Independent AI Auditor · How to Become a Vetted AI Auditor on AI Audit Exchange · How to Write an AI Audit Engagement Brief That Gets Good Responses