Founding-partner program now open · request a scoped proof →
Sample evidence pack

This is what the auditor actually reads.

A real evidence pack from a leaver-revoke cycle — signal to seal, hash-chained and signed, written to storage you control. Verifiable on your own, without trusting us. This is an illustrative example.

evidence_pack_req-live-1142.json
● Sealed · chain verified ✓
pack_idreq-live-1142
triggerWorkday termination · [email protected] · 2026-05-18 14:32:00Z
policyleaver-revoke-v4 · risk=high · owner=m.smith
scope14 target systems · AD, Okta, AWS, 11 SaaS
— sealed event chain —
14:32:15.847Z · REVOKE_ACCESS
[email protected] · 14 systems · approved by m.smith
sha256: a3f5c2e1b8d7f9a0c4e6…b8d1a3e5
14:32:16.104Z · VERIFY_REMOVED
14 / 14 confirmed removed · prev: 7c2e1a48…b9d4a6
14:32:16.339Z · SEAL_PACK
chain verified ✓ · signed ECDSA P-256 · S3 Object Lock
signatureMEUCIQD… ECDSA P-256 · tenant key
storages3://acme-evidence/sidentiq/ · Object Lock: Compliance · retention 7y

Hash-chained

Each event references the previous event's hash. Change one record and every downstream hash breaks — tampering is detectable.

Signed & sealed

The pack is signed with your tenant's ECDSA key and written to S3 with Object Lock. No one — including us — can silently alter it.

Verifiable offline

An auditor can verify the chain and signature independently, with your public key, without any access to SidentiQ.

Generate one from your environment.

A scoped proof ends with a real evidence pack like this — from your systems, signed with your keys, yours to keep.