From Theory to Practice: Real-World Lessons in Post-Quantum Cryptography Migration
summary
Quantum risk is closer than many expect: published estimates drop required logical qubits for breaking RSA‑2048 from ~20 million to under 1 million and surveys show 65% worry about harvest‑now decrypt but only 5% have deployed PQC. Java environments can use MLKEM/MLDSA in JDK24+ or Bouncy Castle 1.79 on older JDKs, JSSE needs BCJSSE or JEP 527 (target Java 27) for TLS PQC. Recommended path: hybrid TLS at the edge, prioritize KEM over signatures, phased outside‑in rollout, and crypto agility via JCA providers with PoC, testing and keystore capacity planning.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:03Post-quantum urgency
- 13:39Java at quantum risk
- 17:19PQC support in Java
- 22:53PQC migration strategy
- 34:24Crypto agility approaches
- 43:36Best practices
related talks
47mReal-World Lessons in Post-Quantum Cryptography Migration
44mTheory to Practice: Real-World Lessons in Post-Quantum Cryptography Migration
51mJava and Post-Quantum Cryptography
24mTransitioning to Post-Quantum Cryptography in IAM
48mSecure Java Applications against Quantum Threats
27mPost-Quantum Cryptography
20mPost-Quantum Cryptography- Preparing digital communication for a Q
59mPost-quantum cryptography for .NET developers