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.sha256sha256sum manifest.sha256 # this hash goes into the audit ticketresults.csv: FAILEDRelated terms
- evidence — The records, files and outputs that show a control really exists and works, collected so that someone else can check it.
- sha256sum — A command-line tool that prints the SHA-256 digest of files and can later check them against a saved list of digests.
- tamper-evident — Built so that any unauthorised change leaves visible signs, even if the change itself cannot be prevented.
- chain of custody — The written record of everyone who had a piece of evidence, when, and why, from collection to court.
Taught in
- Internal Audits, Sampling & Evidence Chains — Cybersecurity Fundamentals, GRC & Cryptography