evidence sealing

Recording a cryptographic hash of collected evidence at a fixed moment, so that any later change to the files can be detected.

In more detail

When testing ends, the auditor hashes every evidence file into a manifest, then hashes the manifest itself and stores that final value outside the evidence folder, for example in the audit ticket. Anyone can later recompute the hashes, and a file that was edited fails the check. Keeping the manifest's own hash elsewhere stops someone from quietly editing a file and rebuilding the manifest to match.

Examples

sha256sum changes.csv sample.txt results.csv > manifest.sha256
sha256sum manifest.sha256    # this hash goes into the audit ticket
results.csv: FAILED

Related terms

Taught in

References