Skip to Content
Documentation menu

Guides

Evidence & audit

Every decision, vote, consent change and configuration change is sealed into an append-only hash chain. The point is evidence an auditor can check without having to trust Authentify.

Four layers of proof

LayerWhat it provesWho can check it
Hash chainNo sealed record was altered, inserted or removed in the middle of the chain.Anyone with the records (dashboard, API, bundle).
Witness (RFC 3161)This authorization existed by a time signed by an independent timestamp authority./verify-witness, no account needed.
CheckpointsThe chain had reached a given head on a given day, so the newest records can’t be quietly dropped or the chain rebuilt.You: you keep the signed copies.
Evidence bundleAll of the above for a period, in one file, signed by Authentify.Your auditor, offline.

The audit log

Dashboard → Monitor → Audit log shows the chain; open any request for its checks, votes, outcome and witness. Over the API (account key or dashboard session):

CallReturns
GET /api/v1/audit-logs?customer_id=…&days=30Sealed records with seal, previous seal and seal version.
GET /api/v1/audit-integrity?customer_id=…The chain re-verified now: records checked and any break found.

Each record's seal covers its own fields and the decided request's immutable fields (action, resource, context, end user, decision), canonicalized with RFC 8785. Changing an amount after the fact breaks the chain at that record.

What isn't stored

Values in context that look like credentials or regulated identifiers are redacted before sealing, so they never become permanent evidence. User tokens from identity providers are never stored, only a hash of their id.

Witnesses

After each /v2/authorize decision is sealed, Authentify asks FreeTSA for an RFC 3161 timestamp of it, in the background, so decisions never wait. The response says witness.status: "pending"; the witness appears on the request moments later. Only a SHA-256 digest leaves Authentify.

From a request's page, Download evidence saves the package. Anyone can check it at /verify-witness: the signature and certificate chain are checked against FreeTSA's own root, which an uploaded file can't replace. A witness proves the record existed by that time; it doesn't backdate anything.

Checkpoints

Once a day, after the chain passes its integrity check, Authentify signs a checkpoint: the head seal and record count, as an EdDSA JWT (typ authentify-checkpoint+jwt), with an independent RFC 3161 timestamp. It is sent to your webhooks as audit.checkpoint.

Keep them

The chain's own checks run inside Authentify's database, so on their own they can't rule out someone with database access deleting the newest records or rebuilding the chain. Your stored checkpoints can't be changed from here.

POST/api/v1/audit-checkpoints/verifyaccount key or session
json
{ "checkpoint": "<JWT you stored>" }

// -> { "valid": true }   or   { "valid": false, "problem": "..." }

valid: false means the log no longer holds what was certified. GET /api/v1/audit-checkpoints lists past checkpoints.

Evidence bundles

A single JSON file your auditor verifies offline: no Authentify account, API call or network access needed.

GET/api/v1/compliance-exports/evidence-bundle?customer_id=…&environment=production&from=…&to=…dashboard session

Omit from/to for the full history (up to 20,000 records per bundle). The auditor runs one dependency-free script (Node 18+):

bash
curl -o jwks.json https://www.authentify.bz/.well-known/jwks.json
node verify-evidence-bundle.mjs authentify-evidence-production.json --jwks jwks.json --tsa-dir ./tokens

It checks, and prints VERIFIED or each failure:

  1. Authentify's signature on the bundle's manifest (so whoever hands it over can't drop the newest records).
  2. The file wasn't edited after export.
  3. Every seal, recomputed and chained from the bundle's anchor.
  4. Full content of every request, including its context.
  5. Completeness up to the latest seal.
  6. That each timestamp names a record in the bundle. The timestamp signatures themselves are checked with OpenSSL against a root certificate the auditor gets from FreeTSA.

Ask us for the verifier script if your auditor doesn't have it.

Compliance coverage

Dashboard → Compliance maps this evidence to controls (Controls & coverage, Coverage) and exports it for the frameworks you select (Exports).