EO 14412: the post-quantum cryptography executive order

Executive Order 14412 gave the FAR Council 180 days to propose a contractor rule. Counted from the signing on June 22, 2026, that’s eight days left in June, 123 across July through October, 30 in November, and 19 in December: December 19, 2026. The agency dates in the post-quantum cryptography executive order arrive later, at the end of 2030 and 2031, and carry more work: moving high value assets (HVAs) and high impact systems to post-quantum key establishment first, then to post-quantum signatures. Nothing in the order decides which systems are allowed to talk to each other.

What does the post-quantum cryptography executive order (EO 14412) require?

EO 14412 requires OMB guidance that moves federal high value assets (HVAs) and high impact systems to post-quantum key establishment by December 31, 2030 and post-quantum digital signatures by December 31, 2031. It also orders a FAR rule for federal contractors, CISA minimum elements for a cryptographic bill of materials, and faster NIST module validation.

EO 14412, “Securing the Nation Against Advanced Cryptographic Attacks,” is Federal Register document 2026-12909, published June 25, 2026 at 91 FR 38483. It moves federal information systems to NIST-approved FIPS for post-quantum cryptography (PQC), and its section 1 names the threat: adversaries “collecting United States information now, and decrypting it later once large-scale quantum computers are operational.”

It runs on four clocks:

• 30 days (July 22, 2026): section 4(a) has each agency name a PQC migration lead to OMB and the National Cyber Director.
• 90 days: section 4(b) calls for OMB guidance requiring agencies to move HVAs and high impact systems, national security systems excluded, to PQC key establishment by December 31, 2030 and PQC signatures by December 31, 2031, and to submit a plan. OMB issued it two days after signing, as M-26-15.
• 180 days (December 19, 2026): the FAR Council’s proposed contractor rule (section 6(c)), faster validation processes at NIST’s Cryptographic Module Validation Program (section 6(b)), the start of a NIST migration pilot that must finish by December 31, 2027 (section 4(c)), and the first NSA report on national security systems (section 5(c)).
• 270 days (March 19, 2027): CISA’s minimum elements for a cryptographic bill of materials under section 5(d), and a section 6(d) FAR proposal on vulnerability disclosure that covers cryptographic weaknesses.

The order sets no 2035 date; that comes from M-26-15, NIST IR 8547, and, earlier, NSM-10. It has no Zero Trust or segmentation language. Its subject is algorithms.

How does EO 14412 relate to NSM-10, M-23-02, and the Quantum Computing Cybersecurity Preparedness Act?

EO 14412 doesn’t revoke or even name NSM-10, OMB M-23-02, or the Quantum Computing Cybersecurity Preparedness Act (QCCPA, Public Law 117-260), although it tells OMB to write its guidance “consistent with 6 U.S.C. 1526(c),” the QCCPA’s migration section.

The older instruments surface in M-26-15 instead, which says it fulfills OMB’s duty under QCCPA section 4(c) and borrows NSM-10’s definition of a high impact system. It never mentions M-23-02. Status reflects each primary text as of November 8, 2026.

What are the federal post-quantum deadlines from 2026 to 2035?

The federal post-quantum deadlines run from June 2026 to 2035, and the two that carry the most work fall on December 31, 2030 and December 31, 2031. “Due” means a document sets the date and the deliverable doesn’t exist yet.

What does OMB M-26-15 require agencies to do?

Action One of M-26-15 requires a prioritized migration “with the objective of mitigating as much quantum risk as feasible by December 31, 2030.” Action Two required a PQC Migration Plan to OMB and the Office of the National Cyber Director within 120 days, so plans were due October 22, 2026. National security systems aren’t in scope.

The plan runs in five phases: strategy, planning, and discovery (2026 to 2027); pilots and early migration (2027 to 2028); prioritized migration of key establishment (2028 to 2030); signature migration (2031); and full migration of remaining systems (2035). Appendix B lists a funding estimate among the plan’s minimum contents, and the post-quantum lines in the budget planning guide cover it.

