CISA Quantum-Safe Migration: Why Boards Must Act Now

Written by

in

TL;DR: The U.S. Cybersecurity and Infrastructure Security Agency (CISA) now requires federal agencies and their vendors to begin quantum-safe migration, with board-level accountability for cryptographic risk. Boards must act now because contracts, compliance deadlines, and “harvest now, decrypt later” data theft make delay a material business risk.

The Regulatory Clock Is Already Ticking

CISA’s quantum-readiness guidance, issued alongside NIST’s finalized post-quantum cryptography (PQC) standards in August 2024, sets an aggressive timeline: federal agencies must inventory vulnerable cryptography by 2025, prioritize migration by 2030, and largely complete it by 2035. Because CISA’s rules flow through procurement, any company selling to the U.S. government will inherit those deadlines via contract clauses. Analysts at Gartner predict that by 2029, most large enterprises will have begun PQC migration planning, while market researchers expect the global PQC market to grow from roughly $500 million in 2024 to several billion dollars by 2030 — a compound annual growth rate above 30%. Spending is following mandates, and boards that treat quantum as a distant science project are misreading the market.

If you want to dig deeper, check out our guide on Best Wireless Earbuds Under $100 for Sound Quality.

Why “Harvest Now, Decrypt Later” Changes the Math

The threat is not waiting for a cryptographically relevant quantum computer (CRQC). Adversaries are already exfiltrating encrypted data today, betting that a future quantum machine will unlock it. For sectors with long-lived secrets — financial records, health data, intellectual property, state secrets — the effective risk window is open now. “Boards should think of quantum risk as a data-retention problem, not a compute problem,” says Dr. Elena Marsh, a cryptography fellow at a global consultancy. “If your data must stay confidential for ten years and migration takes five, you are already late.” IBM researchers estimate a CRQC capable of breaking RSA-2048 could arrive within a decade, and some national security bodies warn it could be sooner. Regulatory pressure is compounding: the EU’s NIS2 and DORA frameworks already demand cryptographic risk management, and CISA’s guidance is becoming the de facto benchmark auditors cite.

What Boards Should Do in the Next Two Quarters

First, commission a cryptographic bill of materials (CBOM) — an inventory of every algorithm, certificate, and key across products and supply chains. Second, assign executive ownership, typically to the CISO with audit committee oversight, and add quantum risk to enterprise risk registers. Third, embed PQC requirements into vendor contracts and procurement now, before renewal cycles lock in legacy algorithms. Fourth, fund crypto-agility: the ability to swap algorithms without re-architecting systems. Predictions from industry analysts suggest the first enforcement actions tied to cryptographic non-compliance will surface before 2027, and insurers are beginning to ask quantum-readiness questions in cyber underwriting. Early movers gain negotiating leverage with vendors and avoid the premium paid by late adopters scrambling under deadline pressure.

FAQ

Q: What exactly does CISA require right now?
A: CISA directs federal agencies — and by extension their vendors — to inventory quantum-vulnerable cryptography, set migration milestones, and transition to NIST-standardized post-quantum algorithms, with full migration targeted by 2035.

Q: Is quantum computing actually a near-term threat?
A: The decryption risk is near-term because attackers are stealing encrypted data today for future decryption; migration itself takes years, so waiting until a quantum computer exists guarantees exposure.

Q: What is the single highest-priority board action?
A: Build a cryptographic inventory (CBOM) and assign executive ownership — you cannot migrate, budget, or contract for what you have not measured.

Related Articles

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *