KMIP Control Plane
What this means for you
- Executive / Business Leader
- In the guided view, the Learn tab opens with "Crypto agility in three steps" — set the policy, watch a request be refused, watch the estate rekey; the Dev tab is not shown for your role.
- GRC / Risk & Compliance
- On the Policy tab, "Which regime governs you?" loads a policy by regulator — US · NSA CNSA 2.0, US · FIPS 140-3, Germany · BSI — and the Inspect tab's Activity trail records every allow, deny or rekey decision.
- Developer / Engineer
- The Dev tab is a pipeline builder with Builder and Code views, a "Corpus (OASIS conformance)" palette, Run, and "Export .py"; switch View to expert and Inspect adds a "KMIP Wire" view of the TTLV bytes.
- Security Architect
- On Operate, "Plane 2 · KMIP Lifecycle" sends a real KMIP 3.0 request per button, with the algorithm set to "Auto — let the policy decide" or a named set; the Policy tab's Compare and Timeline ("As of" slider) show rules over time.
- Researcher / Academic
- The "CSD02" chip states that KMIP 3.0 is an OASIS committee draft, not a ratified standard; in expert view the Policy tab adds a YAML view of the exact rules and Inspect adds the raw "KMIP Wire" response.
- Certification & Validation Engineer
- On the Policy tab, "Which regime governs you?" includes US · FIPS 140-3; KMIP 3.0 is an OASIS committee draft (the "CSD02" chip), so nothing here is a validated configuration.
- IT Ops / DevOps
- The "Migration Estate" tab asks for keys by business label and lets the policy pick the algorithm; move from classical to hybrid to full PQC and "Key objects on this engine" shows rekeyed successors linked to deactivated predecessors.
- Curious Explorer
- Keep View on "guided" and press "Guided Tour" for step-by-step lessons; everything runs in this tab — no server, no Docker.
An educational KMIP 3.0 control plane + PKCS#11 SoftHSM sandbox, compiled to WebAssembly and running entirely in this tab — no server, no Docker. Every operation is a genuine KMIP request answered by the in-browser Rust engine.
In scopecontrol plane + key management at rest · educational WASM sandbox (not a FIPS 140-3 CMVP-validated HSM) · TLS handshake & persistence → full Docker sandbox
Spec statusKMIP 3.0 is an OASIS committee draft (CSD02, May 2026), not yet a ratified Standard —
Why crypto-agility, not just "post-quantum"
Data encrypted today with classical algorithms can be harvested now and decrypted later, once a cryptographically-relevant quantum computer exists — harvest-now, decrypt-later. The fix isn't swapping in a PQC algorithm once; it's a control plane that can migrate keys again whenever the roadmap changes, so a key-management caller that uses stable key names can keep its calls. Public keys, certificates, verifier support and the rollout order still have to be planned. Everything below is that idea made hands-on — flip the policy strip and watch the same request behave differently.
Want the full-fidelity version with TLS transport and the REST control plane? Run the real pqctoday-kmip server from the Docker sandbox.
Try it
- 1. Predict before you run it.
- 2. Run or change the tool above.
- 3. Explain what the result shows.
In the Policy tab, change the disposition for RSA-3072. Where do you see the effect?
A KMIP client can locate the identifier of a sample signing key. The service refuses to sign for that client identity. What access has been demonstrated?
Related content
Next step
Learn how a KMS manages PQC keysThe KMS module explains the key hierarchy, rotation and provider choices behind the policy you just changed.