Ac Audit Logging

Building logs that serve as evidence rather than telemetry: what events an audit trail must record and who its reader is, tamper-evidence through hash chaining and external anchoring, append-only storage and the deletion problem, query patterns for investigators, retention and privacy tension with the trail's purpose, structured event schema for auditability, and the written audit record. It explains how to make a log that can be trusted after the fact; it never recommends a log product and never claims tamper-proof, only tamper-evident. Use when asking "audit log", "tamper evident", "hash chain log", "append only log", "who changed this record", "immutable log", "audit trail design", "compliance evidence", "log integrity", "sequence number gap". Not for observability and SLO telemetry (ac-reliability), not for structured logging in general (ac-reliability), not for access control decisions themselves (ac-security-engineer).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit e56dc2c76c

Frequently asked questions

npx get-skill add jiayaoqijia/ac-audit-logging