Evidence and the auditor report¶
The problem. Evidence gathered by hand is slow to produce and easy to doubt: an auditor can't tell whether an export was edited, or whether it holds every call. With Vidai, records are tamper-evident as they're written, checked every day, and handed over as one signed file. The auditor checks it on their own machine, without access to your systems.
What's tamper-evident, in each edition¶
| Record | Community | Enterprise |
|---|---|---|
| The audit log: every sign-in, change and content read | Each record is chained to the one before, so a change or a gap shows. Check the record walks the chain | The same; with tamper evidence on, Vidai also seals and signs it |
| Calls: what each call was, who made it, what each rule did | Checksummed when exported, so a changed file shows | Enterprise With tamper evidence on, the gateway records each call so a change or a gap shows, and Vidai and the gateway seal and check each other |
What Enterprise includes depends on the features your licence includes. Tamper-evident means a change is detected, not prevented.
Tamper evidence Enterprise¶
One switch, on Proof › Evidence, for both sides: Vidai seals its own records (the audit log, changes, and the gateway's seals it witnesses), and the gateway records each call in its own tamper-evident chain.
flowchart LR
subgraph Vidai
A[Audit log] --> S1[Seals, signed]
C[Changes] --> S1
end
subgraph Gateway
K[Each call's record] --> S2[Seals, signed with the gateway's key]
end
S1 -- witnesses --> S2
S2 -- witnesses --> S1
S1 --> V{Verify}
S2 --> V
V --> R[Verified, Partly verified or Failed]
- The gateway's signing key. When the gateway starts recording, the card shows the key it signs with, Not confirmed. Someone on the gateway's machine prints the key, and an organisation admin confirms they match. Until then a check proves the records are intact, but not who sealed them.
- Checks. Vidai checks what was sealed since the last check every day, and the whole history every 30 days. Verify now runs a check on demand; Check everything again checks the whole history, for before an audit.
- Results. Verified; Partly verified, with why (for example the gateway didn't answer, or its key isn't confirmed yet); or Failed: don't hand evidence over before you know why. A failed check is emailed to organisation admins and shows on Home.

The downloads Enterprise¶
| Download | What's in it |
|---|---|
| Auditor report | One zip for a period: the calls (a sample, or every call), the period's audit events, the policies in force, the key settings each call ran under, Vidai's and the gateway's sealed records, seals and keys, the confirmed trust record, the latest check, a README saying how to check it, and a manifest of every file's SHA-256, signed. Its manifest says whether the calls are attested, partly attested or not recorded |
| Sample of calls | Every high-risk call, plus a seeded random sample of the rest, sized by Confidence (90, 95 or 99%) and Tolerable error (5 or 10%). The same Seed always gives the same calls, so anyone can draw the sample again |
| Every call | Every call in the period |
| Evidence pack | One zip for a regulator or auditor: your AI systems with their risk, owners, teams, models and regions; the policies in force and every change in the period; oversight (approvals, overrides, Stop AI traffic, exemptions); incidents and the register; retention; which system holds what; the last closed access review; the latest verification; and checksums. Optionally labelled for one regulation, or asked For a framework such as SOC 2, when it maps Vidai's records to each control |
No prompt text is included in any of them. Every download is recorded in the audit log, and kept for 7 days.
On Community, Proof › Evidence says that downloading evidence for an auditor comes with the Enterprise edition. You still have the chained audit log, its check, and exports of calls and the audit log.
What the files prove, and what they don't¶
- They prove that the records are complete and unchanged since they were sealed, and, with the gateway's key confirmed, who sealed them.
- They cover AI calls sent through Vidai's gateway, not your other systems or AI calls that don't go through Vidai.
- They're evidence, never a statement that you meet a regulation or that a control is met.
Good to know¶
- Calls made before tamper evidence was switched on stay unattested.
- Switching tamper evidence on or off restarts the gateway for a few seconds; calls in flight finish.
- An auditor report is up to 5 GB; beyond that, choose a sample or a shorter period.