Post-Quantum API Security: Preparing your APIs for Q-day
summary
Demonstrates a working Dilithium PQ JWT implementation by forking jose4j and plugging Bouncy Castle as a PQC provider, rebuilding a Layer7 Gateway and adding token-issue and validation endpoints, which successfully validate PQ signatures. Benchmarks show signing slightly faster than RSA‑2048, validation a bit slower, and tokens larger but manageable. Cites research showing breaks with on the order of 6.2 million qubits and warns Q‑day could be around 2030, so retrofit may take years.
AI-written summary · about
chapters (9)
- 0:00Post-quantum API security intro
- 3:17Quantum threat to APIs
- 6:33API exposure post-quantum
- 8:59JWT attacks with quantum
- 10:26Post-quantum JWT at Layer7
- 13:18Performance impact of PQ crypto
- 14:43Q-day timing and prep
- 19:05Retrofitting systems for PQ
- 20:55Quantum readiness roadmap
related talks
30mNavigating the Quantum Readiness Journey: Securing Kubernetes with Quantum-Resis...
46mFrom Theory to Practice: Real-World Lessons in Post-Quantum Cryptography Migration
13mNavigating the Quantum Readiness Journey: Open-Source Cryptography, PKI and Signing Tools
20mPost-Quantum Cryptography- Preparing digital communication for a Q
27mQ-Day Survival Guide: What the Post-quantum Cryptography Transition Means for Confidential Computing
59mPost-quantum cryptography for .NET developers
23mFireside Chat with Charles on Post Quantum World
28mQuantum Proofing Sigstore: A Tale of Three Approaches