Appendix A turns to the network. Agencies must support TLS 1.3 by January 2, 2030, consistent with EO 14306. Devices that terminate TLS or IPsec, from firewalls to API proxies, must support PQC key exchange, and “Ideally, such terminators should be located architecturally as close to the endpoint as feasible to minimize the risk of their exploitation.” The inventory draws on SBOM analysis, code testing, and “network scanners to detect protocols and cipher suites,” all feeding a cryptographic bill of materials (CBOM).

For systems that can’t move, M-26-15 has a single instruction: “Systems incapable of supporting PQC or hybrid cryptography must be identified and given priority for replacement or decommissioning.” Replacement takes procurement cycles; see systems that can’t be upgraded to post-quantum cryptography.

How should agencies prioritize high value assets for post-quantum migration?

M-26-15 makes the first cut for you: high impact systems, HVAs, and other systems with highly sensitive data or particular exposure to a cryptographically relevant quantum computer (CRQC). It singles out PKI-based logical access control and data “expected to remain mission-sensitive in 2030.” Five factors, each from a federal source, help order it:

• Confidentiality lifetime. Harvest now, decrypt later means traffic recorded today can be decrypted once a CRQC exists. NIST IR 8547 says long-term confidentiality needs “warrant the earliest transitions.”
• Trust anchors. Every system that verifies a key inherits its weakness. M-26-15 names PKI-based access control; CISA’s OT paper lists root keys and signing keys.
• Exposure. CISA asks how far a system shares information outside your organization.
• Product availability. A system in one of CISA’s “transitioning” product categories needs a dated vendor roadmap in the plan.
• Reach. CISA asks, “What other systems does the system communicate with?” An HVA reachable from every workstation subnet carries more risk on old cryptography than one reachable from two jump hosts.

Reach is also the factor the Zero Trust program can change before 2030.

What does NIST IR 8547 mean for post-quantum migration planning?

NIST IR 8547, final since October 27, 2026, is the algorithm calendar M-26-15 requires agency plans to align with. Its central sentence: “NIST will deprecate quantum-vulnerable public-key cryptography after 2030 and disallow its use under NIST standards and guidelines after 2035.” That window “does not alter the earlier deadlines that apply to high value assets, high impact systems, and other high-sensitivity federal systems under EO 14412 and OMB M-26-15,” and NIST is plain about how tight those are: “Measured against the 10 to 20 years that previous cryptographic transitions have taken, these deadlines leave little margin.”

The replacements are FIPS 203 (ML-KEM, with parameter sets ML-KEM-512, ML-KEM-768, and ML-KEM-1024), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA). NIST recommends ML-KEM-768 as the default and calls ML-KEM, at this time, “the only approved post-quantum key-establishment scheme based on public-key cryptography.” One key-establishment scheme. Two FIPS signature standards, plus the stateful hash-based LMS and XMSS schemes in SP 800-208. One default.

Hybrid is allowed. NIST says it “will accommodate the use of a hybrid key-establishment mode and dual signatures in FIPS 140 validation when suitably combined with a NIST-approved scheme.” The standards history is covered in post-quantum cryptography vendors by category.

What does CISA recommend for post-quantum cryptography, including OT?

CISA recommends buying only PQC-capable products in categories where they’re widely available and, in a separate paper, prioritizing network segmentation for legacy OT. The buying guidance, “Product Categories for Technologies That Use Post-Quantum Cryptography Standards” (January 23, 2026), answers EO 14306, and its widely available list covers cloud PaaS and IaaS, chat and messaging, web browsers and servers, and endpoint data-at-rest encryption, though most have PQC for key encapsulation only and aren’t “fully quantum resistant.”

