Exporting Compliance Attestation Bundles
Compliance frameworks demand evidence — not platform marketing, not vendor assertions, but structured records that an external assessor can inspect, verify, and incorporate into their attestation report. Kilimanjaro produces these bundles directly from the platform's structural guarantees: the credential matrix, the rotation cadence, the access patterns over the audit window, the platform-signed hash chain that makes every claim tamper-evident and externally verifiable.
This tutorial walks through generating a compliance attestation bundle for a SOC 2 Type II evidence package. The same flow produces HIPAA or FedRAMP bundles — only the framework selection changes.
Prerequisites
- A Warden-role account on the project (Compliance Officers without Warden are insufficient; bundle export is a high-privilege operation)
- The
@k9o/cliinstalled locally - The audit window your assessor is examining (typically a 12-month window for SOC 2 Type II)
Step 1 — Determine the bundle scope
Compliance bundles are scoped to:
- A specific framework (SOC 2, HIPAA, FedRAMP, ISO 27001, etc.)
- A time window
- A set of projects (single project or org-wide)
For a SOC 2 Type II report covering 2025-05-01 → 2026-04-30 across all projects in your org:
Framework: SOC 2 Type II (Common Criteria + Trust Services Criteria)
Window: 2025-05-01T00:00:00Z → 2026-04-30T23:59:59Z
Scope: org_<your_org_id> (all projects)
Step 2 — Invoke the export
Trigger the export via the Console (Compliance → Attestation bundles → New export) or the CLI's compliance-export command (canonical syntax in the CLI reference). The export request is MFA-gated and runs through the platform's compliance service, which:
- Authenticates the Warden session
- Submits the export through the IRREVERSIBLE_ACTION_GATE for compliance-bundle exports
- Assembles the bundle from the platform's structural guarantees: credential matrix, rotation cadence, access patterns, audit-log summary, threat-model coverage
- Signs the bundle with the platform's compliance signing key (RSA-2048+SHA-256)
- Returns a downloadable signed archive
Bundle size scales with org size and audit window. Larger orgs (or longer windows) produce larger bundles; very large orgs can scope exports per project rather than org-wide.
Step 3 — What's inside the bundle
The signed archive contains structured artefacts spanning the platform's compliance posture for the requested window:
- A manifest with bundle metadata and integrity hashes, plus the platform signature over the manifest
- A credential-matrix section covering the role taxonomy, rotation history, and per-rotation attestations
- A policy-evidence section with policy snapshots, decision summaries, and IRREVERSIBLE_ACTION_GATE exercises within the window
- An audit-chain section with ledger summary, the offline verification report for the full window, transparency-anchor checkpoints, and the published signing keys for the window
- A threat-model-coverage section per surface (Infrastructure, Cryptographic Boundary, Isolation & Privilege, Identity-Aware Kernel, Injection)
- A compliance-mapping section that ties platform controls to the framework's criteria (Trust Services Criteria + Common Criteria for SOC 2)
- A README explaining how to interpret each artefact
Every artefact is machine-readable and most are paired with human-readable PDF summaries.
Step 4 — Verify the bundle's integrity
Before delivering to your assessor, verify the bundle with the platform's bundle-verification tool (Console or CLI per the canonical surface). The verifier extracts the bundle, verifies the manifest signature against the platform's compliance signing key, checks each artefact's hash against the manifest, verifies the embedded audit-chain verification report is itself signed and intact, and reports overall status.
For a clean bundle:
A clean verification reports overall integrity as VALID, with the manifest signature verified, all artefact hashes matching the manifest, the embedded audit chain verified across the requested window, and the external transparency-anchor checkpoints matched. Any deviation surfaces as a verification failure rather than a silent corruption.
Step 5 — Deliver to your assessor
Send the bundle to your SOC 2 assessor along with:
- The platform's compliance signing public key (so they can re-verify on their side)
- The transparency anchor public URL (so they can re-verify the external anchor)
- A walk-through call (typically requested) where you show the assessor how to verify on their end
A competent assessor can independently verify every claim in the bundle — there is no "trust the platform" gap.
Step 6 — Repeat per audit cycle
Compliance audits are recurring; the bundle export is a routine operation. Common cadences:
| Framework | Bundle frequency |
|---|---|
| SOC 2 Type II | Annually (the audit period itself is 6–12 months) |
| HIPAA | Per-incident or per-relationship; not on a fixed cycle |
| FedRAMP | Continuous monitoring; quarterly or monthly attestation bundles |
| ISO 27001 | Annually for surveillance; tri-annually for full recertification |
Scheduled exports are supported per the platform's scheduling surface for bundles produced automatically on a cadence.
Step 7 — Customer-attestable evidence (pre-formal-attestation)
If your project is in a window where the platform's own formal attestations are still in pursuit (per Security → Compliance), the bundle is still useful: it provides customer-attestable evidence for your own vendor-risk-management process. Many enterprise procurement workflows accept customer-attestable evidence in lieu of formal third-party attestation while the platform's attestation cycles complete. Surface the gap explicitly to your assessor — they will know how to incorporate it.
What just happened
You produced a structured, signed, externally-verifiable evidence package directly from the platform's audit and structural surfaces. The package is the platform's compliance posture, materialised for a specific framework and window. No screenshots, no manual evidence collection, no "we assert that we do X" — the package is the evidence.
The same flow works for any of the supported frameworks; only the --framework flag and the artefact selection differ.
Next
- Out-of-Band Ledger Verification — independently verify the audit-chain artefact in the bundle.
- Forensic Audit Trail Discovery — drill into specific events the bundle references.
- Security → Compliance — the broader compliance posture and pursuit status.