Out-of-Band Ledger Verification
The platform's audit ledger is hash-chained and signed. Verifying it inside the Console is convenient for routine investigation; verifying it out-of-band — using a downloaded export, the platform's published verification key, and an open-source utility you run on your own infrastructure — is the answer for the cases where adversarial scrutiny matters most. Legal discovery, regulatory inquiry, audit committee review, post-incident forensics: any context where the question is "can we prove the platform is not lying to us."
The verification is mathematical. The tool walks the hash chain, verifies each entry's signature against the published key, and reports whether every link is intact. If a single entry has been backdated, modified, or dropped, the chain breaks and the verifier surfaces the divergence.
Prerequisites
- A Warden-role account on the project
- The Kilimanjaro CLI (or the standalone offline-verification utility) installed locally
- About fifteen minutes (longer for very large ledgers)
Step 1 — Obtain the project's public verification key
The verification key is published per the platform's documented verification-key surface (see Kibo Audit Ledger §5 for the canonical reference). Download and save the key locally; it will be the input to the offline verification.
For maximal assurance, verify the downloaded key against the platform's published key-rotation history and fingerprints (see Kibo Audit Ledger §5). In Secure Key Release (SKR) mode, you can additionally obtain the key's hardware attestation chain and verify it against silicon-vendor roots (Intel DCAP, AMD VCEK) — this proves the key was released only to attested Kibo workload code, so a compromise of the platform's web layer could not silently substitute a different key.
Step 2 — Export the ledger
Use the platform's audit-export surface (CLI or Console) to download the ledger for the time window relevant to your investigation. The export is one entry per line, in monotonic sequence order, with every field including the signature. Large projects with high operation volumes produce sizeable exports; the export tooling streams to disk to handle multi-GB ledgers.
For routine compliance review, scope the export to the audit period. For incident response or legal discovery, scope to the broadest window the investigation requires.
Step 3 — Run the offline verification
Invoke the offline verification tool with the public key and the downloaded ledger as inputs. The tool walks the chain entry-by-entry. For a clean ledger, the output reports:
- The total entries verified and the time range covered
- The hash-chain status (intact, no breaks)
- The signature verification status (every entry verified against the published key)
- The genesis anchor (the hash of the project's initial ledger entry, establishing the chain root)
- An overall VALID status
For a tampered ledger, the tool surfaces the specific position of the chain break, the expected and observed hash values at the break, and an overall INTEGRITY VIOLATION status. The break is mathematically definitive — an entry between the surrounding positions was modified, removed, or inserted out of order. The tool does not interpret why the break exists; that is the investigation's next step.
Possible causes of a chain break:
- Storage corruption — a failed disk write somewhere in the platform's storage layer. Cross-region replication should detect this through the platform's own continuous verification; if your offline verification finds a break the platform missed, surface it to the security team immediately.
- Deployment artefact — extremely rare; would also surface in deployment-verification gates.
- Integrity attack — the worst case. The break is the proof; the investigation is to determine scope, attribution, and remediation. The platform's runbooks treat this as a security incident.
A signature failure (rather than a hash-chain break) similarly indicates an integrity violation: an entry exists in the export that the published key did not sign. Either the entry was forged (post-hoc insertion) or the key has been substituted. Both are critical.
Step 4 — Anchor to external transparency
For the highest-assurance contexts, the platform anchors ledger checkpoints into an external transparency log — a Merkle-tree-based public log that the platform commits the project's ledger checkpoint hash to on a configured cadence. The verifier can chain its verification against the transparency log when invoked with the appropriate flag.
The transparency anchor catches a class of attack the hash chain alone cannot: post-hoc rewriting of the entire ledger plus signing-key substitution. The transparency log is operated independently from the platform; an attacker who compromises Kibo cannot also compromise the external log. A divergence between the local ledger's checkpoint hash and the transparency log's anchored hash for the same checkpoint is independent proof of tampering.
Step 5 — Produce a verification report
The verification tool supports producing a structured verification report suitable for audit committee or regulator submission. The report contains:
- The verification command and parameters
- The verifier identity, timestamp, and hostname
- Every check performed (hash chain, signatures, transparency anchor)
- The status of each check
- The exact ledger range covered
- Hash digests of the inputs (ledger file, public key, transparency anchor data)
The report is itself signed, so it is tamper-evident in the same way the ledger is. An auditor can independently re-verify by running the same command against the same inputs and matching the report digest.
What just happened
You produced a mathematically definitive answer to the question "is this ledger intact." The answer does not depend on trusting the platform's runtime, the platform's web layer, or any specific piece of platform code. It depends only on:
- Cryptography (RSA-2048+SHA-256 signature verification, SHA-256 hash chaining)
- The published platform verification key
- The downloaded ledger export
Run this verification routinely — quarterly for compliance hygiene, immediately on demand for any incident response or external inquiry. The cost is minutes; the value is forensic certainty.
Next
- Forensic Audit Trail Discovery — find the specific operations to investigate.
- Exporting Compliance Attestation Bundle — package verification reports into the broader compliance evidence trail.
- Kibo Audit Ledger — the architectural treatment of the ledger and its verification protocol.
- CLI — canonical Kilimanjaro CLI invocation reference, including the audit-export and verification commands.