The buying rule: “Once a category is listed as having PQC-capable products widely available, organizations should plan acquisitions to procure only PQC-capable products in that category.” Networking hardware sits on the transitioning list, so the rule doesn’t reach it yet, and CISA’s examples for that category include firewalls, which M-26-15 requires to support PQC key exchange when they terminate TLS or IPsec. OT and IoT devices are out of scope, and so are cryptographic discovery and inventory products. OT gets its own paper.

The OT paper, “Post-Quantum Considerations for Operational Technology” (October 2024), is the federal source on containment: “Entities should prioritize network segmentation for legacy OT, end-of-life software, and platforms that require extensive time to apply updates.” M-26-15 never says this. CISA does, for OT. Inventory comes first there too, so CISA’s OT asset inventory guidance and IT/OT segmentation belong in the same plan.

What do federal contractors need to do to comply with the post-quantum cryptography executive order?

Nothing binding yet. As of November 8, 2026, no FAR proposed rule on post-quantum cryptography appears in the Federal Register. EO 14412 section 6(c) directs the FAR Council to propose a rule requiring “covered contractors to comply by December 31, 2030, with NIST’s FIPS, including all applicable FIPS incorporating PQC compliant algorithms.” The order doesn’t define “covered contractor.” A proposed rule isn’t a contract clause; the clause arrives with a final rule. Section 6(d) adds a second proposal, due March 19, 2027, on vulnerability disclosure, “including testing for lack of encryption and the use of non-FIPS approved algorithms.”

M-26-15 already pushes PQC into what agencies buy. Appendix B makes the program office responsible for ensuring “vendor requirements include PQC-readiness and cryptographic agility provisions,” which can put PQC language in a solicitation before any FAR rule is final. Preparation that holds up whatever the rule says, none of it required today:

• A cryptographic inventory and CBOM for the systems that touch the contract (CISA’s CBOM minimum elements are due March 19, 2027); cryptographic discovery and CBOM tools are compared separately.
• A read of current contract clauses and RFP evaluation criteria for FIPS 140 and PQC language.
• Dated PQC roadmaps and CMVP validation status from your own suppliers.
• TLS 1.3 on any service you run for an agency. The agency’s own deadline is January 2, 2030.
• CNSA 2.0 for work on national security systems, required in new acquisitions from January 1, 2027.
• A vulnerability disclosure policy that accepts cryptographic findings.

How does Zero Trust support the federal post-quantum migration?

Zero Trust supports the federal post-quantum migration by isolating the systems that won’t migrate in time. M-26-15 covers the other half of the relationship, in Appendix A, section 7: “PQC is a foundational dependency for advancing a durable zero-trust architecture (ZTA) into an optimal state as defined by the CISA ZTA Maturity Model.” It then assigns PQC work to each pillar, from device attestation to PQC-signed tokens between workloads, because Zero Trust verification is only as strong as its cryptography.

The isolation half is written down in an older document. OMB M-22-09 (January 26, 2022), the federal Zero Trust strategy under EO 14028, describes a target state where “Agency systems are isolated from each other, and the network traffic flowing between and within them is reliably encrypted.” The Federal Register lists no revocation of EO 14028 as of November 8, 2026; EO 14306 amended EO 14144 instead. Isolation and encryption are separate clauses. PQC upgrades the second. M-26-15 never mentions the first.

Some systems won’t be migrated by December 31, 2030. M-26-15 concedes as much: agencies “have already identified legacy systems for which migration would be too difficult or costly.” Until they are replaced, those systems keep quantum-vulnerable cryptography and their current network reach. That exception list is the natural input to the Zero Trust networks pillar: restrict which identities and systems can open sessions to each one, using identity-based microsegmentation or another isolation method from NIST SP 800-207. Segmentation doesn’t change the cryptography; a permitted session can still be recorded for later decryption, and a device that accepts a forged signature still accepts it. It narrows reachability and buys time, nothing more.

