Post-quantum migration outlook 2027: how fast banks and agencies must move
Federal agencies now have fixed 2030 and 2031 dates for post-quantum cryptography; banks have non-binding international guidance pointing to the same years, and procurement rules will carry the federal dates to vendors.
Where things stand
The algorithms are settled enough to build on. NIST published its first three post-quantum standards on August 13, 2024: FIPS 203 (ML-KEM) for key establishment, and FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for digital signatures [4]. Two more are coming. NIST selected HQC as a backup to ML-KEM in March 2025 and said it planned a draft standard in about a year and a final standard in 2027 [7]. NIST IR 8547, final as of October 2026, says a FIPS specifying HQC is under development and that a signature standard derived from FALCON is being developed as an additional alternative [3] [12].
The deadlines changed more in 2026 than the algorithms did. Until this year the federal anchor was National Security Memorandum 10 of May 4, 2022, which set the goal of mitigating as much quantum risk as feasible by 2035 [6]. Executive Order 14412, signed June 22, 2026, moved the hardest dates forward for the systems that matter most: every high value asset and high impact system must use post-quantum key establishment by December 31, 2030 and post-quantum digital signatures by December 31, 2031 [1]. OMB Memorandum M-26-15, dated June 24, 2026, puts the order into practice, sets the objective of mitigating as much quantum risk as feasible by December 31, 2030, and gave agencies 120 days from its date to send a migration plan to OMB and the Office of the National Cyber Director [2]. The 2035 goal has not gone away; NIST says it remains in place and that the most sensitive systems must now move substantially earlier [3].
NIST's own schedule now sits behind the federal one. IR 8547 says NIST will deprecate quantum-vulnerable public-key cryptography after 2030 and disallow it under NIST standards and guidelines after 2035, and that this window does not alter the earlier deadlines for high value assets, high impact systems and other high-sensitivity federal systems [3]. For signatures this replaces an earlier projection, in SP 800-57 Part 1, that public-key schemes giving 112 bits of security would be disallowed on January 1, 2031 [3].
| Date | What falls due | Who it binds |
|---|---|---|
| December 31, 2027 | NIST completes its own post-quantum migration pilot [1] | NIST |
| January 2, 2030 | Support for TLS 1.3 or a successor version [2] [3] | Federal agencies |
| December 31, 2030 | Post-quantum key establishment for high value assets and high impact systems [1]; covered contractors to comply with NIST FIPS, including post-quantum ones, under a FAR rule the order calls for [1] | Agencies; federal contractors once a final rule exists |
| December 31, 2031 | Post-quantum digital signatures for high value assets and high impact systems [1] | Federal agencies |
| After 2030 / after 2035 | Quantum-vulnerable public-key algorithms deprecated, then disallowed under NIST standards [3] | Anyone who follows NIST standards |
| End of 2030 / 2035 | EU: high-risk use cases migrated; then medium-risk, and low-risk as far as feasible [9] | EU Member States (recommendation) |
What sets the pace
Three forces set the speed, and they act on different organizations. The first is federal law and policy. The Quantum Computing Cybersecurity Preparedness Act, approved December 21, 2022, told OMB to issue migration guidance not later than 1 year after NIST issued post-quantum standards, and requires OMB to report agencies' progress to Congress, starting 1 year after that guidance and continuing until 5 years after the standards were issued [5]. M-26-15 says it fulfills that duty [2]. Its plan has five phases: strategy and discovery in 2026 and 2027, pilots and early migration in 2027 and 2028, prioritized key-establishment migration from 2028 to 2030, signature migration in 2031, and full migration by 2035 [2].
The second force is the threat model. M-26-15 says a cryptographically relevant quantum computer is not yet known to exist but may arrive in the coming decade [2]. Executive Order 14412 names the risk of adversaries collecting United States information now and decrypting it later [1]. That is why both the memorandum and NIST put systems holding data expected to remain mission-sensitive in 2030 at the front of the queue [2] [3], and why the EU roadmap treats a use case as high-risk if a loss of confidentiality after 10 years or more would still cause significant damage [9].
The third force is procurement. The order directs the FAR Council to publish, within 180 days of the order, a proposed rule requiring covered contractors to comply by December 31, 2030 with NIST's FIPS, including those incorporating post-quantum algorithms, and a second proposed rule within 270 days on vulnerability disclosure programs that take reports of cryptographic weaknesses, including use of algorithms that are not FIPS-approved [1]. It also asks NIST to revise its validation processes within 180 days to speed up cryptographic module validations, and CISA, with NIST, to publish minimum elements for a cryptographic bill of materials within 270 days [1]. M-26-15 tells agencies to write post-quantum integration into requirements for the product categories CISA lists, and says CISA and the Department of War, with GSA, will lead migration efforts for FedRAMP-authorized cloud service providers and for cloud services used at more than one agency [2].
Moraph's view
Moraph's view: procurement will move the market faster than the threat or the standards. Once a contract clause names December 31, 2030, every vendor selling to agencies needs post-quantum support in its main product lines well before then, and those same products are what banks buy. We expect vendor roadmaps, not bank supervisors, to set the practical pace for most financial institutions through 2027.
Banks versus agencies
For federal agencies the pace is fixed in writing, with named dates and a plan already due. For banks it is not. Executive Order 14412 does not name the financial sector; it asks Sector Risk Management Agencies, working with CISA, to help critical infrastructure owners and operators develop migration plans, with no deadline attached [1]. M-26-15 and the Preparedness Act cover federal agencies and exclude national security systems [2] [5].
What banks have instead is a growing set of non-binding international guidance that points to the same years. The G7 Cyber Expert Group's January 2026 statement says it does not set guidance or regulatory expectations, but notes that guidance often points to 2035 as an overall target date and that addressing the most critical systems in 2030-32 would limit downside risk [8]. It lays out six phases, from awareness and preparation through discovery and inventory to validation and monitoring [8]. The BIS paper of July 7, 2025 urges the financial system to start the transition today, with awareness and a cryptographic inventory as critical foundations, and says keeping it secure may involve cryptographic agility, defense in depth, hybrid models and phased migration [10]. FS-ISAC's paper of September 25, 2025 calls for a global transition timeline for the sector, with cross-border coordination that does not rely on prescriptive regulation [11].
In Europe the dates are firmer but still aimed at governments. The EU roadmap, version 1.1 dated June 11, 2025, asks every Member State to have taken first steps and set an initial national roadmap by December 31, 2026, to complete the transition for high-risk use cases by December 31, 2030, and to finish medium-risk use cases by December 31, 2035 [9].
Moraph's view
Moraph's view: the gap between the two sectors is one of enforcement, not of dates. A bank that builds its plan to the federal milestones (inventory now, key establishment for its most sensitive systems by 2030, signatures by 2031) will be on the right side of every timeline published so far, including the EU's. Banks with long-lived confidential data, such as wealth, trade finance and customer identity records, carry the same harvest-now risk the federal order describes and have less reason to wait for a rule.
What could change the timeline
Faster: a public demonstration of quantum hardware that shortens credible estimates would pull dates in, and both the G7 group and the EU roadmap say their dates may change as the risk changes [8] [9]. Contract terms are another accelerator; once the FAR rule is final, any bank or vendor that is also a covered federal contractor inherits the 2030 date [1].
Slower: the order is to be carried out subject to the availability of appropriations [1]. The Preparedness Act required OMB's guidance within 1 year of the August 2024 standards, and M-26-15 is dated June 2026 [2] [4] [5]. Standards gaps can also slow work: the HQC standard and the FALCON-based signature standard were still in development as of October 2026 [3], and NIST says it will revise SP 800-131A with more detailed schedules during the transition [3].
Moraph's view
Moraph's view: the most likely slip is in signatures, not key exchange. Hybrid key exchange is already a setting in mainstream protocols, while signatures reach into certificate authorities, hardware security modules, payment cards and firmware signing, where replacement cycles run for years. Expect the 2031 signature date to be the one agencies report trouble meeting first.
What to watch in 2027
Five things will show whether the pace is real. First, the FAR Council's proposed post-quantum rule and the vulnerability disclosure rule, both due under the order within 270 days at the latest [1]. Second, CISA's minimum elements for a cryptographic bill of materials, due within 270 days of the order [1]. Third, OMB's first progress report to Congress under the Preparedness Act, due not later than 1 year after its guidance [5]. Fourth, NIST's draft or final standards for HQC and the FALCON-based signature, and its pilot, which must finish by December 31, 2027 [1] [3] [7]. Fifth, the EU Member States' end-2026 milestone and whether any financial supervisor turns the G7 or EU timelines into an expectation for banks [8] [9].
This outlook explains published policy and guidance as checked on November 16, 2026; it is not legal advice.
What this means for you
- Federal agencies: Treat the plan submitted under M-26-15 as a working document; the memorandum says it will mature over time and expects pilots and early migrations in 2027 and 2028 [2]. Put systems holding data expected to remain mission-sensitive in 2030 among the first [2].
- Banks: Use the federal milestones as a planning benchmark even without a rule: the G7 Cyber Expert Group points to the most critical systems in 2030-32 [8], and BIS urges starting with a cryptographic inventory now [10]. Check whether any federal contracts would bring the FAR rule's 2030 date into scope once it is final [1].
- State and local agencies: Expect federal guidance to reach you through Sector Risk Management Agencies and CISA, which the order asks to help critical infrastructure owners and operators plan [1], and through products already built to federal requirements. Our suggestion: ask vendors now for their post-quantum roadmaps.
- Vendors: Plan for a FAR clause tied to December 31, 2030 [1], agency requirements that reference CISA's product categories [2], and public guidance from CISA and NIST on the minimum elements of a cryptographic bill of materials [1]. Agency systems that cannot support post-quantum or hybrid cryptography are to be given priority for replacement or decommissioning [2].
Moraph predictions
Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.
P1 By Confidence 65% Open
The FAR Council will publish in the Federal Register the proposed rule required by section 6(c) of Executive Order 14412, requiring covered contractors to comply with NIST FIPS including post-quantum algorithms.
How we will check: Search federalregister.gov for a proposed rule from the Federal Acquisition Regulatory Council (DoD, GSA and NASA) that cites Executive Order 14412 and post-quantum cryptography, with a publication date on or before June 30, 2027.
Basis: Section 6(c) of the order sets a 180-day deadline from June 22, 2026 for the proposed rule [1].
P2 By Confidence 70% Open
CISA will publish public guidance on the minimum elements of a cryptographic bill of materials.
How we will check: Look on cisa.gov for a published guidance document setting out minimum elements for a cryptographic bill of materials, dated on or before September 30, 2027.
Basis: Section 5(d) of Executive Order 14412 requires DHS, through CISA and with NIST, to release this guidance within 270 days of June 22, 2026 [1].
P3 By Confidence 75% Open
NIST will publish a draft or final FIPS that specifies the HQC key-encapsulation mechanism.
How we will check: Look on csrc.nist.gov for a draft (initial public draft) or final FIPS specifying HQC, with a release date on or before December 31, 2027.
Basis: NIST said in March 2025 it planned a draft HQC standard in about a year and a final standard in 2027 [7]; IR 8547 said in October 2026 that the FIPS was under development [3].
P4 By Confidence 85% Open
None of the OCC, the Federal Reserve Board or the FDIC will publish a final rule that sets a post-quantum cryptography migration deadline for banks.
How we will check: Search federalregister.gov for final rules from these three agencies published by December 31, 2027 that mention post-quantum cryptography and set a compliance date; the prediction is right if there are none.
Basis: Executive Order 14412 does not name the financial sector and gives Sector Risk Management Agencies a supporting role with no deadline [1]; the G7 Cyber Expert Group says its roadmap sets no regulatory expectations [8].
P5 By Confidence 65% Open
NIST will publish a new draft or final revision of SP 800-131A that adds schedules for the transition to post-quantum cryptography.
How we will check: Look on csrc.nist.gov for a draft or final revision of SP 800-131A released after November 16, 2026 and on or before June 30, 2028 that includes post-quantum transition schedules; the October 2024 Rev. 3 draft does not count.
Basis: NIST IR 8547 says NIST will revise SP 800-131A with more detailed guidelines and schedules during the transition [3]; the latest revision, Rev. 3, was still an initial public draft of October 21, 2024 when checked [13].
Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.
Spotted an error? Tell us and we will check it and correct the piece where needed.