Real-World Lessons in Post-Quantum Cryptography Migration
summary
PQC migration is an engineering rollout: start with a four‑layer inventory (dependencies, source/framework calls, configuration/key stores, runtime evidence) and run one safe pilot. Java now exposes ML-KEM/ML-DSA in Java 24 and hybrid TLS in JDK 27; a small Spring Boot demo surfaces 22 crypto touch points and a composite audit finds >3,000, so inventory is nontrivial. Use keytool -list -v, Maven dependency tree, JFR and JSSE debug or packet captures to prove negotiation and verify hybrid key exchange.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker intro
- 0:26Why PQC migration matters now
- 15:54What Java teams need to know
- 23:43Migration mechanics without breaking production
- 37:15Key principles and first steps
- 45:16Summary and closing
related talks
44mTheory to Practice: Real-World Lessons in Post-Quantum Cryptography Migration
46mFrom Theory to Practice: Real-World Lessons in Post-Quantum Cryptography Migration
23mReal-World Post-Quantum Migrations: Lessons Learned and Performance Results
51mJava and Post-Quantum Cryptography
24mTransitioning to Post-Quantum Cryptography in IAM
30mMigrating and benchmarking a banking application
48mSecure Java Applications against Quantum Threats
59mPost-quantum cryptography for .NET developers