SigilbaseAudit event ingestion API: integration best practices
How to integrate an audit event ingestion API well: idempotency, batching, the outbox pattern, failure alerting and schema design that survives audits.
Notes from the registry.
On provable records, audit evidence, and the design decisions behind Sigilbase.
Subscribe with the Atom feed; there is no newsletter and no tracking of readers.
Start here
Tamper-evident audit logs: what they are, why they matter
What a tamper-evident audit log is, how it differs from ordinary logging, and how hash chains and signed checkpoints turn records into provable evidence. The rest of this section builds on the ideas explained here.
All posts
-
-
The best cryptographic audit log solutions in 2026
Cryptographic audit log solutions compared, from managed services to open-source verifiable logs, and the questions separating provable from promised.
-
How to implement provable audit logs, step by step
How to implement provable audit logs: event schema, hash chains, Merkle checkpoints, signed proofs and independent offline verification, in build order.
-
Audit log requirements for SOC 2, ISO 27001 and PCI DSS
The audit log requirements of SOC 2, ISO 27001 and PCI DSS: events, integrity, retention and review, plus one design that satisfies all three.
-
SEC Rule 17a-4: WORM storage vs the audit-trail alternative
What the SEC's 2022 amendments to Rule 17a-4 changed, what the audit-trail alternative actually requires, and how to evaluate systems against either path.
-
SOC 2 audit evidence: an engineer's guide
SOC 2 audit evidence from the engineering side, covering what auditors request, continuous collection, trustworthy records and a 90-day plan.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.