Full Report
Learn what you can do today to prepare for Q-Day
Analysis Summary
# Best Practices: Post-Quantum Cryptography (PQC) Readiness
## Overview
These practices address the preparatory steps necessary to ensure data confidentiality and system trust remain secure against future Cryptographically Relevant Quantum Computers (CRQCs) capable of breaking current asymmetric encryption standards (like RSA and ECC) via Shor's algorithm. The goal is to establish a roadmap for migrating vulnerable cryptographic assets to Post-Quantum Cryptography (PQC) standards before Q-Day (the day a CRQC effectively exists).
## Key Recommendations
### Immediate Actions
1. **Begin Cryptographic Inventory:** Start identifying all cryptographic mechanisms currently in use across the organization, especially focusing on those relying on RSA and Elliptic Curve Cryptography (ECC) for asymmetric encryption and key exchange.
2. **Determine Vulnerability Exposure:** For each identified cryptographic mechanism, determine its exposure level, paying attention to data that requires long-term confidentiality (data harvested today might be decrypted later—"Harvest Now, Decrypt Later" risk).
3. **Establish PQC Migration Task Force:** Formally establish an internal team responsible for assessing risks, tracking migration progress, and selecting future PQC standards.
### Short-term Improvements (1-3 months)
1. **Prioritize High-Risk Assets:** Rank identified cryptographic uses based on the sensitivity of the data protected, the lifespan the protection needs to maintain, and the difficulty/cost of migration. Prioritize systems protecting high-value, long-lived secrets.
2. **Monitor NIST PQC Standardization:** Actively track the progress of the National Institute of Standards and Technology (NIST) Post-Quantum Cryptography standardization process to determine which algorithms will become the new benchmarks.
3. **Implement Cryptographic Agility Audits:** Review systems and applications to assess how difficult it would be to swap out current cryptographic libraries and algorithms for new PQC standards when they are finalized.
### Long-term Strategy (3+ months)
1. **Develop Phased Migration Plan:** Create a detailed, multi-year roadmap for replacing vulnerable algorithms with PQC-compliant alternatives, incorporating testing and shadow deployment phases.
2. **Adopt Cryptographic Agility:** Architect new systems and refactor existing critical ones to support the swapping of cryptographic primitives without requiring extensive, ground-up redevelopment (e.g., using abstraction layers or crypto-agnostic libraries).
3. **Implement Hybrid Mode Testing (where applicable):** Begin testing systems capable of operating in a hybrid mode, using both current standardized encryption and forthcoming PQC candidates simultaneously, to ensure compatibility and performance before full transition.
## Implementation Guidance
### For Small Organizations
- Focus heavily on the **Inventory (Immediate Action)**, leveraging software composition analysis (SCA) tools or vulnerability scanners if available, to identify cryptographic libraries in use within commercial off-the-shelf (COTS) software and cloud services.
- Engage system integrators or trusted cloud providers to identify PQC readiness in managed services, as building custom PQC capabilities internally might be resource-prohibitive.
### For Medium Organizations
- Dedicate resources to detailed **Cryptographic Agility Reviews** for internally developed applications.
- Incorporate PQC readiness metrics into the procurement cycle for all new hardware and software purchases, demanding vendor roadmaps addressing PQC migration.
### For Large Enterprises
- Mandate the use of abstraction layers or standardized cryptographic modules across all development teams to enforce cryptographic agility centrally.
- Leverage dedicated security frameworks (like the one mentioned in the context) to continuously scan the cloud environment for vulnerable encryption protocols (e.g., using cloud security posture management tools).
- Begin planning for the "crypto-agile TLS handshake" by looking at capabilities within load balancers and network gateways.
## Configuration Examples
*The provided context does not detail specific technical configurations (such as code snippets or exact cloud settings) but emphasizes detecting existing vulnerable encryption. Configuration efforts should focus on:*
1. **Enforcing Cryptographic Agility:** Configure Application Security Testing (AST) pipelines to flag dependencies using deprecated asymmetric algorithms (e.g., hardcoded RSA-2048 use without wrapper/abstraction).
2. **Detecting Cryptographic Risks:** Utilize cloud security posture management (CSPM) tools or vendor-specific detection frameworks to continuously monitor for workloads utilizing vulnerable legacy crypto settings.
## Compliance Alignment
The transition to PQC alignment indirectly addresses several core tenets of major security frameworks:
* **NIST SP 800-208 (Recommendation for Approved PQC Algorithms):** This future standard will guide the selection and deployment of algorithms. Readiness efforts should anticipate compliance with the final NIST selections.
* **NIST Cybersecurity Framework (Identify & Protect Functions):** The inventory phase directly aligns with asset management and protective measure planning.
* **CIS Benchmarks (Cryptographic Standards):** Ongoing configuration checks should verify that current systems adhere to the strongest *available* non-quantum-vulnerable encryption standards while planning the upgrade path.
## Common Pitfalls to Avoid
1. **Underestimating Data Lifetime Risk:** Assuming Q-Day readiness can wait until the threat is imminent. Data with a security requirement extending beyond the expected Q-Day timeline (even if 10+ years) needs protection *now*.
2. **Waiting for Final Standards:** Delaying inventory and agility preparation until NIST finalizes all algorithms. Action must start based on early candidate evaluation.
3. **Treating PQC as an Application-Only Issue:** Ignoring the cryptographic protocols used in infrastructure layers, hardware security modules (HSMs), VPNs, and cloud key management services (KMS).
4. **Assuming COTS Software is Safe:** Failing to pressure vendors for PQC roadmaps, as internal development teams may not control cryptographic dependencies buried within third-party components.
## Resources
- NIST Post-Quantum Cryptography Standardization Project documentation (for official algorithm candidates and status updates).
- Vendor/Partner security frameworks designed for PQC inventory and detection (e.g., the "Wiz for Post-Quantum Cryptography Security Framework" mentioned in the source).
- Academic papers and cryptographic research detailing the required qubit counts and timelines for breaking current standards.