TL;DR: PQC-capable HSMs are not always quantum-safe because immutable classical boot keys can keep the hardware root of trust tied to RSA or ECC, according to DigiCert. HSM governance has to account for where the first verification step begins, not just which later operations support PQC.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “Do PQC Certificates Require Quantum-Safe HSMs?”.
Key questions
Q: When do operational controls become acceptable in place of full cryptographic assurance?
A: Only when the organisation explicitly accepts that the trust model is partly procedural and can enforce it with network restriction, personnel governance, and tightly controlled firmware updates.
Q: What breaks when PQC support is treated as the same thing as quantum safety?
A: The control assumption breaks at the boot chain.
Q: How do organisations decide whether an HSM trust model is truly quantum-safe?
A: They should verify the cryptographic primitive protecting the immutable boot key, then check whether every other trust layer depends on that same root.
Practitioner guidance
- Map the hardware root of trust Identify which immutable key verifies boot on each HSM model and whether it is RSA, ECC, or a PQC primitive.
- Separate PQC capability from quantum-safe assurance Treat ML-DSA support, firmware updateability, and immutable boot verification as distinct review items so that signing capability is not mistaken for full device trust.
- Document compensating operational controls Where legacy HSMs remain, record the network restrictions, personnel vetting, and update governance that carry part of the assurance model.
Bottom line: PQC capability and quantum-safe architecture are not the same thing, because the boot trust root can remain classical even when later cryptographic operations have been upgraded.
Glossary terms: Quantum-safe HSM, PQC-capable HSM, Hardware Root Of Trust, Operational security
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Quantum-safe trust begins at the boot chain, not at the certificate. A device that can sign with PQC still depends on its immutable hardware key to verify the first code that runs. If that key is classical, the trust root has not been modernised, only the later stages of the stack have. Practitioners should treat root-of-trust design as a separate assurance decision, not as a side effect of PQC readiness.
A few things that frame the scale:
- 48% of organisations cite cloud-based services as a driver for PKI deployment, according to the 2023 State of Machine Identity Management report.
A question worth separating out:
Q: What is the difference between PQC-capable HSMs and quantum-safe HSMs?
A: PQC-capable HSMs can perform post-quantum operations such as signing or verifying with ML-DSA. Quantum-safe HSMs use PQC throughout the device trust chain, including the immutable boot verification key. The former describes a function; the latter describes an end-to-end assurance model that removes classical cryptographic dependence at the root.
👉 Read our full editorial: PQC-capable HSMs still depend on classical trust at boot