Tamper-evident audit trail

A tamper-evident audit trail is a log of every human and system action in which each entry carries the fingerprint of the previous one. Entries are never edited or deleted. If any entry is changed later, recomputing the chain shows the break. Reconora records package intake, runs, approvals, claims and rule changes this way.

How it works

A tamper-evident audit trail stores, with each entry, a SHA-256 fingerprint of the entry before it. An illustrative chain:

#1041  run started        prev: 8c21…  hash: 3f9a…
#1042  claim approved     prev: 3f9a…  hash: b7e0…
#1043  rule proposed      prev: b7e0…  hash: 41dd…

Edit entry #1042 and its fingerprint changes. Entry #1043 no longer points to it, so the integrity check, recomputed on demand, shows exactly where the chain breaks.

Why it matters

Regulators and auditors ask who decided what, when and on what grounds. A tamper-evident audit trail answers with the entry, its author and its evidence, without a spreadsheet hunt. In Reconora it works together with five roles with separated rights. A rule change by an operator is only a proposal until a manager approves it. The log exports for an auditor in one click.

How to spot it

Ask three questions about any log you rely on. Can an administrator edit or delete an entry? Is there a check that would show it? Can you export the log with its integrity proof? A log that anyone can quietly change is a list, not an audit trail.

Related terms

Discrepancy queue · Claim candidate · Record balance · Anonymisation · Audit trail

Try it on one day of your data

One day of your data, reconciled, and the report stays with you whether or not you continue.

Updated