The Decision You Face
Your cryptographic infrastructure is currently effective. It's passed audits, documented in your System Security Plan, and mapped to AC-17, SC-8, SC-13, and SC-17. It's protecting Controlled Unclassified Information (CUI) right now. But with NIST set to release post-quantum cryptography (PQC) standards in August 2024 and an executive order pushing migration timelines, you must decide: start migrating now with immature tools and uncertain interoperability, or wait for the ecosystem to mature and risk missing compliance deadlines.
This is a pressing issue. The executive order mandates agencies transition high-value assets to PQC for key establishment by 2030 and digital signatures by 2031. For contractors handling CUI under DFARS 252.204-7012 or pursuing CMMC certification, the question is when to start, not if.
Why You Should Consider Migrating Now
The "harvest now, decrypt later" threat makes waiting risky. Adversaries are collecting encrypted data today, anticipating future quantum computers that can crack current algorithms. If your data's sensitivity lifespan exceeds five years, you're already vulnerable.
NIST's roadmap highlights this urgency, identifying which algorithms need replacement and mapping them to new PQC standards. For highly sensitive data, prioritize key establishment migration over digital signatures.
The hybrid approach offers a practical solution. NIST suggests combining conventional encryption with PQC, likening it to using two padlocks on a door. This allows you to protect data against future quantum threats while maintaining compatibility with systems yet to migrate.
Starting now also builds your team's capabilities. Cryptographic migrations are complex. You'll need to inventory systems using encryption, understand dependencies, test compatibility, update documentation, and retrain staff. The National Cybersecurity Center of Excellence is developing practical blueprints, but execution takes months. Teams starting in 2025 will be ready by 2030. Those waiting until 2028 will struggle.
From a compliance standpoint, early action shows due diligence. When your C3PAO asks about emerging cryptographic threats during your CMMC Level 2 assessment, saying "we've implemented hybrid PQC for CUI at rest" is stronger than "we're monitoring the situation."
Why You Might Wait
However, the tooling isn't ready. NIST released the standards in August 2024, but most commercial products, open-source libraries, and hardware security modules don't yet support the new algorithms. You're facing custom implementations, vendor roadmaps that slip, and integration challenges that consume engineering resources needed for other compliance tasks.
Interoperability is a concern. If you migrate your key establishment to PQC but your cloud provider or partners haven't, you're creating communication barriers. The hybrid approach theoretically addresses this, but in practice, it doubles your cryptographic stacks, increasing complexity and your attack surface.
The standards will evolve. NIST's roadmap notes that some algorithms "might be disallowed in federal systems after a certain date" or "allowed but at the user's own risk." Investing heavily in a specific algorithm in 2025 that gets deprecated in 2027 wastes resources and creates technical debt.
The Government Accountability Office reported that federal agencies haven't fully prepared by identifying vulnerable systems or testing quantum-resistant algorithms. If agencies with cryptographic expertise and NIST support struggle, a 500-person defense contractor faces even greater challenges.
You also face opportunity costs. Your team is already implementing NIST SP 800-171 Rev 3 changes, preparing for CMMC assessments, responding to incident reporting requirements, and managing ongoing authorization activities. Adding a cryptographic migration means other critical tasks may not get done. If those tasks include fixing vulnerabilities from your last assessment, you've made your organization less secure in the name of preparing for a future threat.
Practical Steps for Practitioners
Most organizations are adopting a phased approach based on data sensitivity and system lifecycle. They're inventorying cryptographic implementations now, identifying systems protecting the most sensitive data, and planning to migrate those first when vendor support is available. They're not waiting until 2029, but they're not forcing custom implementations in 2025 either.
The hybrid model is gaining traction selectively. Organizations are using it for high-value cases where complexity is justified, not enterprise-wide. A defense contractor might use hybrid encryption for ITAR-controlled technical data while keeping standard encryption for less sensitive CUI.
Practitioners are closely monitoring vendor roadmaps. When your Hardware Security Module vendor releases PQC support, when your cloud provider adds it to their encryption services, when your VPN appliance gets certified algorithms, that's when migration becomes feasible. The focus shifts from "should we" to "how fast can we execute."
Our Recommendation
Start your inventory and planning now, but don't rush implementation until you have mature tools. The 2030 deadline for key establishment is real, but it's not imminent. You have time to do this right.
Specifically, document every system using cryptography in your boundary. Map which ones protect data with long sensitivity lifespans. Identify which vendor products need replacement or upgrades. Include this in your capital planning. When vendors release PQC-capable versions, you'll know what to buy and where to deploy it.
For systems you're building or upgrading in 2025-2026, design them to support hybrid encryption, even if you don't activate it immediately. The architectural decisions you make now will determine how challenging migration is in 2028.
Don't let PQC distract you from current compliance obligations. An assessor finding gaps in your AC-2 account management or SI-4 system monitoring will issue findings today. A theoretical quantum computer vulnerability is noted as a future concern. Fix the issues that will fail your assessment first.
However, take the "harvest now, decrypt later" threat seriously for your most sensitive data. If you're protecting weapon system designs, intelligence analysis, or long-term strategic plans, the risk isn't theoretical. For those specific cases, accept the complexity of early hybrid implementation. For everything else, plan deliberately and execute when the ecosystem supports you.
