Evidence and compliance

The hash chain

Audit records chain cryptographically — each record's hash covers the previous one. The dashboard's audit view supports verification, and exports carry the chain so an auditor (or your script) can confirm nothing was edited or dropped after the fact.

SOC 2 style exports

• Filterable, searchable, paginated audit exports (JSON or CSV) with actor, action, timestamp, and chain hash —
• policy approval timelines with proposer and approver identities,
• incident timelines from creation through resolution,
• enclave attestation records for protected actions,
• the release measurement registry: each deployment's enclave measurement, its approval record, and the exact measurement the runtime pins,
• model-coverage evidence — which governed surface sent each observed provider request, and the gaps Kavros explicitly did not observe.

Provable release provenance

Every release ships a signed manifest, SBOM, and build provenance. The enclave image is rebuilt on the customer's Nitro host at deploy time, its measurement is registered and approved (automatically when it matches the runtime's own pin, reviewed by an administrator otherwise), and on-path receipt appraisal refuses any request whose attestation quote does not chain to the AWS Nitro root and match the approved measurement. Coverage, not vibes: the evidence chain runs from signed release, to approved measurement, to per-request enclave receipt.

Framework evidence packs

Evidence packs assemble the artifacts a control framework asks for — access reviews, change approvals, incident handling, data-protection checks — from the records the platform already produces. They speed the conversation with your auditor; they do not, by themselves, make you compliant — the honest boundary, stated up front. The same honesty applies to coverage: model-coverage counts what the enclave path observed and says so; it is not a claim that no request ever bypassed Kavros.

Executive reporting

The executive pack condenses the deployment's posture — agents governed, actions blocked, spend under management, incidents and their resolution — into a form you can forward without redaction work.

Verify it yourself

# export from the dashboard, then check the chain locally
kavros explain 403 --body '{"error":"Blocked by Kavros", ...}'
# → what happened, whether anything reached the target, what to do next

The same plain-language rule applies to evidence: every record should be readable by the person who has to act on it.