AxioRankDocs

Compliance evidence bundle

One zip of offline-verifiable evidence for SOC 2, ISO 27001, HIPAA, and more, assembled live from your control plane.

When an auditor asks how you govern your AI agents, the evidence bundle is the answer: a one-click zip, assembled live from your control plane, that an auditor can verify offline without an AxioRank account. By default every artifact is mapped to SOC 2 (Trust Services Criteria) and ISO/IEC 27001:2022 Annex A controls in the bundled CONTROLS.md. Other framework profiles (HIPAA, NIST AI RMF, ISO 42001, and more) are one query parameter away (see Framework profiles).

The bundle is a point-in-time snapshot. Activity counts cover the trailing 90 days; the integrity artifacts cover the audit ledger's entire checkpoint history. Everything in it is already redacted and safe to leave the platform: the governance config carries no secrets, and the ledger artifacts are signatures and hashes.

Who can generate it

Admins, owners, and security auditors, since the bundle contains the access review and the full governance config. It is available on the Team plan and above; other plans receive a 403.

Generate it

Download it from Dashboard → Zero Trust Maturity (/maturity) or Dashboard → Audit Integrity (/integrity), or hit the route directly:

GET /api/compliance/evidence-bundle

This is a dashboard route authenticated by your signed-in session (it is a download link, not an API-key endpoint). The response is application/zip, named axiorank-evidence-YYYY-MM-DD-90d.zip from the generation date, where the trailing 90d is the evidence window in days (90 by default).

Contents

PathWhat it is
manifest.jsonWorkspace, generation time, the covered period, and a sorted list of every other file in the zip.
README.mdWhat the bundle is and how its folders fit together.
CONTROLS.mdEach artifact mapped to the selected framework's controls (SOC 2 and ISO 27001 by default).
VERIFY.mdStep-by-step offline verification instructions for your auditor.
maturity/scorecard.jsonThe Zero-Trust maturity scorecard: overall tier plus per-domain scores.
maturity/scorecard.htmlThe same scorecard as a self-contained, printable page.
integrity/signed-tree-head.jsonThe latest Ed25519 signed tree head over the sealed audit ledger.
integrity/checkpoints.jsonThe full checkpoint chain: sequence, window, row count, hashes, Merkle root, tree size.
integrity/jwks.jsonThe public signing keys, as published at /api/v1/audit/public-key.
governance/config.jsonThe enforced policy, detector, and response configuration as code.
access/access-review.jsonMembers with roles and join dates, plus MFA and SSO enforcement.
retention/retention-and-siem.jsonAudit and inbound retention windows, and configured SIEM destinations.
activity/decision-summary.jsonAllow, deny, hold, and total decision counts for the 90-day period.

Verify offline

The integrity/ artifacts are designed so an auditor needs nothing but the published public key:

  1. Signature: the signed tree head's Ed25519 signature verifies against a key in integrity/jwks.json. Pin the JWKS out of band (or refetch it from /api/v1/audit/public-key) so verification does not trust the bundle itself.
  2. Chain: each entry in integrity/checkpoints.json links to the previous via prevHash, so any altered, deleted, inserted, or reordered row breaks the chain from that point forward.
  3. Per-row proof: any individual audit row can be proven with a verifiable receipt against the tree head in this bundle.

The open-source verifier runs entirely offline:

npm install @axiorank/audit-verify
import { verifyReceipt } from "@axiorank/audit-verify";

const result = verifyReceipt(receipt, jwks); // jwks pinned out of band
console.log(result.ok, result.checks); // leaf, inclusion, sthSignature, provenance
pip install "axiorank[verify]"
from axiorank import verify_receipt

assert verify_receipt(receipt, jwks) is True

The bundled VERIFY.md walks your auditor through the same steps, so they can verify without ever reading these docs.

Use cases

  • Auditor handoff: drop one zip into the evidence request portal instead of screenshotting a dozen dashboards.
  • Quarterly access review: access/access-review.json is a member, role, MFA, and SSO snapshot you can archive and sign off each quarter.
  • Vendor questionnaires: the scorecard and control mapping answer most "how do you govern agent actions?" questions verbatim.

Guidance, not certification

The control mappings exist to speed your auditor's review. They are not a SOC 2 report or an ISO certificate.

Framework profiles

The default bundle maps to SOC 2 and ISO 27001. The same machinery assembles a pack mapped to a different framework with a ?profile= query parameter on the download route:

GET /api/compliance/evidence-bundle?profile=hipaa
profileFramework
soc2-isoSOC 2 (Trust Services Criteria) and ISO/IEC 27001 (the default).
iso-27001ISO/IEC 27001:2022 on its own.
hipaaHIPAA Security Rule (45 CFR Part 164, Subpart C) safeguards.
eu-ai-actEU AI Act, Articles 12 and 14. See EU AI Act evidence pack.
nist-ai-rmfNIST AI Risk Management Framework.
iso-42001ISO/IEC 42001 AI management system.
au-ai6Australia's Voluntary AI Safety Standard.

An unrecognized value falls back to the default SOC 2 pack. Scheduled evidence delivery takes the same profile, so a recurring HIPAA or EU AI Act pack can land on your evidence endpoint automatically.

Guidance, not certification

Selecting a profile maps the same evidence to that framework's controls to speed an auditor's review. It is not a HIPAA attestation, a SOC 2 report, or an ISO certificate.

Next steps

On this page