Legal disputes
Claiming "the logs were not altered" carries no weight on its own in court. A cryptographic chain provides mathematical proof — independently verifiable by an expert witness.
Every audit record is mathematically chained to the next. Retroactive change is impossible — any tampering breaks the chain and is detected the moment verification runs.
"The logs cannot be altered" stops being a claim and becomes mathematical proof:
Claiming "the logs were not altered" carries no weight on its own in court. A cryptographic chain provides mathematical proof — independently verifiable by an expert witness.
When a supervisory authority asks for proof of audit record integrity, the chain verification report is the answer. It operationalises the security obligation under GDPR Article 32 and KVKK Article 12.
For independent audit firms, "log immutability" is a gold-tier control point. An audit hash chain makes this control testable and reproducible.
Three hash fields — a simple but unbreakable mathematical chain:
Each row in the audit log carries three hash fields: prevHash (the previous record's hash), entryHash (a hash of this record's contents), and chainHash (a combination of the two). These three values mathematically tie the chain together.
Modifying an old record would require recomputing and overwriting every chainHash that follows. This breaks timestamps and is detected the instant verification runs.
During verification the server recomputes each record one by one and compares against the stored chainHash. If a single record is corrupted, its id and timestamp are reported — actionable for forensics.
From /settings/compliance/audit-chain in the panel, every tenant can verify the integrity of
their own chain independently — without raising a support ticket, with a single click.
Create your free account. No credit card required. 1,000 sends per month free.