Full Report
Post-quantum cryptography protects against quantum threats using today’s hardware. Quantum tech like QKD may sound appealing, but it isn’t necessary or sufficient to secure organizations.
Analysis Summary
# Best Practices: Adopting and Implementing Post-Quantum Cryptography (PQC)
## Overview
These guidelines focus on proactively preparing an organization's cryptographic infrastructure to withstand attacks from future, cryptographically relevant quantum computers (CRQCs). The emphasis is on leveraging current, PQC-ready hardware and algorithmic migration strategies, rather than relying solely on nascent technologies like Quantum Key Distribution (QKD).
## Key Recommendations
### Immediate Actions
1. **Conduct Cryptographic Inventory:** Catalog all cryptographic assets, including algorithms used (e.g., RSA, ECC), key lengths, digital signature schemes, and where they are deployed (e.g., TLS/SSL, code signing, stored data encryption).
2. **Establish PQC Migration Leadership:** Form a cross-functional team (led by Security/IT management) responsible for tracking NIST PQC standardization progress and overseeing the transition roadmap.
3. **Prioritize High-Value Assets:** Identify data and systems whose confidentiality must persist beyond the estimated timeline for CRQC availability ("crypto-agility test for long-lived secrets").
### Short-term Improvements (1-3 months)
1. **Implement Crypto-Agility Planning:** Document the process and dependencies required to rapidly switch cryptographic primitives across the organization once NIST finalizes the PQC standards package.
2. **Test Hybrid Mode Deployment (Pilot):** Begin testing pilot deployments using hybrid cryptography, where security relies on the combination of current classical algorithms *and* candidate PQC schemes (e.g., combining RSA-2048 with an early PQC candidate for TLS connections).
3. **Evaluate Hardware Readiness:** Assess existing hardware and software for potential limitations regarding larger key sizes or new instruction sets required by emerging PQC algorithms.
### Long-term Strategy (3+ months)
1. **Develop a Comprehensive Migration Roadmap:** Create a phased plan mapping the decommissioning of legacy public-key infrastructure (PKI) and the widespread deployment of NIST-approved PQC algorithms across all affected systems.
2. **Integrate PQC into Procurement Policies:** Mandate that all new systems, hardware, and software solutions must support cryptographic agility and have a clear path to adopt standardized PQC algorithms.
3. **Monitor and Test Quantum Readiness:** Establish continuous monitoring to track ongoing NIST standardization updates. Schedule periodic "stress tests" to ensure existing hybrid implementations function correctly and do not introduce performance degradation beyond acceptable levels.
## Implementation Guidance
### For Small Organizations
- **Focus on Inventory and Updates:** Concentrate efforts on identifying the top 5-10 external-facing systems (VPN, web servers) and ensure their cryptographic libraries (e.g., OpenSSL versions) are up-to-date to support future algorithm agility when standards finalize.
- **External Consultation on Roadmap:** Given limited internal expertise, budget for one-time consultation to translate NIST documentation into a simple, actionable checklist.
### For Medium Organizations
- **Dedicated Crypto-Agility Task Force:** Dedicate specific engineering resources to manage cryptographic dependencies within application code and firmware updates.
- **Phased Hybrid Rollout:** Begin deploying hybrid TLS certificates on internal APIs and less critical external services to gain experience before wide deployment.
### For Large Enterprises
- **Establish Centralized Key Management System (KMS) Updates:** Ensure the central KMS infrastructure can manage the diverse key sizes and formats associated with PQC algorithms immediately upon standardization.
- **Comprehensive PKI Overhaul:** Plan for a complete overhaul or major update of the Public Key Infrastructure (PKI) to issue and manage PQC and hybrid certificates at scale, including intermediate CAs.
## Configuration Examples
*(Note: Since NIST standards are evolving, specific algorithm parameters are omitted. The focus is on the architectural approach.)*
**Hybrid TLS Configuration Concept:**
When establishing a secure connection, ensure the handshake utilizes both a legacy algorithm and a standardized PQC algorithm:
* **Digital Signature:** Signatures must be verifiable using both the legacy standard (for backward compatibility) and the new PQC standard.
* **Key Exchange:** The session key should be derived using a combination (hybrid model) of the existing Diffie-Hellman/ECDH key agreement and the new PQC key encapsulation mechanism (KEM) output.
## Compliance Alignment
- **NIST (National Institute of Standards and Technology):** Closely monitor the PQC standardization process (FIPS 203, 204, 186-5 draft standards) as these will become the de facto regulatory baseline for federal and commercial entities relying on US standards.
- **ISO/IEC 19790 / 24759:** Align hardware security module (HSM) readiness and cryptographic module validation processes to accommodate new PQC algorithm requirements.
- **CIS Critical Security Controls (Futureproofing):** Control 15 (Account Monitoring and Control) and Control 17 (Incident Response Management) must be updated to include PQC migration risks as a major threat vector.
## Common Pitfalls to Avoid
- **Over-reliance on QKD:** Do not halt PQC software migration efforts waiting for Quantum Key Distribution (QKD) infrastructure. QKD is highly specialized, expensive, and not yet scalable or sufficient for general-purpose enterprise security.
- **"Rip and Replace" Mentality:** Avoid planning for a single, massive switchover. PQC adoption must be gradual, implemented using hybrid modes to maintain current security while migrating slowly.
- **Ignoring Long-Lived Data:** Failing to address data encrypted *today* that must remain secret for decades (e.g., medical records, intellectual property). This data is vulnerable to "Store Now, Decrypt Later" quantum attacks.
- **Ignoring Crypto-Agility:** Deploying new cryptographic primitives without the system's ability to easily swap them out again if better PQC algorithms emerge—this locks in potentially non-optimal choices.
## Resources
- **NIST PQC Standardization Website:** Official source for algorithm finalization status and draft standards documents (Search: "NIST Post-Quantum Cryptography").
- **Cryptographic Agility Checklists:** Utilize checklists provided by cybersecurity agencies that focus on identifying cryptographic dependencies within software stacks.