Skip to content
Skip to main content
What's Real, What's Simulated
Real in this demo
- RFC 3394 AES Key Wrap with byte-exact RFC test vectors.
- RFC 5649 padded key wrap with byte-exact RFC test vectors.
- AES-256-GCM sealing via WebCrypto.
- SHA-256 hash-chained audit log.
-
HMAC-SHA-256 key-evolving audit log, with the HMAC checked against RFC 4231 and an
independent WebCrypto computation.
-
Key-handle wrap, unwrap and byte-returning decrypt all run real RFC 3394 AES-KW;
every recovered key is confirmed against an independent AES-GCM challenge.
- In-memory DEK zeroization before discard.
Simulated for browser context
- The KMS is an in-memory module, not an HSM-backed service.
- Audit entries persist to localStorage rather than a write-once store.
- Multi-region is represented in one browser runtime.
-
The optional caller/key/operation grant is a teaching check. Caller labels are
unverified browser strings, not IAM identities; the normal API remains permissive.
-
The key-handle token is a small in-memory API model with sensitive handles and
roles, not a hardware token or a PKCS #11 emulator; its bounded explorer searches
only the displayed model.
-
The key-evolving log's logger compromise and erasure of earlier states are modeled
assumptions of the exercise, not properties a browser tab can enforce.
Not included (out of scope)
- Quorum-based key ceremonies.
- FIPS 140-3 certification workflows.
- KMIP wire protocol.
- PKCS#11 HSM bindings.
-
Confidential logging: the key-evolving log is integrity-only, not the full
Schneier–Kelsey protocol or Bellare–Yee's exact construction.