Skip to main content

Vault mode

Vault mode is where the platform's encryption custody lives. The custody primitives — Keys, Secrets, the custody-mode ladder, the signed audit ledger, and operational metering — are all reachable from a single sidebar here. Vault is its own mode, peer to Admin and Forge; it isn't a section inside Admin.

Vault mode opens on the Operator dashboard — a Pulse surface showing the operational signal you most often want at a glance: keys active, recent rotation events, next-rotation countdown, custody distribution across modes, recent ledger activity, and any custody-state changes from the last day.

Two role-cohort gates govern access. To reach Vault mode at all, you need to be a project admin. To work with specific surfaces underneath, you also need a Vault-domain role — VAULT_OPERATOR for full mutation, VAULT_AUDITOR for read-only, or the older KIBO_ADMIN role which carries full mutation plus Kibo RBAC management. A read-only auditor can browse the ledger and view usage without holding any custody-mutation power.

Custody modes​

Custody is the mode switcher for your encryption custody. The platform has two distinct axes:

Custody / sovereignty axis — three modes controlling who holds the key:

  • Platform-Managed (default) — Kibo holds the key in a software-protected managed key store.
  • BYOK (Bring Your Own Key) — keys held in your own cloud KMS; Kibo re-wraps DEKs under your KMS-held CEK.
  • HYOK (Hold Your Own Key) — keys held in your own HSM cluster; Kibo never sees the CEK.

SKR (Secure Key Release) is a separate, orthogonal overlay on Platform-Managed — not a rung on the custody ladder. It does not change who holds the key (Kibo still does), but adds attestation-gated key release: keys are issued only to your own verified, attested code. Enabling it requires registering a measurement policy first (the platform returns K9O_ATTESTATION_POLICY_NOT_SET 409 if you attempt to activate it without one).

Ascending to BYOK or HYOK is onboarding-gated by the provider/HSM wizard. Descending to a weaker custody mode is an irreversible action and requires confirmation through the same gate machinery as any other gated change.

Custody-mode transitions are project-scoped — every project has its own custody arrangement, and the substrate is the same across regular Kilimanjaro projects and standalone Kibo projects.

Working with keys​

Keys lists every encryption key protecting your project's data — Customer Encryption Keys (CEKs), per-tenant Data Encryption Keys (DEKs), and any custody-mode-specific keys above. Per-key actions:

  • Rotate a key — generates a new version; existing ciphertext re-wraps under the new key version (for BYOK/HYOK, re-wrap unwraps under the old key version and wraps under the new through the customer's KMS or key manager, so the plaintext CEK never leaves it; for Platform-Managed, re-wrap is performed in-process. In both cases the DEK is zeroized after use)
  • Disable a key — marks it inactive without destroying it
  • Delete a key — gated by an irreversible-action confirmation

The per-key detail surface carries the key's full lineage: version history, rotation cadence, the KMS pin (when BYOK or HYOK), and the corresponding ledger entries.

Working with secrets​

Secrets is your project's encrypted secrets table. Each row is a named secret with metadata visible to anyone with read access; the plaintext value requires an explicit privileged operation. Per-secret actions include creating new versions, rolling back to an earlier version, scoping access via policy, and viewing the access history.

Secrets compose with the rest of the platform: a function in Forge can request a secret by name and receive the plaintext in its execution context (in Secure Key Release (SKR) mode, the function runs inside a hardware-isolated TEE and the secret is released only to attested code); the request is logged in the ledger underneath.

The signed audit ledger​

Ledger is the append-only, hash-chained, platform-signed log of every key and secret operation. Provisioning, rotation, encrypt and decrypt counts, custody transitions, every plaintext-secret resolution — all here, all signed under the platform's audit signing key, all verifiable end-to-end.

The ledger is the forensic backbone of your custody posture. Every entry is signed under the platform's RSA-2048 / SHA-256 audit signing key (a software-protected platform key; in SKR mode, the signing key is custodied in a FIPS 140-3 Level 3 HSM). A read-only VAULT_AUDITOR can browse it without holding any mutation power; that separation is the foundation of the platform's compliance story.

Usage metering​

Usage shows encrypt, decrypt, sign, and verify call counts plus estimated costs, broken out by key, by custody mode, and by time window. The metering pipeline updates roughly hourly and feeds your project's billing.

If you bought just Kibo​

Kibo customers — the standalone secrets-management module — see Vault mode as their primary operational surface. The mode picker hides the other four modes (Workspace, Studio, Forge, Admin) because they don't apply to a Kibo-only project. The Settings pillar remains accessible at the appropriate scope.

To a Kibo customer, the Vault sidebar — Custody, Secrets, Keys, Ledger, Usage, plus the Operator dashboard at the top — is the whole surface. The custody substrate underneath is the same as on a regular Kilimanjaro project; the surrounding interface is what's been pared back.

See also​

  • Orientation — the five modes at a glance.
  • Admin mode — for governance work (Admin's Watchtower has a thin Vault oversight summary with a cross-mode link to Vault).
  • Kibo Overview — the custody architecture and the Application Cryptographic Oracle Protocol.
  • SKR — the integrity mode: measurement policy, CI registration, per-release enforcement.
  • BYOK — the four BYOK providers and the re-wrap discipline.
  • HYOK — the four cloud-managed HSM paths.
  • Audit Ledger — the cryptographic forensic backbone.