Tamper-Evident Audit Record
A tamper-evident audit record is a log entry for one decision that is hashed, hash-chained to the record before it, and kept write-once, so that changing any record breaks the chain at that point.
Why tamper-evidence matters
A log that an administrator can edit proves little. A tamper-evident, hash-chained record shows any change without requiring you to trust the vendor or the operator.
In Raidu
Every decision is written once with SHA-256 per record, chained by previous hash, anchored outside the database and kept write-once for ten years. Records are linked so any change shows. Database triggers refuse updates and deletes. See Evidence and Audit.
Questions about Tamper-Evident Audit Record.
Can an admin delete a record? +
How does this work with GDPR erasure? +
Agent Firewall
An agent firewall applies policy to what AI agents do, not only what they say. It checks every tool call on the way out and scans what the …
Read ›AI FinOps
AI FinOps is the practice of managing what AI model calls cost: setting budgets per team, attributing every call to the team and decision …
Read ›AI Firewall
An AI firewall is a control that sits between people, apps and agents and the AI models they call. It checks every prompt, agent step and …
Read ›Raidu is the accountability layer for your data and your AI. Intercept. Explain. Prove.
See the runtime, the tamper-evident record, and what a regulator-ready trail looks like for your AI stack.