Hash-chained evidence
Evidence records in which each one includes the cryptographic hash of the previous record, so any alteration breaks the chain.
Overview
Using a hash function such as SHA-256, each record’s fingerprint depends on everything before it. Changing or deleting a record invalidates every later hash. The chain’s head can be signed or published so third parties can verify it.
It connects most directly to Evidence package, Private evidence chain and Audit trail.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
It makes evidence tamper-evident without relying on trust in whoever holds it.
Who it affects
Organisations that must prove records were not altered.
Where it sits
Ten linked steps connect where you operate to the proof that you complied.
- 01Jurisdiction
- 02Industry
- 03Activity
- 04Authority
- 05Regulation
- 06Requirement
- 07Guidance
- 08Control
- 09Evidence
- 10Enforcement
Connections
The terms most closely tied to Hash-chained evidence. Select one to open it.
What to do about it
- 1Define the owner, frequency, data and pass condition.
- 2Automate the test on source data where you can.
- 3Capture evidence on every run, including exceptions.
- 4Review exceptions and failures and record the decision.
From requirement to evidence.
Every evidence pack and log in Regulation Layer is hash-chained on a private chain dedicated to your company.
Request early access →