Post-quantum cryptography migration strategy for cloud services
summary
NIST selects lattice KEM Kyber and signatures like Dilithium (plus SPHINCS+ and Falcon) for standardization, and AWS reports working implementations: s2n-tls with PQ hybrids deployed to KMS, Secrets Manager and ACM, and PQ SFTP in AWS Transfer Service configurable via the console. Kyber-512 adds ~750 bytes per direction versus EC, a PQ TLS hybrid handshake adds ~2,500 bytes and ~0.3 ms, and NIST FIPS drafts appear in 2024 with tool and migration expectations from agencies by 2025–2030.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 1:28Quantum computing threat to cryptography
- 8:46Long-term data protection challenges
- 12:02Quantum bits and cryptographic impact
- 16:05Industry post-quantum cryptography efforts
- 18:33NIST selected post-quantum algorithms
- 25:07Global migration plans and timelines
- 28:26AWS post-quantum security strategy
- 31:59Protocol and library development
- 34:12Hybrid key exchange mechanisms
- 37:09Performance of post-quantum TLS
- 39:03Post-quantum SFTP support
- 41:16Migration steps for customers
- 42:40AWS commitment to seamless transition
related talks
15mSecuring Cloud Native Infra for the Post-Quantum Era
43mStatus report on Post Quantum Cryptography Standardization
01h 05mChallenges and Opportunities from Quantum-Safe Cryptography
24mTransitioning to Post-Quantum Cryptography in IAM
01h 02mNIST Post-Quantum Cryptography Update
59mPost-quantum cryptography for .NET developers
13mNavigating the Quantum Readiness Journey: Open-Source Cryptography, PKI and Signing Tools
39mPQC at the European Telecommunications Standards Institute ETSI