The frameworks underneath are in the Zero Trust architecture implementation guide and how six compliance frameworks separate segmentation requirements from recommendations.

Does post-quantum cryptography stop lateral movement?

No. Lateral movement rides permitted paths and valid credentials; a stronger key exchange only makes the permitted session harder to decrypt. M-22-09 assigns lateral movement to isolation, whose goal is “to meaningfully isolate environments, so that an adversary that compromises one application or component cannot easily move laterally within an organization and compromise other distinct environments.”

PQC does protect authentication over time. M-26-15 warns that a CRQC could “take control of or impersonate devices, systems, and people.” The movement itself is covered in the guide to understanding and preventing lateral movement.

What can post-quantum migration not fix on its own?

A label is the first gap. A product marketed as “quantum-safe” gives you nothing to verify until you ask which FIPS 203 parameter set it uses, whether the mode is hybrid, and whether the module has CMVP validation.

Downgrade is the second: a system that supports ML-KEM but still accepts classical-only handshakes keeps negotiating classical key exchange with every peer that hasn’t upgraded, and those sessions stay open to harvest now, decrypt later. M-26-15 names the risk directly: “To avoid downgrade attacks, ensure that devices can be configured to use only acceptable algorithms.”

Coverage is the third. The CISA product categories list leaves out OT and IoT devices, and CISA’s OT paper lists what a CRQC would open up on them, including attackers who “exploit public-key-based Secure Boot protections used to ensure integrity of core system software and firmware.” A device whose firmware check depends on that public-key chain doesn’t migrate until the vendor ships new firmware or hardware. The agency doesn’t set that date. Until then, the containment and exception-register work in the guide on systems that can’t be upgraded to post-quantum cryptography applies.

Before the FAR rule text lands, three lists should exist: your HVA and high impact systems, the cryptography each one runs, and the systems that will still be quantum-vulnerable on December 31, 2030. The third list needs an owner in both the PQC program and the Zero Trust program.

Where does Elisity fit?

Elisity fits two parts of this program: reachability for systems that miss 2030 today, and network-observed evidence for the cryptographic inventory starting in the first half of 2027. It doesn’t migrate cryptography, and it doesn’t encrypt, decrypt, or modify the traffic it permits. Elisity Quantum Posture, planned for the first half of 2027, will classify the assets, internal services, and external services Elisity observes on the network as Quantum Vulnerable, Quantum Ready, Quantum Safe, or Insufficient evidence. A Quantum Safe result will describe the cryptography Elisity observed, not the whole asset. Quantum Posture will read cryptography only in observed network traffic, not inside firmware or code, so it will complement the SBOM analysis and code testing M-26-15 names for the same inventory.

For the exception list, Elisity IdentityGraph™ identifies each asset and what it communicates with, you simulate policy against observed traffic, and the Elisity Dynamic Policy Engine enforces it at supported enforcement points in your existing network infrastructure, anywhere that infrastructure carries the asset’s traffic, from where a device connects to the data center, including traffic bound for the cloud applications it talks to. Traffic that never crosses a supported enforcement point, such as traffic that stays on an unsupported switch or passes directly between two clients of one wireless access point, is outside that control. See Zero Trust and PQC in one program.

Frequently asked questions about the post-quantum executive order

Is the post-quantum executive order EO 14412, EO 14409, or EO 14413?

The post-quantum cryptography executive order is EO 14412, “Securing the Nation Against Advanced Cryptographic Attacks,” signed June 22, 2026 (Federal Register document 2026-12909). EO 14413, signed the same day, is a different order, “Ushering in the Next Frontier of Quantum Innovation” (2026-12910). EO 14409 (June 2, 2026) covers artificial intelligence, not cryptography.

Is the FAR post-quantum rule final?

No. EO 14412 section 6(c) gives the FAR Council until December 19, 2026 to publish a proposed rule, and no such rule appeared in the Federal Register as of November 8, 2026. The rule would set a December 31, 2030 compliance date for covered contractors.

