HSM & PQC Operations
Deep dive into Hardware Security Modules: PKCS#11 v3.2 PQC mechanisms, vendor comparison, firmware migration, and FIPS 140-3 validation.
Why this matters: Your keys are only as safe as the hardware holding them — HSMs are where PQC migration meets the physical root of trust.
Start here: Step through the 8 PKCS#11 operations in order: each shows the API call and detail, and Execute Operation reveals the expected output — or live output from the in-browser HSM in Live WASM mode.
For your role
- Security Architect
- Step through eight PKCS#11 PQC operations with the on-prem versus cloud comparison, then the nine-vendor comparison by PQC maturity, algorithms and FIPS validation, and the fleet sizing for ten enterprise use cases.
- Researcher / Academic
- Track CMVP and CAVP PQC validation status across HSM vendors in Step 4: it is the current record of which modules have validated ML-KEM and ML-DSA implementations.
- Certification & Validation Engineer
- Step 4 tracks CMVP and CAVP PQC validation status across HSM vendors — read it by stage: a CAVP validation of ML-KEM or ML-DSA is the prerequisite, not a module certificate.
- IT Ops / DevOps
- Plan the firmware migration from classical to PQC with dual partitions in Step 3 and size the fleet in Step 5: the two operations a PQC rollout adds to an HSM estate.
A Hardware Security Module (HSM) is a tamper-resistant physical device that performs cryptographic operations and protects keys within a certified security boundary. The defines four increasing, qualitative security levels. A module's certificate states one overall level; its Security Policy lists the level reached in each requirement area.
Lowest level: basic requirements, production-grade components, no specific physical-security mechanisms required. Not software-only: a Level 1 module can be hardware, software, firmware or hybrid, though many software libraries are validated here.
Tamper-evidence (seals, coatings). Role-based authentication. Minimum OS requirements.
Tamper-resistant. Identity-based authentication. Physical/logical separation of interfaces. Keys zeroed on tamper detection.
Tamper-responsive envelope. Environmental failure protection (voltage, temperature). Complete physical penetration protection.
HSM Integration Architecture
On-Prem vs Cloud HSM
- • Thales Luna 7 (Network HSM, FIPS 140-3 L3)
- • Entrust nShield 5 (FIPS 140-3 L3 certificates #5329 and #4745 cover the nShield 5s module)
- • Utimaco u.trust GP HSM Se-Series (PCIe; see its FIPS status in the vendor deep dive below)
PQC firmware is shipping. Algorithm sets, APIs and validated configurations differ by vendor — see the vendor deep dive below.
- • AWS CloudHSM (ML-DSA keys in the HSM; whether ML-DSA counts as FIPS-approved is unreconciled, see the Cloud HSM deep dive)
- • Azure Dedicated HSM (Thales Luna 7; PQC needs a customer-administered firmware upgrade; retiring)
- • Google Cloud HSM (Cloud KMS lists no PQC algorithm for HSM keys)
Cloud PQC support is uneven: check each service's own documentation (checked 15 Oct 2026)
Ready to explore HSM operations?
Step through PKCS#11 PQC operations, compare vendors, and plan firmware migrations in the interactive workshop.
Related Resources
Products shown here are a representative selection — not an exhaustive list. For the full vendor landscape with PQC readiness status, visit the Tools & Products tab in this module or browse the Migrate catalog →
Check off all sections and mark this reading done.
Related modules
- ACVP Lab Workflow: From Vector Set to EvidenceSame track · Hardware Infrastructure · Shares ML-KEM, ML-DSA, PKCS#11
- Homomorphic Encryption (FHE)Same track · Hardware Infrastructure · Same migration phase · Shares ML-DSA, ML-KEM
- Confidential Computing & TEEsSame track · Hardware Infrastructure · Same migration phase · Shares ML-DSA, ML-KEM
- Secure Boot & Firmware PQCSame track · Hardware Infrastructure · Same migration phase · Shares ML-DSA, ML-KEM
In the Industry Landscape
- Hardware Security ModulesPQC key generation & side-channel hardening · PKCS#11 / KMIP interface migration · Root-of-trust & firmware signing · +3 more
- Semiconductors / Secure ElementsTPM 2.0 chips (platform keys and attestation) · PQC in security controllers, TPMs & microcontrollers (chip-vendor statements)
- Cloud Computing / Data CentersBy protocol · Cloud KMS / BYOK key wrapping and API transport · Cloud HSM root keys & FIPS modules
- Cryptocurrency / BlockchainBy protocol · Exchange & custody key management
- Finance & BankingBy protocol · HSM key management & wrapping
Check your understanding
15 questions on HSM & PQC Operations, each with its answer and the reason.
Take the quizNext step
Produce the artifact: Infrastructure Modernization PlannerThis module belongs to phase 6 (Infrastructure & Performance); Infrastructure Modernization Planner produces a deliverable of that phase in the Command Center.
Production Tool Capabilities & Verification ChecklistHSM Administrators & Cryptographic Custodians
Capabilities to require in your production tools:
- OASIS PKCS#11 v3.2 interface supporting `C_EncapsulateKey`, `C_DecapsulateKey`, `CKM_ML_KEM`, `CKM_ML_DSA`, `CKM_SLH_DSA`, and `CKA_PARAMETER_SET`.
- FIPS 140-3 Level 3 physical security, with documented non-invasive (side-channel) attack mitigations, for firmware executing PQC primitives inside the cryptographic boundary.
- Partition-level mechanism policy enforcement blocking deprecated classical algorithms (`CKM_RSA_PKCS`, `<2048-bit RSA`).
How to evaluate in your environment
Query HSM partition capabilities (`pkcs11-tool --list-mechanisms`) and execute `C_EncapsulateKey` / `C_Sign` KAT vectors on a staging HSM slot.
Production evidence to collect
HSM firmware version and CMVP certificate reference, `pkcs11-tool` mechanism list, and signed HSM audit log.
Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.
Record evidence for your environment
Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.
Evidence missing. 0 of 3 requirements have a reference or scope rationale.
Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.