Demonstration · Key management

ZAP: Zero Trust AI-Managed PQC

A post-quantum migration is not one cryptographic step; it is key generation, distribution, verification, rotation, revocation, and audit, forever. ZAP orchestrates that lifecycle into one governed workflow so the operational burden does not fall on people doing it by hand.

generatedistribute verifyaudit

Demonstration: a walkthrough of the ZAP workflow. Controls are illustrative, not a live key-management console; fingerprints and locators shown are illustrative Sample values.

The lifecycle

One governed workflow

Generate
hedged + pairwise-consistency
Distribute
locator; private key stays home
Verify
verify-after-sign
Audit
hash-chained, continuous

The same flow is applied to every identity ZAP manages, under a Zero Trust policy gate.

Walkthrough

What each step does

  1. Generate a key pair

    ZAP generates a lattice key pair with hedged signing and runs a FIPS 140-3 pairwise-consistency test. A pair that fails the test is withheld, not shipped; the honest error is “keypair withheld,” not “retry.”

    POST /api/keypair/generate
    → { "status": "ok", "kem_fingerprint": "0000samplekem000",
           "dsa_fingerprint": "0000sampledsa000" }  // sample fingerprints, illustrative
  2. Distribute the public key

    The public key is published to a locator service and shared with named recipients. The private key never leaves the node that generated it.

    POST /api/keypair/upload  { "recipients": ["team@group.local"] }
    → { "locator": "SAMPLEdemoLocatorQF000000000000000000000000" }  // sample locator
  3. Verify before trust

    Every signature is checked with verify-after-sign before it is relied upon; recipients verify first. A mismatch surfaces at the AEAD tag, not as a decryption oracle.

  4. Audit continuously

    Generation, rotation, and revocation are recorded in a hash-chained, signed log so the compliance posture is provable rather than asserted.

Try the controls

Live console

A live ZAP console connects to a running key-management node. In this public demonstration the controls are shown as disabled affordances; this page does not generate or manage real keys.

Generate key pair (not enabled) Upload public key (not enabled) View audit log (not enabled)

FLAG: not a live console. Real key generation, distribution, and audit run inside the enclave on an authenticated node, gated by XQ Zero Trust policy (owner / Jason). The controls above are intentionally disabled in this public demo. Fingerprints and locators shown on this page are illustrative samples, not live credentials.

See it against your stack

We will walk ZAP through your actual key lifecycle.