
Post-Quantum Cryptography: Why CISOs Must Act Now Before 2030
Quantum threats aren't future problems—they're happening now. Learn why CISOs must prioritize post-quantum cryptography before 2030 to stop \"harvest now, decrypt later\" attacks.
Your encrypted data is being harvested right now. Not in some future scenario. Not after a quantum computer arrives. Today. Nation-state adversaries and sophisticated threat actors are intercepting and archiving encrypted communications, trade secrets, M&A negotiations, and patient health records with a single purpose: decrypt them once quantum computing reaches cryptographic relevance. This strategy has a name. "Harvest now, decrypt later" (HNDL) is not a theoretical risk model; it is an active, ongoing intelligence operation running against your organization at this moment.
What makes HNDL categorically different from every other cybersecurity threat boards have faced is the retroactive liability it creates.
Sensitive communications captured in 2026 could be decrypted in 2032. The breach may not be visible when the data is stolen; it becomes visible years later when the encryption protecting it collapses.
For board members and CEOs, this creates a compliance and litigation exposure that your current security controls simply cannot address. The defenses you believe are working today will be rendered worthless by a technology that does not yet fully exist.
The window for responsible action is closing faster than most organizations realize. Gartner's February 2026 cybersecurity trends report identified post-quantum cryptography as a top strategic priority, warning that asymmetric cryptography will become unsafe by 2030.
Given that a full PQC migration takes two to five years for most organizations, and given the HNDL threat, the mathematical conclusion is clear: organizations that start now in 2026 are on the outer edge of a responsible timeline.
This is not a technical patch your IT team can schedule for next quarter. This is a fundamental infrastructure overhaul requiring executive sponsorship and multi-year budget commitment starting now.
The Market and Regulatory Reality in 2026
The standards are finalized. The mandates are set. The market is repricing risk accordingly.
In August 2024, NIST released its principal PQC standards as Federal Information Processing Standards (FIPS), specifying key establishment and digital signature schemes based on candidates evaluated through a multi-year process.
The standards include three post-quantum cryptographic algorithms: ML-KEM (originally known as CRYSTALS-Kyber), ML-DSA (originally CRYSTALS-Dilithium), and SLH-DSA (initially submitted as SPHINCS+).
These are not drafts. They are production-ready standards available for implementation today.
The regulatory pressure is accelerating on multiple fronts simultaneously.
The NSA's CNSA 2.0 framework requires quantum-safe algorithms for all new national security systems by January 2027, full application migration by 2030, and complete infrastructure migration by 2035.
For government contractors, this timeline is not optional.
On January 23, 2026, CISA released its Product Categories for Technologies That Use Post-Quantum Cryptography Standards, listing categories of products where federal agencies should acquire only PQC-enabled solutions, as required by Executive Order 14306.
The quantum computing market itself reflects how seriously investment capital is treating this threat.
The post-quantum cryptography market is projected to grow from approximately $420 million in 2025 to $2.84 billion by 2030 at a 46.2% CAGR.
That growth trajectory signals enterprise buyers moving from planning to procurement.
Most boards are being asked to approve cryptographic migration budgets without understanding that the data already leaving their networks today carries a time-delayed liability that no firewall, EDR platform, or incident response retainer can eliminate retroactively.
The awareness-to-action gap among security professionals is stark.
While 62 percent of technology and cybersecurity professionals are worried that quantum computing will break today's internet encryption, only 5 percent say it's a high priority for the near future, and just 5 percent say their organizations have a defined quantum computing strategy.
Only 7 percent of respondents say they have a strong understanding of the new NIST standards, and 44 percent admit they have never heard of them.
This data, drawn from ISACA's 2025 Quantum Computing Pulse Poll of more than 2,600 global professionals, represents the single largest organizational readiness gap in enterprise security today.
The Threat Is Accelerating Faster Than Enterprise Timelines
The technical case for urgency sharpened significantly in early 2026.
Google researchers revised the estimated qubit count needed to break RSA-2048 from roughly 20 million in 2019 down to under one million in a 2025 paper. This is a 20-fold reduction achieved through software optimization alone, with no new hardware required. A February 2026 preprint reduced the estimate further, to under 100,000 physical qubits.
These numbers move in one direction only, and consistently ahead of what enterprise security roadmaps anticipated.
Research shows that high-retention sectors such as satellite and health networks face exposure windows extending decades under delayed PQC adoption, while hybrid and forward-secure approaches reduce this risk horizon by over two-thirds.
Sectors handling data with long confidentiality obligations, including healthcare, financial services, legal, and defense contracting, carry the highest immediate exposure.
The international regulatory picture adds further urgency for organizations with cross-border operations.
The EU published a coordinated PQC implementation roadmap on June 23, 2025, targeting critical infrastructure quantum-resistance by 2030, which is more aggressive than U.S. civilian timelines.
The Australian Signals Directorate mandates that traditional asymmetric cryptography must not be used beyond the end of 2030, and organizations should develop a refined plan for transition by the end of 2026, with critical systems commencing transition by the end of 2028.
Understanding Your PQC Migration Scope
PQC migration is not a single technology decision. It is an enterprise-wide cryptographic inventory and replacement program. Every system that uses asymmetric cryptography requires evaluation, prioritization, and scheduled remediation. The table below maps common cryptographic dependencies to their migration complexity and NIST guidance alignment.
| Cryptographic Dependency | Current Vulnerable Standard | NIST PQC Replacement | Migration Complexity |
|---|
| TLS/HTTPS Web Traffic | RSA, ECDSA, ECDH | ML-KEM (FIPS 203), ML-DSA (FIPS 204) | Medium: vendor/browser coordination required |
| Code Signing & Software Updates | RSA-2048, ECDSA | ML-DSA (FIPS 204), SLH-DSA (FIPS 205) | High: supply chain and toolchain changes |
| VPN & Remote Access | IKE/IPsec with RSA/ECC | ML-KEM hybrid key exchange | Medium: firmware/vendor dependent |
| PKI & Certificate Infrastructure | RSA, ECC certificates | ML-DSA, SLH-DSA | Very High: full CA rebuild required |
| API Authentication & JWTs | RSA-based signing | ML-DSA | Medium: application-layer refactoring |
| Embedded Systems & IoT | ECC, RSA | Algorithm-specific; constrained environments | Very High: hardware replacement may be needed |
| Key Management Systems (KMS) | RSA key wrapping | ML-KEM | High: HSM vendor roadmap dependent |
| Email Encryption (S/MIME, PGP) | RSA, ECC | ML-DSA, ML-KEM | Low-Medium: tooling exists, user rollout complex |
With the release of the first three final PQC standards, organizations should begin migrating their systems to quantum-resistant cryptography. Cybersecurity products, services, and protocols will need updates, and organizations must identify where vulnerable algorithms are used and plan to replace or update them.
Framework Alignment: Connecting PQC to What Your Board Already Approves
Boards approve risk frameworks, not cryptographic algorithms. The most effective path to executive authorization for PQC migration investment runs through frameworks your governance and compliance teams already operate.
NIST Cybersecurity Framework 2.0 maps directly to PQC readiness. The Identify function covers cryptographic asset discovery and inventory. The Protect function encompasses algorithm migration and implementation of FIPS 203-205 standards. The Detect function includes monitoring for quantum-relevant threat intelligence. The Govern function, new to CSF 2.0, addresses exactly the kind of multi-year strategic program PQC migration requires.
NIST's CSWP 39, finalized on December 19, 2025, defined cryptographic agility as an essential capability, introducing a maturity model. CSWP 48, published as an initial public draft on September 18, 2025, maps PQC capabilities to the NIST Cybersecurity Framework 2.0 and SP 800-53 Rev. 5 controls, giving governance teams a structured method for expressing PQC migration as auditable risk outcomes rather than an isolated engineering project.
ISO/IEC 27001:2022 organizations can anchor PQC migration under Annex A control A.8.24 (use of cryptography), which requires organizations to define and implement rules for the effective use of cryptography. CIS Controls v8 Control 3 (Data Protection) and Control 16 (Application Software Security) provide additional mapping points for organizations that report against CIS benchmarks.
Emerging Trends Shaping the Next 36 Months
Cryptographic Agility Becomes a Board-Level KPI
Cryptographic agility, the organizational capacity to rapidly swap cryptographic algorithms without system-wide disruption, is moving from a technical preference to a governance requirement.
PQC readiness includes asset discovery, protocol mapping, crypto-agility, hybrid testing, and alignment with applicable standards and timelines.
Organizations that invest in cryptographic agility now will be positioned to respond to future algorithm deprecations without emergency remediation cycles.
Hybrid Cryptography as the Transition Bridge
Hybrid cryptography combines classical and post-quantum algorithms. The goal is resilience: even if one algorithm is later broken, the other still provides security. That makes hybrids a useful transitional tool during migration.
Major cloud providers have already moved on this.
Major providers including AWS, Google Cloud, and Microsoft Azure have announced hybrid TLS support by 2024-2025 and full PQC migration targets by 2028-2030.
Vendor Contracts Are Becoming a Compliance Battleground
Government contractors face specific near-term deadlines.
By 2027, all new acquisitions for national security systems are required to use NSA-approved quantum-resistant algorithms pursuant to CNSSP 15, with all NSS required to be quantum-resistant by 2035 per NSM-10.
Private sector organizations supplying regulated industries should expect quantum-readiness clauses to appear in enterprise vendor assessments throughout 2026 and 2027.
FIPS 140-2 Deprecation Creates an Immediate Compliance Deadline
A parallel compliance deadline that CISOs should track: on September 21, 2026, NIST's Cryptographic Module Validation Program (CMVP) will move all remaining FIPS 140-2 validated certificates to the Historical list.
Organizations relying on FIPS 140-2 validated modules for compliance purposes face a deadline that is months away, not years.
Your PQC Readiness Assessment: 10 Questions Your Board Should Ask Today
Use this checklist to assess your organization's current quantum readiness posture. Each "No" or "Unknown" answer represents a gap requiring executive attention.
| # | Board-Level Readiness Question | Status |
| 1 | Do we have a complete cryptographic asset inventory across all systems? | Yes / No / Unknown |
| 2 | Have we identified which data assets carry confidentiality requirements beyond 2030? | Yes / No / Unknown |
| 3 | Do we have a board-approved PQC migration roadmap with budget allocation? | Yes / No / Unknown |
| 4 | Has our risk register been updated to include HNDL exposure for high-value data? | Yes / No / Unknown |
| 5 | Have we assessed our third-party vendors' PQC migration timelines? | Yes / No / Unknown |
| 6 | Do we understand our FIPS 140-2 certificate status ahead of the September 2026 CMVP deadline? | Yes / No / Unknown |
| 7 | Are government contracts or regulated data in scope for NSA CNSA 2.0 or NSM-10 obligations? | Yes / No / Unknown |
| 8 | Does our security architecture support cryptographic agility for rapid algorithm replacement? | Yes / No / Unknown |
| 9 | Have we mapped our PQC obligations under NIST CSF 2.0 and applicable compliance frameworks? | Yes / No / Unknown |
| 10 | Does our board receive regular reporting on cryptographic risk posture? | Yes / No / Unknown |
Organizations scoring fewer than five "Yes" responses carry material quantum risk exposure that is likely unquantified in current enterprise risk assessments.
The Practical Migration Roadmap: Four Phases Executives Must Fund
A credible PQC migration program runs in four phases that must be sequenced properly to avoid remediation debt.
Phase 1: Discovery and Inventory (Months 1-6). Conduct a full cryptographic asset inventory. Every certificate, key, VPN tunnel, API, signing process, and embedded system must be catalogued. This is the most labor-intensive phase and the one organizations most frequently underestimate. No migration plan can be costed or scheduled without it.
Phase 2: Risk Prioritization and Roadmap Development (Months 4-9). Classify cryptographic assets by data sensitivity, system criticality, and confidentiality shelf life. Systems handling data that must remain confidential past 2030 require the fastest migration path. Develop a multi-year roadmap with milestone dates tied to regulatory deadlines, including the NIST PQC migration guidance and CISA's PQC product categories.
Phase 3: Pilot Implementation and Vendor Alignment (Months 9-18). Implement hybrid TLS and FIPS 203/204/205 standards in controlled environments. Engage every major technology vendor on their PQC roadmap and contractual commitments. Identify embedded systems and IoT infrastructure that may require hardware replacement rather than software updates.
Phase 4: Enterprise Rollout and Continuous Monitoring (Months 18-60+). Execute migration by asset class in priority order. Establish cryptographic agility as an ongoing capability so future algorithm changes do not trigger another full-scale emergency program. Build PQC readiness into all new vendor procurement and contract language.
How I Help
Most organizations approaching PQC migration face the same fundamental gap: the technical expertise to understand what must change, but no strategic leadership to translate that into a board-approved program with accountable timelines and defensible risk decisions. That is precisely where a Fractional CISO delivers disproportionate value.
With 20+ years of security leadership experience, I provide the strategic direction your PQC migration program requires without the cost or lead time of a full-time CISO hire. I build your cryptographic inventory framework, develop the board-ready risk narrative that connects HNDL exposure to financial and regulatory liability, and own the executive reporting cadence that keeps your migration on track and your board informed. For organizations that have never had a CISO-level voice translating quantum risk into governance language, this is the engagement that prevents a future crisis from becoming an avoidable one.
For organizations with existing compliance obligations, my compliance advisory services connect your PQC migration directly to NIST CSF 2.0, ISO 27001, and applicable regulatory frameworks. My board advisory services help directors develop the quantum literacy and oversight vocabulary needed to fulfill their fiduciary duty on this issue. For organizations developing AI-enabled systems, my AI governance practice ensures your AI cryptographic dependencies are assessed alongside your broader migration program. Organizations redesigning infrastructure for quantum resilience will benefit from my security architecture services, which integrate PQC requirements into system design from the ground up.
The 2030 threshold is not abstract. It is a compliance and liability deadline with regulatory, contractual, and reputational consequences that are already being shaped by decisions organizations make in 2026. The organizations that will navigate this transition successfully are the ones that treat it as a strategic program requiring executive ownership, not a technical project delegated below the leadership line.
Schedule a discovery call to assess your organization's current quantum readiness posture and identify your highest-priority migration actions. The conversation takes 30 minutes. The exposure you are carrying right now does not.
Adil Karam
Security & AI Governance Advisor
Helping organizations navigate security leadership and AI governance challenges.
Related Articles
The Evolving CISO: Why Security Leadership is Moving to the Boardroom in 2026
The Executive's Guide to Managing Fourth-Party Risk: When Your Vendors' Vendors Become Your Problem
PCI DSS 4.0: Mastering Compliance Post-March 2025
Ready to Put These Insights Into Action?
Whether you need AI governance, security leadership, or compliance guidance—let's discuss how to apply these strategies to your organization.