Securing Multi-Cloud APIs Against Quantum Threats
summary
Argues that “harvest now, decrypt later” is an immediate risk and points to NIST-chosen algorithms Kyber and Dilithium (with hash‑based and Falcon options as diversity), recommends a hybrid ECDH+ML‑KEM handshake so attackers must break both, and prescribes a five‑level agility model plus a four‑phase migration roadmap. Notes measurable tradeoffs: larger keys increase handshake size but can be mitigated with session resumption, connection pooling and HTTP/2/3 multiplexing, and prioritizes APIs handling decades‑long confidential data for early migration.
AI-written summary · about
chapters (13)
- 0:00Welcome and Speaker Intro
- 0:31Quantum Threat Overview
- 1:14Harvest Now Decrypt Later
- 2:19Beyond the Perimeter Risks
- 3:44Risk Assessment Framework
- 4:51NIST Standards and Mandate
- 5:36Post Quantum Algorithms
- 6:27Hybrid Crypto Strategy
- 7:02Crypto Agility Maturity Model
- 7:44Performance and Benchmarking
- 8:12Four Phase Migration Roadmap
- 8:49Program Governance and Timelines
- 9:58Call to Action and Closing
related talks
15mSecuring Cloud Native Infra for the Post-Quantum Era
24mTransitioning to Post-Quantum Cryptography in IAM
01h 05mChallenges and Opportunities from Quantum-Safe Cryptography
26mCryptographic Agility: Preparing Modern Apps for Quantum Safety and Beyond
46mAchieving Quantum Readiness: A Comprehensive Approach
44mPost-quantum cryptography migration strategy for cloud services
30mNavigating the Quantum Readiness Journey: Securing Kubernetes with Quantum-Resis...
32mCybersecurity in Post Quantum Era