Tamper evidence Enterprise¶
Evidence for an audit is usually screenshots and exports, and the auditor has to trust that nobody edited them. With tamper evidence on, both sides of Vidai seal and sign their records: the gateway seals every call it carries, and Vidai seals its own records (the audit log, every change) and witnesses the gateway's seals. An auditor checks a report alone, offline, trusting only the arithmetic. A change, a deletion or a gap shows.
What Enterprise includes depends on the features your licence includes. On Community, the audit log is still hash-chained and checkable; signed seals on both sides, and the downloads below, come with Enterprise.
How it works¶
- Each record is chained to the one before it. Every few minutes, a seal signs everything written since the last one, and seals are chained too.
- The gateway signs its seals with the gateway's signing key. Once the gateway starts recording, the Control room shows that key marked Not confirmed. Someone with access to the gateway's machine reads its key id there and compares; if they match, an organisation admin chooses Confirm the gateway's key. Until then, a check proves the records are intact, not who sealed them.
- Vidai checks both sides by itself every day, and the whole history every 30 days. Verify now checks what was sealed since the last check; Check everything again checks the whole history, for before an audit.
flowchart LR
subgraph GW[Gateway]
C[Call records] --> GS[Gateway seals<br/>signed with its key]
end
subgraph V[Vidai]
A[Audit log and changes] --> VS[Vidai's seals]
end
GS -->|witnessed| VS
GS & VS --> Rep[Auditor report<br/>records, seals, keys,<br/>signed manifest]
Rep --> Aud[Auditor checks it<br/>on their own machine]
What a check can say¶
| Result | Meaning |
|---|---|
| Verified | Every record on both sides is intact and in order, and the keys are the ones you confirmed |
| Partly verified | Something stopped a full check, and it says what: the gateway didn't answer, isn't recording, its records couldn't be read, its key isn't confirmed yet, or it hasn't recorded Vidai's latest seals |
| Failed | A record or seal doesn't match. Don't hand evidence over before you know why |
| Never verified | No check has run yet |
A failed check is emailed to organisation admins, and Home's Needs attention says when a check fails, the gateway is out of step, or its key needs confirming.

What you hand an auditor¶
| Download | What's in it |
|---|---|
| Auditor report | One zip for a period: the calls (a reproducible sample, or every call, with every high-risk call always included), the period's audit events, the policies in force, both sides' sealed records, seals and keys, the latest check, the settings each call ran under, a README saying how to check it, and a manifest of every file's SHA-256, signed |
| Evidence pack | One zip for a regulator: your AI systems with their risk and owners, the policies in force and every change, oversight (approvals, overrides, Stop AI traffic, exemptions), incidents, retention, the last closed access review and the latest check. Optionally labelled for a regulation, or mapped to a framework's controls (SOC 2, ISO/IEC 27001, ISO/IEC 42001, SOX, NIST AI RMF) |
A sample is sized by Confidence and Tolerable error, and the same Seed always gives the same calls, so an auditor can reproduce it. No prompt text is in either file. Each download is recorded in the audit log.
The auditor checks the report on their own machine without reaching your systems, and can compare a few seal digests with the copies your SIEM keeps. With the gateway's public key, which the report carries, they can check the evidence independently.

What it covers¶
Every call made while tamper evidence is on is attested, and each report's manifest says whether its calls are attested or partly attested. The downloads cover AI requests sent through the gateway. They're evidence: whether it meets a regulation is your auditor's call, and everything they need to make it is in the file.
Related¶
- Audit log: the chain every edition has
- Policies and regulations: downloads for a regulation you follow
- Risk and AI systems: high-risk calls always in the sample
- Access reviews and incidents: what the evidence pack carries
- The parts: the gateway and Vidai, the two sides that seal