M-26-15 gave federal civilian agencies until October 22, 2026 to send OMB a post-quantum cryptography migration plan. That date has passed, and the plan is only one of the federal post-quantum cryptography deadlines set this year by Executive Order 14412 and the memo. This post lays out the dated requirements in both, with the section that sets each one, so a CISO or a contracting shop can see what is behind them and what comes next.
What changed in June 2026?
EO 14412, "Securing the Nation Against Advanced Cryptographic Attacks," was signed June 22, 2026 and published at 91 FR 38483. On June 24, the Office of Management and Budget (OMB) issued M-26-15, "Execution of the Migration to Post-Quantum Cryptography," to carry it out. The order's stated concern is adversaries "collecting United States information now, and decrypting it later once large-scale quantum computers are operational."
The earlier goal, from National Security Memorandum 10 in 2022, was to migrate as much quantum risk as feasible by 2035. The new documents pull that forward. Section 4(b) of the order has OMB require each agency to move "all HVAs and high impact systems" to post-quantum cryptography (PQC) for key establishment by December 31, 2030, and for digital signatures by December 31, 2031. M-26-15 goes wider: its Action One tells agencies to migrate cryptography in the systems they own or operate "with the objective of mitigating as much quantum risk as feasible by December 31, 2030."
A high impact system is one where at least one security objective is rated "high" under FIPS 199. High value assets (HVAs) are systems designated under OMB M-19-03 or its successor. The memo adds a third priority group: "any other system with highly-sensitive data" or likely to be particularly vulnerable to quantum attack, including logical access systems built on public key infrastructure (PKI) and data "expected to remain mission-sensitive in 2030." National security systems are excluded from the inventory review in section 4(b)(i); the NSA reports on them separately under section 5(c).
Federal post-quantum cryptography deadlines, date by date
The near-term dates are where the work is. Day counts run from the order's signing on June 22, 2026, or from the memo's date of June 24, 2026.
| Date | What is due | Source |
|---|---|---|
| July 22, 2026 | Each agency names a PQC migration lead and sends contact details to OMB and the National Cyber Director | EO 14412 sec. 4(a), 30 days |
| Late August 2026 | GSA stands up an interagency working group on PQC for identity, credential and access management | M-26-15 sec. 3.C.3, 60 days |
| September 20, 2026 | OMB guidance to agencies (met early by M-26-15 on June 24) | EO 14412 sec. 4(b), 90 days |
| October 22, 2026 | Agency PQC migration plans due to OMB and the Office of the National Cyber Director | M-26-15 sec. 3.B and 3.D, 120 days |
| December 19, 2026 | FAR Council proposed rule on contractor FIPS compliance; NIST revises Cryptographic Module Validation Program processes; NIST starts its own PQC pilot; first NSA report on national security systems | EO 14412 sec. 6(c), 6(b), 4(c), 5(c), 180 days |
| March 19, 2027 | CISA and NIST guidance on minimum elements of a cryptographic bill of materials; FAR Council proposed rule on contractor vulnerability disclosure programs | EO 14412 sec. 5(d), 6(d), 270 days |
| December 31, 2027 | NIST completes its pilot | EO 14412 sec. 4(c) |
| January 2, 2030 | Agencies support TLS 1.3 or a successor version (a date first set by EO 14306) | M-26-15 app. A, sec. 4 |
| December 31, 2030 | HVAs and high impact systems use PQC for key establishment; agencies mitigate as much quantum risk as feasible; covered contractors comply with PQC FIPS (as the FAR rule will set out) | EO 14412 sec. 4(b)(ii), 6(c); M-26-15 sec. 3.A |
| December 31, 2031 | HVAs and high impact systems use PQC for digital signatures | EO 14412 sec. 4(b)(iii) |
| 2035 | Remaining systems migrated, based on risk and commercial availability | M-26-15 sec. 3.D, phase 5 |
M-26-15 also frames the work in phases: planning and discovery in 2026 and 2027, pilots and early migration in 2027 and 2028, key establishment for priority systems from 2028 through 2030, and their digital signatures in 2031. The order notes that implementation is subject to the availability of appropriations, so the funding estimate in each plan matters.
What did the October 22 migration plan have to contain?
Each plan needed a risk-based system prioritization, timelines and milestones for the migration phases and for reaching TLS 1.3, the methods and automated tools used for cryptographic inventory, a plan for a cryptographically agile architecture, a third-party coordination plan, estimated funding and staffing, a risk management approach for the transition period and defined governance roles. Agencies "must align their plans with NIST Internal Report (IR) 8547." NIST published the final version of IR 8547 on October 27, 2026; we cover its deprecation dates in NIST IR 8547 is final.
The memo is explicit that this is not only the CIO's and CISO's job. Appendix B gives a sample allocation of responsibilities that includes the chief financial officer for budget, a PQC technical lead, a security architect and application and system owners. Under it, the "Program Office or Requirement Owner" ensures vendor requirements include PQC readiness and cryptographic agility provisions.
The memo says the plan "should be treated as a dynamic document that will mature over time" but sets no fixed resubmission cycle. OMB, with the National Cyber Director, "will assess agency-wide progress and release further guidance as needed."
Key establishment vs digital signatures: why two dates?
They protect against different risks. Key establishment is how two systems agree on a session key, as in a TLS handshake; NIST's FIPS 203 (ML-KEM) covers it. Digital signatures prove who signed something and that it hasn't changed; FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) cover those. NIST approved all three on August 13, 2024.
Key establishment comes first. Recorded traffic is the collect-now, decrypt-later exposure the order describes, and it grows every day a session runs on classical key exchange. M-26-15 calls TLS 1.3 "foundational for deploying PQC at the network level," so systems that can't negotiate it are a blocker for the 2030 date as well as a requirement of their own.
Where does this leave contractors and cloud providers?
Section 6(c) of the order directs the FAR Council to publish a proposed rule within 180 days, by December 19, 2026, requiring "covered contractors" to comply with NIST's FIPS, "including all applicable FIPS incorporating PQC compliant algorithms," by December 31, 2030. The order does not define covered contractors; the proposed rule is expected to, and comments will follow. As of October 26, 2026, we had not seen it published. Which contracts it reaches will depend on the final rule and its clause, and how it applies to a given contract is for the contracting officer.
Cloud services are already in scope through the agencies. M-26-15 says CISA and the Department of War, in coordination with GSA, "will lead PQC migration efforts for FedRAMP-authorized cloud service providers" and for cloud services used by multiple agencies. It tells agencies to engage their providers "to delineate PQC migration responsibilities within the shared responsibility model," and says they should reference CISA's "Product Categories for Technologies That Use Post-Quantum Cryptography Standards" when buying. For a provider, that responsibility split sits alongside the authorization questions we covered in our FedRAMP 20x explainer.
Next steps for agency teams and vendors
With the plan filed, agency teams can turn to the tasks that make it real:
- Confirm the system list in the plan covers all three priority groups (HVAs, high impact systems and other sensitive systems, including PKI-based access control and data that stays sensitive past 2030), and flag systems that can't support PQC or hybrid cryptography, which M-26-15 wants identified for replacement or decommissioning.
- Stand up automated cryptographic discovery (the memo names software composition analysis, application security testing and network scanners) and record results in a form you can map to the cryptographic bill of materials elements CISA and NIST are due to publish by March 19, 2027.
- Map PQC upgrades onto hardware refresh, cloud migration and software release schedules that already have funding.
- Work with your contracting officer to add PQC readiness and crypto-agility language to new requirements, as Appendix B suggests, rather than waiting for the FAR rule.
Vendors can read the proposed FAR rule when it appears, check that their products support TLS 1.3, and prepare to answer agency inventory questions about the cryptography inside what they deliver. Our cybersecurity team supports agencies with FISMA and NIST compliance work, and our KEV catalog explainer covers another set of federal deadlines that run on asset inventory.
The Bottom Line
The plans went in on October 22, so the work now shifts from writing to inventory, testing and buying. Treat December 19, 2026 as the next checkpoint, when the proposed FAR rule is due and should show how covered contractors are defined. M-26-15 tells agencies to fold PQC upgrades into planned cloud migrations and hardware refreshes "to maximize efficiency and minimize costs," which is the practical place to start.
FAQ
When were federal PQC migration plans due?
OMB M-26-15 required agencies to submit their post-quantum cryptography migration plans to OMB and the Office of the National Cyber Director no later than 120 days from the memo's date of June 24, 2026, which was October 22, 2026. Plans go to [email protected].
What is the deadline for post-quantum cryptography in federal systems?
EO 14412 sets December 31, 2030 for key establishment and December 31, 2031 for digital signatures in high value assets and high impact systems. M-26-15 also sets the objective of mitigating as much quantum risk as feasible across agency systems by December 31, 2030, restates the January 2, 2030 TLS 1.3 deadline from EO 14306, and treats 2035 as the date to complete remaining systems.
Do federal contractors have to use post-quantum cryptography?
Not yet by rule. EO 14412 directs the FAR Council to publish a proposed rule by December 19, 2026 that would require covered contractors to comply with NIST FIPS, including those with PQC algorithms, by December 31, 2030. Until a final rule is in your contract, your obligations are the ones your current contract states. As of October 26, 2026, we had not seen the proposed rule published.
Does EO 14412 apply to national security systems?
Only through a separate track. Section 4(b)(i) excludes national security systems from the agency inventory review, and M-26-15 does not apply to them. Section 5(c) instead has the NSA report to the President on their migration within 180 days and every year after until it is complete.
Which NIST standards are the post-quantum algorithms?
NIST approved three on August 13, 2024: FIPS 203 (ML-KEM) for key establishment, and FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for digital signatures. NIST said it is also developing a FIPS for a signature algorithm derived from FALCON.
Sources
- Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks (June 22, 2026), 91 FR 38483
- OMB, M-26-15, Execution of the Migration to Post-Quantum Cryptography (June 24, 2026)
- NIST, Announcing Approval of Three Federal Information Processing Standards (FIPS) for Post-Quantum Cryptography (August 13, 2024)
- FedScoop, Agencies have four months to finalize quantum-ready migration plans (June 25, 2026)
- The Hacker News, Trump Order Sets 2030 Deadline for Federal Post-Quantum Crypto Migration (June 23, 2026)
How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.
Update history.
- : Noted that NIST published the final NIST IR 8547 on October 27, 2026, replacing the November 2024 draft (source: NIST CSRC, NIST IR 8547 document history).





