Skip to main content

Kibo CLI

The @k9o/cli package covers the Kibo operations that are useful from a terminal: managing vault secrets and verifying an exported audit ledger offline. It is the same k9o binary as the rest of Kilimanjaro. Key rotation, custody-mode transitions, and BYOK or HYOK attachment are not CLI commands; they run through the Console or the API (see Kibo BYOK and Kibo HYOK).

This page covers the Kibo-specific commands; the general CLI surface (installation, authentication, output formats, per-project profiles, CI integration) lives at CLI Overview.

1. Installation​

See CLI Overview §1 for installation paths. After install, verify with k9o --version.

2. Common Kibo commands​

CommandWhat it does
k9o vault-secret list [--prefix <p>]List project secrets (metadata only, no plaintext)
k9o vault-secret get <name> --region <region>Read a secret's metadata
k9o vault-secret create <name> --region <region>Seal a new secret; the value is prompted for without echo, or passed with --value
k9o vault-secret reveal <name> --region <region>Reveal a secret's plaintext
k9o vault-secret update <name> --region <region>Set a new value (bumps the version)
k9o vault-secret rotate <name> --region <region>Re-wrap the secret under a fresh key; the content is unchanged
k9o vault-secret delete <name> --region <region>Retire a secret
k9o ledger verify (--file <ledger> | --stdin)Verify the hash-chain integrity of an exported audit ledger offline; exits non-zero on a chain break

Run k9o <command> --help for the full argument surface.

3. Example: verifying an exported ledger​

k9o ledger verify is a thin launcher over the kibo-ledger-verify binary. The npm package does not ship that binary: put it on PATH or point K9O_LEDGER_VERIFY_BIN at it.

k9o ledger verify --file export.ndjson # chain integrity
k9o ledger verify --file export.ndjson \
--key-set keyset.json --signature @export.sig # also verify the platform signature
cat export.ndjson | k9o ledger verify --stdin --format json # structured verdict for CI

--key-set and --signature must be supplied together. Without them only chain integrity is checked, which is the offline saved-file auditor case. The exit code is 0 when the ledger verifies, 1 when verification fails, and 2 for an operational error before a verdict.

4. SIEM forwarding​

For SIEM forwarding, configure the platform-side SIEM forwarding contract via Console / Security / SIEM; the CLI does not stream the ledger.

5. Output formats + scripting​

Commands support --output json per CLI Overview §7. The json format is best for scripts:

k9o vault-secret list --output json

6. See also​