Platform / Audit & evidence
Audit & evidence
The evidence layer everything writes into — the reason the rest is worth anything.
Case by case
An auditor asks who approved this access in April.
One record answers it: who, when, what they saw at the time, and what they decided.
→ An answer, not a meeting.
Someone edits the record to tidy something up.
Each entry is chained to the one before it, so the chain visibly breaks. You can check it yourself.
→ Tampering shows.
You need last quarter's evidence pack.
Export it. It is not a project, and it is not a professional services engagement.
→ A download.
Under the hood
What you actually get
The evidence layer everything else writes into.
Immutable by construction
The audit log is append-only at the database level — a trigger blocks deletes and restricts updates — so history cannot be quietly rewritten.
Hash-chained integrity
Entries are HMAC hash-chained to the one before, so an altered record breaks the chain visibly and an exported chain can be re-verified for tampering.
One record, everything
Logins, MFA, decisions, entitlement changes, vault and privileged access, provisioning, rotation, configuration and campaign lifecycle all land in one filterable record.
SIEM fan-out
Forward the firehose to Splunk HEC, Microsoft Sentinel or a generic HTTP sink, batched and filterable, alongside signed outbound webhooks with retry.
Data-subject rights
Built-in data-subject access export and right-to-erasure workflows for privacy requests.
Retention framework
Per-data-class retention policies with dry-run support and versioned, tenant-overlaid resolution — evidence recorded without destructive action until a policy is approved.
Felt first by: GRC, audit, and the CISO. · Take this on its own — every edge speaks the standards your estate already speaks, so replacing it later stays cheap.