Skip to content
A personal experiment · alpha · code not public yet · no offer, no support Project status →

Audit trail

Every event goes into an append-only hash chain: each record contains the hash of the one before. Event types are a closed, documented list in the contract. Each record carries:

  • the event type and the action, with its risk class;
  • the principal (a user, a device and its level, an agent run and the user it acts for);
  • the approvers, their devices and levels, the display channel (cli, device-app, …);
  • the catalog digest (and the catalog layer, its version and signer), the policy version and the profile;
  • references such as an incident ticket.

Refused proposals and refused approvals are recorded too (op.approval_refused and refusal codes): they show that a rule works. Reads record that they happened and the size of the answer, not its content. A start under a weakened or relaxed configuration is recorded as config.weakened or in core.started.

Terminal window
vcx audit # fetch the chain and verify it on your machine
vaicoa-core audit-verify # verify it from the core's store
vcx audit export --from 2026-11-05T11:47:17Z --to 2026-11-05T12:01:17Z --out export.json
vcx audit verify-export --ca ca.pem export.json

An export contains a time window with anchors before and after it, so completeness can be checked offline; a cut-off export is refused (EXPORT REFUSED: … chain broken).

The signed head. A hash chain alone does not show whether records were cut off at the end: a shorter chain is consistent in itself. So the core signs its head (sequence number and hash) with a dedicated audit key whose certificate its CA issues. vcx remembers the last head it saw and refuses an export that lacks it. This is evidence outside the core, not protection: a core whose audit key is stolen can sign a shortened head. Write the head down elsewhere regularly (a ticket, an email, paper), and compare it later.

Restore drills, game days and access reviews end with a report the core signs with its audit key; the apps and vaicoa-core report drill --verify check the signature. Postmortems build their timeline from the audit. DORA, toil and on-call reports are computed from it.

Vaicoa records who proposed, who approved and who refused what, with which key and through which channel, and what ran. That can help you produce evidence for change management, access management and continuity tests. Whether it is enough for a particular audit is your auditor’s call. Vaicoa Core records facts; it contains no mapping to standards. Catalog entries may carry a controls: label (for example change-management), and since every record names the catalog digest, the labels that applied at the time stay fixed.