Post-Quantum Cryptography and Enterprise Risk
Quantum computing, cybersecurity, cryptographic modernization, and enterprise risk management.
DEW Diligence, LLC | October 29, 2026 — Revised, November 1, 2026
Post-Quantum Readiness: A Business Risk That Cannot Wait for Quantum Computing
Quantum computers do not need to break today's encryption for organizations to face quantum-related cybersecurity risk. Across the digital economy, businesses rely on cryptography to secure financial transactions, confidential information, identities, communications, software, infrastructure, and trusted relationships between organizations. Much of this protection depends on mathematical assumptions that a quantum computer could eventually undermine. The question for business executives is whether the enterprise can identify, replace, and modernize its cryptographic dependencies before those protections become inadequate.
On October 27, 2026, the National Institute of Standards and Technology (NIST) finalized NIST IR 8547, Transition to Post-Quantum Cryptography Standards, nearly two years after the initial public draft of November 2024. The publication identifies the quantum-vulnerable public-key algorithms in current NIST standards, maps them to quantum-resistant replacements, and establishes the reference timeline for federal agencies, technology providers, and organizations developing their migration strategies. The report supports two federal directives issued in June 2026: Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks (June 22, 2026), and OMB Memorandum M-26-15, Execution of the Migration to Post-Quantum Cryptography (June 24, 2026). Together they accelerated post-quantum migration for federal High Value Assets and high-impact systems and required every civilian agency to submit a PQC migration plan within 120 days — on or about October 22, 2026, five days before NIST's final report. The federal transition has moved from planning to execution.
Financial institutions, healthcare organizations, technology providers, critical infrastructure operators, and enterprises with sensitive long-lived information must consider how quantum-related risk affects their technology investments, security architectures, suppliers, and business continuity strategies.
Post-quantum readiness is becoming an enterprise technology-risk management responsibility.
Understanding the Threat: What Quantum Computing Can and Cannot Break
Quantum computing introduces potential capabilities that differ fundamentally from conventional computing. Certain quantum algorithms could solve mathematical problems that underpin commonly used public-key cryptography more efficiently than known classical methods. A powerful, fault-tolerant quantum computer could threaten widely deployed asymmetric cryptographic schemes, including RSA and elliptic-curve cryptography. These schemes support important security functions, including key establishment, digital signatures, certificate-based authentication, and public-key infrastructure (PKI).
However, not all cryptography is equally exposed. Modern symmetric encryption, including appropriately configured AES, and approved cryptographic hash functions are substantially less vulnerable to known quantum attacks than widely used asymmetric algorithms. In its final transition report, NIST confirms that approved symmetric cryptographic primitives providing at least 128 bits of classical security are believed to satisfy at least its first post-quantum security category and remain approved. Organizations must still select appropriate algorithms, key lengths, implementations, and security controls. That is important because enterprises may not want to approach quantum readiness by indiscriminately replacing every encryption technology. They need to understand which security mechanisms are vulnerable, where they are deployed, what functions they protect, and how those protections can be migrated safely.
Three NIST standards establish a foundation
On August 13, 2024, NIST finalized three principal post-quantum cryptography standards:
Standard | Algorithm | Primary purpose |
FIPS 203 | ML-KEM | Quantum-resistant key establishment |
FIPS 204 | ML-DSA | Quantum-resistant digital signatures |
FIPS 205 | SLH-DSA | Stateless hash-based digital signatures |
ML-KEM helps establish shared secrets that can subsequently support symmetric encryption. ML-DSA and SLH-DSA provide quantum-resistant alternatives for creating and verifying digital signatures. The final IR 8547 recommends ML-KEM-768 as the default parameter set for most key-establishment uses, with other parameter sets permitted where requirements differ. Two further standards are in progress but not final. NIST selected HQC in March 2025 as a code-based backup to ML-KEM, with its FIPS still under development, and NIST states it has no current plans to select additional key-encapsulation mechanisms. FN-DSA (FIPS 206), a compact signature scheme derived from FALCON, also remains in development. Enterprises should plan production deployments around the three finalized standards and treat HQC and FN-DSA as roadmap items, not procurement requirements.
Importantly, adopting a standardized algorithm does not automatically establish that a product is secure, interoperable, operationally ready, or compliant with every applicable federal requirement. Deployment involves cryptographic libraries, protocols, hardware security modules, key management, certificates, application compatibility, and relevant validation requirements. For business leaders, the standardization milestone is important because it shifts the primary challenge from algorithm selection toward implementation and enterprise-wide execution.
Harvest Now, Decrypt Later: Why Data Confidentiality Matters Today
One of the most consequential quantum-related threats does not require a cryptographically relevant quantum computer to exist today. It is known as harvest now, decrypt later (HNDL).
An adversary may collect encrypted communications or information today with the intention of decrypting that information when sufficiently advanced quantum capabilities become available. Consider information that must remain confidential for an extended period like intellectual property, research and development records, acquisition strategies, sensitive financial information, legal communications, classified or government-sensitive information, and certain healthcare or customer records. Some business information becomes irrelevant within months. Other information may retain strategic, regulatory, contractual, or commercial sensitivity for decades. Organizations must therefore evaluate how long information requires protection against how long cryptographic migration may take.
If the required confidentiality lifetime of protected information, combined with the time needed to migrate its cryptographic protections, exceeds the time remaining before a plausible cryptographic threat, earlier action may be necessary.
The arrival date of a cryptographically relevant quantum computer remains uncertain. Confidentiality requirements, system dependencies, procurement schedules, and migration complexity can be estimated and actively managed. This is why post-quantum security planning should begin with business information and its protection requirements, rather than quantum computing forecasts alone. HNDL is also why federal policy prioritizes key establishment ahead of digital signatures. Meaning, protecting the confidentiality of data in transit closes the harvesting window, while signatures protect authenticity at the time of verification.
NIST's 2026 Transition Guidance Changes the Enterprise Planning Conversation
The United States has moved beyond developing post-quantum standards toward implementing risk-based migration priorities. NIST IR 8547 identifies quantum-vulnerable public-key cryptographic algorithms and establishes the broader transition path toward quantum-resistant alternatives.
The most consequential change from the 2024 draft is scope. The draft proposed deprecating only 112-bit-strength parameters, such as RSA-2048, after 2030, leaving stronger parameters such as RSA-3072, P-256, and Ed25519 acceptable until 2035. The final report deprecates all approved quantum-vulnerable public-key algorithms after 2030, at every key size, and disallows them after 2035. Organizations that scoped their migration plans around stronger classical key sizes remaining acceptable until 2035 should revisit that assumption now.
Federal milestones
Date | Requirement | Source |
~October 22, 2026 | Civilian agency PQC migration plans due to OMB and ONCD | OMB M-26-15 |
~March 2027 | CISA, with NIST, publishes minimum elements for a cryptographic bill of materials | EO 14412 |
January 2, 2030 | Federal systems support TLS 1.3 | EO 14306; OMB M-26-15 |
December 31, 2030 | High Value Assets and high-impact systems use post-quantum key establishment | EO 14412 |
December 31, 2030 | Covered federal contractors comply with NIST FIPS, including post-quantum algorithms (proposed FAR rule) | EO 14412 |
After 2030 | All quantum-vulnerable public-key algorithms deprecated under NIST standards | NIST IR 8547 |
December 31, 2031 | High Value Assets and high-impact systems use post-quantum digital signatures | EO 14412 |
2035 | Remaining federal civilian systems migrated; quantum-vulnerable algorithms disallowed under NIST standards | OMB M-26-15; NIST IR 8547 |
These dates should not be confused with predictions about when quantum computers will become capable of breaking cryptography. They are policy and standards transition milestones intended to reduce risk before a cryptographic disruption occurs.
Regulatory applicability is equally important. Federal requirements do not automatically establish identical legal obligations for every private organization. Applicability depends on whether an entity operates a covered federal system, performs covered contractual work, or is subject to another relevant law, regulation, standard, or contractual requirement.
That boundary is moving. EO 14412 directs the Federal Acquisition Regulatory Council to propose, within 180 days of the order (on or about mid-December 2026), a rule requiring covered federal contractors to comply with NIST FIPS, including post-quantum algorithms, by December 31, 2030. Technology providers, managed service providers, and professional services firms that support federal customers should expect post-quantum requirements to appear in solicitations and contract clauses, and should expect their own commercial customers to ask the same questions in due diligence.
Enterprises purchasing or building technology today should consider whether those investments will remain supportable throughout their expected operational lifetimes. A technology acquisition that appears economical today may create substantial remediation costs if its cryptographic architecture cannot adapt.
Cryptographic Debt: The Hidden Cost of Legacy Architecture
Most enterprises do not operate a single cryptographic platform. Cryptographic dependencies exist across application stacks, APIs, databases, cloud environments, identity systems, certificates, network infrastructure, virtual private networks, operational technology, connected devices, software development pipelines, and third-party services. Some dependencies are visible to security teams. Others are embedded in vendor products, legacy applications, hardware, firmware, or cloud-managed services. This creates what can be described as cryptographic debt. This debt being accumulated technology dependencies that make cryptographic change increasingly difficult, costly, and operationally risky.
Organizations may know which applications they own without knowing every cryptographic algorithm those applications use, where cryptographic keys are managed, how certificates are validated, or which third parties control the underlying implementation. That lack of visibility becomes a significant obstacle when migration requires coordinated changes across several technology and service providers.
From asset inventory to cryptographic visibility
Traditional IT asset management and configuration management databases provide valuable information, but they rarely deliver a complete picture of cryptographic dependencies. An effective cryptographic inventory should identify the algorithms, protocols, libraries, keys and their metadata, certificates, supporting hardware, ownership, affected systems, and related business services. OMB M-26-15 makes this inventory the first phase of federal migration and calls for it to be automated and continuously maintained rather than produced once.
A cryptographic bill of materials (CBOM) provides a structured view of the cryptographic components used within a product or application. EO 14412 is the first federal directive to name the CBOM as a defined artifact. It requires CISA, in coordination with NIST, to publish minimum elements for a CBOM within 270 days of the order, on or about March 2027. Organizations need not wait for that guidance to begin. Existing formats such as the CycloneDX CBOM schema provide a practical starting point, provided the data model stays flexible enough to map to the federal minimum elements once published.
Organizations should consider integrating cryptographic discovery into vulnerability management, software composition analysis, architecture governance, configuration management, and vendor assessments. Suppliers should be asked now whether they can deliver a CBOM for the products they sell. NIST's National Cybersecurity Center of Excellence (NCCoE) Migration to Post-Quantum Cryptography Project emphasizes cryptographic visibility, risk management, interoperability, and benchmarking.
Cryptographic Agility: Building an Architecture That Can Adapt
Post-quantum cryptography addresses an important emerging risk, but it does not eliminate the need for future cryptographic modernization. Algorithms may be revised. Implementation vulnerabilities may be discovered. Standards may evolve. Technology providers may discontinue products or change supported security mechanisms. Organizations must therefore evaluate cryptographic agility as a long-term architectural capability.
NIST's Considerations for Achieving Crypto Agility: Strategies and Practices (CSWP 39upd1), finalized December 19, 2025 and updated June 29, 2026 as CSWP 39upd1, examines approaches to replacing and adapting cryptographic mechanisms while maintaining security and operational continuity. It also introduces a crypto-agility maturity model, from unplanned practices to programs integrated with enterprise risk management. In practical enterprise terms, cryptographic agility means reducing unnecessary dependencies on fixed algorithms and designing systems that can support controlled changes to cryptographic components. This can include configurable cryptographic libraries, replaceable key-management capabilities, standardized interfaces, automated certificate lifecycle management, supported protocols, and tested migration procedures.
Hybrid cryptography and interoperability
Some organizations may use hybrid approaches during migration, combining conventional and post-quantum key-establishment mechanisms to maintain appropriate security properties while transitioning. The final IR 8547 clarifies that a hybrid key-establishment scheme can be FIPS 140-validated when at least one component comes from an approved scheme such as ML-KEM, and NIST plans to update SP 800-56C accordingly. For signatures, NIST accommodates dual-signature approaches when one component is approved, while cautioning that their security properties require careful analysis. Hybrid use still introduces operational considerations, including computational overhead, compatibility, implementation correctness, and protocol support.
TLS 1.3 is a modern security protocol and an important foundation for post-quantum migration; federal systems must support it by January 2, 2030. However, using TLS 1.3 alone does not establish post-quantum resistance. The security properties depend on the cryptographic mechanisms actually negotiated and implemented. NIST names TLS an early migration priority, with hybrid TLS guidance planned for the next revision of SP 800-52. Organizations should examine their ability to support quantum-resistant or appropriately designed hybrid key establishment across applications, endpoints, APIs, service providers, and network security infrastructure. The goal is to modernize digital trust without creating unacceptable security, performance, or operational disruption.
Financial Strategy: Post-Quantum Security as a Technology Investment Decision
How should the enterprise allocate limited capital toward a technology risk whose eventual timing is uncertain? The answer may begin with exposure, asset criticality, lifecycle economics, and measurable risk reduction.
Post-quantum readiness may require investments in cryptographic discovery, software upgrades, certificate infrastructure, hardware replacement, supplier coordination, engineering resources, testing, and ongoing governance. Some expenditures can be incorporated into existing modernization initiatives. Others may require dedicated funding because legacy infrastructure cannot be adapted economically. OMB M-26-15 directs agencies to identify systems incapable of supporting PQC or hybrid cryptography and to prioritize them for replacement or decommissioning; private-sector enterprises benefit from the same early identification, because those systems drive the largest and least flexible costs.
From a financial management perspective, organizations could evaluate:
Capital expenditure (CapEx): Hardware replacement, infrastructure modernization, and qualifying technology investments.
Operating expenditure (OpEx): Software services, vendor support, assessment activities, managed capabilities, and ongoing security operations.
Total cost of ownership (TCO): Acquisition, integration, testing, maintenance, migration, training, and eventual retirement costs.
Risk-adjusted prioritization: The relationship between information sensitivity, asset criticality, likelihood and timing uncertainty, business consequences, and migration cost.
Investment timing: Opportunities to avoid duplicate spending by incorporating cryptographic modernization into scheduled technology refreshes and transformation programs.
Accounting classification depends on the nature of each expenditure and applicable accounting policies; not every security modernization cost qualifies for capitalization. The strategic financial objective is to minimize unnecessary migration costs while reducing long-term exposure. Technology investments should also be evaluated against the expected service life of the acquired infrastructure. A connected industrial device expected to remain operational for fifteen years presents a different investment decision from a cloud service that can be upgraded through a managed provider. Under the final IR 8547, any asset purchased today with classical public-key cryptography and a service life beyond 2030 will operate on deprecated algorithms for part of that life. This is where cybersecurity strategy becomes enterprise financial stewardship.
Executive Governance: What Organizations Should Do Now
An effective post-quantum readiness program requires shared accountability across cybersecurity, information technology, enterprise architecture, data governance, procurement, legal, risk management, and business leadership. Organizations can structure the initiative as a phased enterprise modernization program.
Enterprise phase | Aligned M-26-15 phase(s) | Federal window |
1. Governance, visibility, and risk assessment | Strategy and discovery | 2026–2027 |
2. Architecture, supplier readiness, and controlled pilots | Pilots and early migration | 2027–2028 |
3. Risk-prioritized migration and continuous oversight | Prioritized migration; signature migration; full migration | 2028–2035 |
Phase 1: Governance, visibility, and risk assessment
Establish executive sponsorship and assign accountable program ownership; M-26-15 frames this as a leadership responsibility, not one delegated solely to the CISO. Determine which systems and information assets are subject to applicable regulatory, contractual, or policy requirements, including prospective federal contract clauses. Begin automated cryptographic discovery and identify business-critical systems, long-lived confidential information, exposed public-key mechanisms, and relevant third-party dependencies. Integrate those findings into enterprise risk assessments and technology roadmaps.
Phase 2: Architecture, supplier readiness, and controlled pilots
Work with technology providers to understand their support for NIST-standardized post-quantum algorithms, upgrade paths, implementation timelines, validation requirements, CBOM availability, and remaining interoperability limitations. CISA's Product Categories for Technologies That Use Post-Quantum Cryptography Standards (January 23, 2026) separates categories where PQC-capable products are widely available from those still transitioning, and is a useful reference for procurement conversations. Establish cryptographic agility requirements for new technology purchases and major architectural changes. Pilot supported PQC and hybrid implementations in controlled environments. Test performance, certificate and signature sizes, protocol interoperability, hardware capabilities, operational monitoring, rollback procedures, and service continuity. Migration should proceed according to supported implementations and verified operational readiness, not arbitrary deployment targets.
Phase 3: Risk-prioritized migration and continuous oversight
Prioritize systems protecting long-lived sensitive information, critical business operations, or assets subject to accelerated requirements, with key establishment first. Coordinate migration with established cloud, application, infrastructure, identity, PKI, and technology lifecycle programs. Maintain a measurable enterprise roadmap covering planned migrations, remaining dependencies, vendor commitments, exceptions, costs, and operational risks.
A board or executive risk committee should be able to monitor meaningful measures such as cryptographic inventory coverage, critical-system exposure, vendor readiness, completed migration milestones, unresolved exceptions, and forecast migration expenditures. These measures provide greater decision value than reporting the number of cryptographic products purchased.
The Boardroom Question: Is the Enterprise Ready to Change?
Boards do not need a detailed education in quantum physics to oversee post-quantum security. They need evidence that management understands the exposure and has a defensible strategy to address it. Executives should be prepared to explain which critical business services rely on quantum-vulnerable cryptography, how long sensitive information must remain protected, which suppliers and systems present significant migration constraints, and how modernization investments are being prioritized.
They should also be able to identify the consequences of delayed action. For some organizations, the greatest risk may involve the future confidentiality of information. For others, the challenge may be digital signatures, software integrity, legacy operational technology, constrained hardware, or vendor-controlled infrastructure. For federal suppliers, it may be eligibility for future contracts. Those differences are important because they determine the sequence, cost, and urgency of migration.
Security Architecture: A Long-Term Business Obligation
Quantum computing offers important possibilities for scientific research, optimization, materials development, and other computational disciplines. Its future capabilities and commercial adoption timelines remain uncertain. That uncertainty should not be confused with uncertainty about the need to modernize vulnerable cryptographic systems. NIST has established foundational standards and, as of October 2026, a final transition roadmap. Federal policy has set binding migration dates for the most sensitive systems and is extending requirements to contractors. Technical guidance is available to support cryptographic discovery, architecture modernization, and risk-based implementation. Organizations should respond with disciplined due diligence.
Post-quantum readiness is fundamentally about protecting enterprise value, maintaining digital trust, reducing technology debt, and designing security architectures capable of adapting to future cryptographic change. We approach this challenge through the intersection of business strategy, information technology, information security, emerging technology, governance, and enterprise risk management. The most effective investment is not necessarily the earliest deployment of a new cryptographic product. It is a measured strategy that connects technical readiness with information value, operational resilience, vendor accountability, and financial discipline.
The quantum security clock may not have a certain expiration date, but the work required to prepare for cryptographic change is already underway.
Sources and Further Reading
Primary source
Moody, D., Perlner, R., Regenscheid, A., Robinson, A., and Cooper, D. Transition to Post-Quantum Cryptography Standards. National Institute of Standards and Technology, NIST IR 8547, October 27, 2026.
Supporting research and authoritative references
The White House. Executive Order 14412: Securing the Nation Against Advanced Cryptographic Attacks. June 22, 2026.
Office of Management and Budget (OMB). Memorandum M-26-15: Execution of the Migration to Post-Quantum Cryptography. June 24, 2026.
Cybersecurity and Infrastructure Security Agency (CISA). CISA Releases Product Categories to Aid in Post-Quantum Cryptography Adoption. January 23, 2026.
National Institute of Standards and Technology, National Cybersecurity Center of Excellence (NCCoE). Migration to Post-Quantum Cryptography. Applied Cryptography Project.
NIST standards and publications
NIST FIPS 203, Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM), August 2024.
NIST FIPS 204, Module-Lattice-Based Digital Signature Standard (ML-DSA), August 2024.
NIST FIPS 205, Stateless Hash-Based Digital Signature Standard (SLH-DSA), August 2024.
NIST CSWP 39upd1, Considerations for Achieving Crypto Agility: Strategies and Practices, December 2025, updated June 29, 2026.
NIST SP 800-227, Recommendations for Key-Encapsulation Mechanisms, September 2025.
NIST, Post-Quantum Cryptography Standardization Project and Publications. Ongoing standards development and supporting research.
Editorial disclosure: This article represents independent research and strategic commentary by DEW Diligence, LLC. DEW Diligence is not affiliated with or endorsed by NIST, CISA, the Office of Management and Budget, the White House, or other organizations referenced. Technical standards, federal directives, and research findings are attributed to their respective issuing organizations. Interpretations of enterprise risk, cryptographic modernization priorities, financial considerations, and implementation strategies represent DEW Diligence's independent analysis and recommendations, not official guidance from the cited organizations. Federal migration requirements, regulatory obligations, and contractual applicability depend on the organization, information systems, sector, and governing authorities. Migration deadlines should not be interpreted as predictions of when cryptographically relevant quantum computers will become operational. This article does not constitute legal advice or an independent security assessment.
Want more on this topic? Contact us for a consultation, and review our services for fractional & virtual CIO, CISO, and CTO executive consulting.
David E. Williams, CISM, GSTRT, GSLC
Founding Principal, DEW Diligence, LLC
© 2026 DEW Diligence, LLC.
Comments