Introduction to Quantum Threats
Quantum computers pose an existential threat to current public-key cryptography. While practical quantum computers are years away, the "harvest now, decrypt later" threat demands action today.
The Quantum Threat Timeline
Current State:
Largest quantum computers: ~1,000 qubits
Cryptographically relevant: ~4,000+ logical qubits needed
Estimated timeline: 10-15 years
Some estimates: As early as 2030
Why Act Now?
Harvest Now, Decrypt Later:
Adversaries collecting encrypted data today
Will decrypt when quantum computers available
Long-lived secrets at immediate risk
State actors actively collecting
Cryptographic Vulnerabilities
Algorithms at Risk
Broken by Quantum Computers:
RSA (all key sizes)
ECC (Elliptic Curve Cryptography)
DH (Diffie-Hellman)
DSA (Digital Signature Algorithm)
ECDSA, ECDH
Weakened but Usable:
AES (use 256-bit)
SHA-3 (use longer outputs)
Symmetric algorithms generally safe
Impact Assessment
Affected Systems:
TLS/SSL communications
VPN tunnels
Digital signatures
PKI infrastructure
Code signing
Encrypted storage
Blockchain
NIST Post-Quantum Standards
Selected Algorithms
Key Encapsulation (Encryption):
ML-KEM (CRYSTALS-Kyber) - Primary standard
Based on lattice problems
Fast performance
Moderate key sizes
Digital Signatures:
ML-DSA (CRYSTALS-Dilithium) - Primary standard
SLH-DSA (SPHINCS+) - Hash-based backup
FN-DSA (FALCON) - Compact signatures
Algorithm Comparison
ML-KEM (Kyber):
Key size: ~1.5 KB
Ciphertext: ~1.5 KB
Fast operations
Well-studied
ML-DSA (Dilithium):
Public key: ~1.3 KB
Signature: ~2.4 KB
Fast signing/verification
Migration Strategy
Assessment Phase
Cryptographic Inventory:
All cryptographic uses
Algorithm identification
Key sizes and lifetimes
Dependency mapping
Risk Prioritization:
Data sensitivity
Secrecy lifetime requirements
Exposure to collection
Replacement difficulty
Hybrid Approach
Why Hybrid?
PQC algorithms less mature
Hedge against future breaks
Gradual transition
Compliance flexibility
Implementation:
Combine classical + PQC
Either algorithm compromise required
Standards support hybrid modes
Migration Phases
Phase 1: Preparation
Cryptographic inventory
Risk assessment
Skill development
Tool acquisition
Phase 2: Pilot
Non-critical systems
Internal applications
Testing environments
Performance benchmarking
Phase 3: Migration
Critical systems
External interfaces
PKI transition
Certificate replacement
Phase 4: Optimization
Performance tuning
Monitoring
Pure PQC transition
Legacy deprecation
Technical Implementation
TLS/SSL Migration
Current Support:
OpenSSL 3.x with providers
BoringSSL experimental
Browser experiments
Cloud provider rollouts
Hybrid Modes:
X25519Kyber768
P256Kyber768
Hybrid key exchange
PKI Transition
Challenges:
Larger certificates
Signature size increase
HSM upgrades needed
Backward compatibility
Approach:
Dual certificates
Staged rollout
Validator updates
CRL/OCSP adaptation
Code Signing
Considerations:
Long-lived signatures
Backward verification
Timestamp authorities
Build system updates
Infrastructure Requirements
Hardware Considerations
HSM Requirements:
PQC algorithm support
Larger key storage
Updated firmware
Performance capacity
Network Impact:
Larger handshakes
Bandwidth increase
Latency considerations
MTU issues
Software Updates
Required Updates:
Cryptographic libraries
TLS implementations
PKI software
Applications
Challenges and Solutions
Performance Impact
Challenge: Larger keys and signatures
Solution: Hardware acceleration, caching, hybrid optimization
Compatibility
Challenge: Legacy system support
Solution: Hybrid modes, gradual rollout, protocol negotiation
Key Management
Challenge: Larger key storage
Solution: Key hierarchy optimization, HSM upgrades
Certificate Sizes
Challenge: Increased certificate sizes
Solution: Certificate compression, chain optimization
Industry Guidance
Government Mandates
US Requirements:
NSA CNSA 2.0 Suite
OMB M-23-02 memo
CISA PQC guidance
NIST migration guidelines
Timeline:
2025: Inventory complete
2030: Widespread deployment
2035: Mandatory compliance
Industry Standards
Emerging Standards:
IETF PQC drafts
Cloud provider guidelines
Financial sector guidance
Healthcare requirements
Implementation Roadmap
Year 1: Foundation
Cryptographic inventory
Risk assessment
Team training
Vendor engagement
Year 2-3: Pilot
Test implementations
Performance baseline
Process development
Tool validation
Year 3-5: Migration
Production rollout
PKI transition
Application updates
Partner coordination
Year 5+: Optimization
Pure PQC transition
Legacy deprecation
Continuous monitoring
Standard evolution
Conclusion
The quantum threat is real and approaching. Organizations must begin preparing now through cryptographic inventories, risk assessments, and piloting post-quantum solutions. Early movers will have significant advantages in managing this transition smoothly.