Workshop Description
Key management infrastructure sits at the root of every encryption hierarchy. A compromised root key compromises everything encrypted beneath it. That makes KMS and HSM infrastructure the single highest-priority target for PQC migration in any cloud environment.
This workshop addresses the practical engineering of that migration across the three major cloud KMS platforms (AWS KMS, Azure Key Vault, GCP Cloud KMS) and the on-premises HSM vendors most commonly deployed in enterprise environments (Thales Luna, Utimaco SecurityServer, Entrust nShield). The core challenge is not algorithm selection. FIPS 203 (ML-KEM) and FIPS 204 (ML-DSA) define the target algorithms. The challenge is sequencing: migrating a three-tier key hierarchy (root keys, key-encrypting keys, data-encrypting keys) without disrupting production workloads, while navigating HSM firmware update cycles, FIPS 140-3 revalidation timelines, and cross-region key synchronisation constraints. Participants work through that sequencing problem with their own infrastructure as the reference architecture.
What participants cover
- Cloud KMS PQC readiness: current ML-KEM and ML-DSA support across AWS KMS, Azure Key Vault (including Managed HSM), and GCP Cloud KMS (software and HSM-backed keys)
- On-premises HSM migration: PKCS#11 v3.1 PQC mechanism identifiers, KMIP v2.1 PQC object types, and vendor-specific firmware upgrade paths
- Key hierarchy migration sequencing: root key constraints, hybrid key encapsulation (ML-KEM + ECDH), and re-encryption strategies for data-encrypting keys
- FIPS 140-3 revalidation: how HSM firmware PQC updates interact with existing FIPS validation status and what that means for compliance deadlines
- Compliance drivers: NIST FIPS 203/204/205 timelines, CNSA 2.0 deadlines, ANSSI and BSI guidance, and NIST SP 800-57 key management alignment
- Migration planning: cryptographic inventory methodology for key types and dependencies, risk-based prioritisation of key hierarchies, and vendor engagement checklists