Whitepaper · MF-WP-03 · Version 1.0
Evidence You Can Prove
Signed exports and a tamper-evident audit trail
When video goes to a court or an inquiry, the first question is whether anyone could have changed it. This paper explains what a MultiFusion evidence package contains, how a court, auditor or investigating officer can check it with standard tools and no MultiFusion software, what a signature proves and what it does not, and good practice for keeping the audit trail trustworthy.
For courts, auditors, investigating officers, CISOs and tender committees
- Signed evidence packages
- Independent verification
- Tamper-evident audit trail
- What a signature proves
- Good practice
SHA-256bc55a8deb863d9a20ccaa1f298870a427b4181109dbb3cd53770363e5c7358a9
4checks
A third party runs four checks on a package, all printed in its VERIFY.txt.
0MultiFusion tools
Only openssl, a SHA-256 tool and base64 are needed to check a package.
1hash per file
SHA-256 for every file in the package, and an ECDSA P-256 signature over the list.
1anchor an hour
The audit chain is re-checked every hour and its head hash recorded.
Contents
- 01Why provable evidence matterspage 2
- 02What an evidence package containspage 3
- 03Checking a package with opensslpage 5
- 04What a signature proves, and what it does notpage 6
- 05The tamper-evident audit trailpage 7
- 06Good practice for a sitepage 9
Figures: Inside a signed evidence package · The four checks a reviewer runs · The audit chain, intact and after one edit
Look inside
Every page of the paper. Click a page to read from there.
