Tamper-Evident Log

Each entry stores a hash that includes the previous entry's hash, so changing history breaks every later link. The protection is real only if the latest hash is kept somewhere the editor cannot reach, because someone able to rewrite the whole chain can also recompute it. It is distinct from write-once storage and from access controls on the database, and an application that merely does not expose an edit button is not tamper-evident.

• Audit Log
• Hash Pinning
• Incident Response
• Separation of Duties

• What is AI agent monitoring? Definition, scope, and tooling