Update on end-to-end PKI and HSM integrations with ML-DSA
summary
Benchmarks show HSM behavior varies wildly: some REST or soft HSMs handle tens to hundreds of certificates per second while others drop to ~70 or a few dozen; LMS throughput can be LMS performance <1–5 sig/s on some devices and fails under parallel requests on others. Payload signing limits differ (cloud HSMs may enforce a 4KB limit; tests found payload limits vary 4KB–600MB). PKCS#11 v3.1 supports LMS today and PKCS#11 v3.1 and draft 3.2 adds ML-DSA support, but API and stateful-signature quirks require careful engineering.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:03Introduction
- 2:29PKI migration goals and use cases
- 3:59HSM types and performance
- 7:55Testing ML-DSA and LMS with HSMs
- 12:56Signing size limitations
- 16:07Lessons learned
- 19:45HSM integration APIs
- 21:55Recommendations and future outlook
- 23:24Q&A
related talks
24mReal-World Readiness for PQC: Gaps, Gains, and Groundwork
29mCrunching the Numbers Post Quantum Algorithm Performance
28mMixed Certificate Chains for the Transition to Post Quantum Authentication in PKI
35mThe internet is ready for some PQC certificates
28mQuantum-safe PKI for the German administration
27mImplementing Post Quantum algorithms in PKCS #11
58mPQC Integration in HSMs: From Standards to Strategy
24mHSM Advances Supporting quantum-safe PKI Automation
