01Chain
SHA-256 row chaining
Each audit row hashes the previous row’s content into itself — altering an old row breaks every hash after it.
Sovereignty · Audit Log
Tamper-evident by construction, not by promise.
The Voz360 audit log is a hash-chained record of every privileged action: each row is SHA-256 chained to the row before it, written under a row lock, so any tampering breaks the chain and is immediately detectable.
The Voz360 audit log is a hash-chained record of every privileged action: each row is SHA-256 chained to the row before it, written under a row lock, so any tampering breaks the chain and is immediately detectable.
02Lock
Row-locked writes
Chain writes take a FOR UPDATE row lock, so concurrent privileged actions cannot race and corrupt the chain order.
03Verify
Re-hash to detect tampering
A verification pass re-computes the chain from the first row; any mismatch identifies exactly where history was altered.
Questions, answered
What enterprise buying teams want to know.
Self-contained answers, so the questions a security or procurement reviewer asks first don't require reading the whole page.
What counts as a "privileged action" in the audit log?
Role and permission changes, outbound dial placement, recording pause/resume, DEK rotation, and other actions with security or compliance relevance — the exact event taxonomy is confirmed during a security review.
Can an administrator edit or delete an audit row?
The chain design is built so that any modification to a historical row breaks the hash chain from that point forward, making the tampering detectable on the next verification pass.
Talk to Voz360
Run it on your terms.
Bring your deployment constraints, compliance requirements, and channel mix. We will show you exactly where control lives in the architecture.