Does network segmentation satisfy a federal PQC mandate?

No. EO 14412, OMB M-26-15, and NIST IR 8547 set dates for post-quantum key establishment and signatures, and segmentation changes neither. M-26-15 sends systems that can’t support PQC to replacement or decommissioning. Segmentation limits which systems can reach a vulnerable one while it waits.

Does EO 14412 apply to national security systems?

Not its agency deadlines. Section 4(b) excludes national security systems from the OMB guidance, and M-26-15 doesn’t apply to them. National security systems follow CNSA 2.0 under CNSSP 15, starting with new acquisitions from January 1, 2027 and mandated CNSA 2.0 algorithms by December 31, 2031.

Does the post-quantum executive order apply to hospitals and other critical infrastructure?

EO 14412 sets no deadline for private critical infrastructure operators. Section 5(a) directs Sector Risk Management Agencies to work with CISA to help owners and operators develop PQC migration plans; for hospitals that agency is HHS. No HHS post-quantum guidance was found as of November 8, 2026. Hospitals can start with these PQC readiness steps for hospitals.

What kinds of vendors does a federal post-quantum program need?

A federal post-quantum program usually needs several: discovery and CBOM platforms, PQC libraries and HSMs, PKI, gateways for systems that can’t change, and compensating controls that limit reachability. Elisity provides compensating access control for systems that can’t migrate on schedule, and Elisity Quantum Posture, planned for the first half of 2027, will add network-observed cryptographic evidence to the inventory. Neither meets a PQC deadline on its own. The full comparison is in post-quantum cryptography vendors by category.

What does harvest now, decrypt later mean in EO 14412?

Harvest now, decrypt later is the risk EO 14412 section 1 describes as adversaries “collecting United States information now, and decrypting it later once large-scale quantum computers are operational.” Key establishment, which protects confidentiality, carries the earlier federal date of December 31, 2030.

Sources

• Executive Order 14412, “Securing the Nation Against Advanced Cryptographic Attacks,” June 22, 2026, 91 FR 38483, document 2026-12909. Federal Register
• Executive Order 14413, “Ushering in the Next Frontier of Quantum Innovation,” June 22, 2026, document 2026-12910. Federal Register
• Executive Order 14409, “Promoting Advanced Artificial Intelligence Innovation and Security,” June 2, 2026, document 2026-11415. Federal Register
• OMB M-26-15, “Execution of the Migration to Post-Quantum Cryptography,” June 24, 2026. whitehouse.gov (PDF)
• NIST IR 8547, “Transition to Post-Quantum Cryptography Standards,” final, October 27, 2026. NIST CSRC
• CISA, “Product Categories for Technologies That Use Post-Quantum Cryptography Standards,” January 23, 2026. cisa.gov
• CISA, “Post-Quantum Considerations for Operational Technology,” October 2024. cisa.gov
• NSA, “The Commercial National Security Algorithm Suite 2.0 and Quantum Computing FAQ,” version 2.1, December 2024. defense.gov (PDF)
• National Security Memorandum 10, May 4, 2022. White House archive
• OMB M-23-02, “Migrating to Post-Quantum Cryptography,” November 18, 2022. whitehouse.gov (PDF)
• Quantum Computing Cybersecurity Preparedness Act, Public Law 117-260, December 21, 2022. govinfo.gov
• Executive Order 14306, June 6, 2025, document 2025-10804. Federal Register
• Executive Order 14028, “Improving the Nation’s Cybersecurity,” May 12, 2021, document 2021-10460. Federal Register
• OMB M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles,” January 26, 2022. whitehouse.gov (PDF)
• NIST SP 800-207, “Zero Trust Architecture,” August 2020. NIST CSRC
• CISA, Zero Trust Maturity Model, Version 2.0. cisa.gov
• OMB, Memoranda index (checked November 8, 2026). whitehouse.gov