Counsel for the
frontier of computation
Research

Post-Quantum Migration: Deadlines, ML-KEM, ML-DSA, and Readiness Evidence

Compliance and migration ·

Migration deadlines become useful when connected to particular systems, cryptographic functions, and verifiable commitments. A legal perspective on post-quantum readiness.

Post-quantum migration involves several different clocks: the publication of algorithm standards, transition schedules for particular systems, and commitments made in procurement and commercial agreements. A readiness assessment identifies which clock governs the decision and what evidence establishes progress.

CipherLaw uses PQScope, the firm’s proprietary research tooling, to connect standards and policy with implementation evidence and the underlying research. That work helps identify sources, dependencies, and unresolved questions relevant to migration. The linked article explains the research approach; the authorities cited below support the specific dates and technical distinctions.

Migration timelines and their scope

There is no single deadline that governs every organization and system. The following milestones have different audiences and effects. Sources were checked on November 21, 2026.

August 13, 2024
Algorithm standards
NIST published FIPS 203 for ML-KEM and FIPS 204 for ML-DSA. These establish technical specifications; publication itself does not establish a universal migration deadline.
December 31, 2030 and 2031
Sensitive federal systems
Executive Order 14412, section 4(b), directs OMB guidance requiring agencies to transition high value assets and high impact systems, excluding National Security Systems, to PQC key establishment by December 31, 2030, and digital signatures by December 31, 2031.
After 2030 and after 2035
NIST transition schedule
The final NIST IR 8547, published October 27, 2026, sets deprecation of quantum-vulnerable public-key cryptography after 2030 and disallowance under NIST standards and guidelines after 2035. Earlier deadlines for sensitive federal systems remain applicable.
2028, 2031, and 2035
UK planning targets
NCSC guidance sets indicative targets: discovery and an initial plan by 2028, highest-priority migration and a refined roadmap by 2031, and completion by 2035. Its primary audience includes large organizations, critical infrastructure operators, and organizations with bespoke IT.

For a particular engagement, the legal analysis starts with the organization’s role, system classification, jurisdiction, and contractual commitments. A federal agency direction, an indicative planning target, and a supplier’s promised delivery date can each affect a project, but through different mechanisms.

The distinction is especially important in procurement. Section 6(c) of Executive Order 14412 directs the FAR Council to publish a proposed rule concerning covered contractors and a December 31, 2030 compliance date. That direction alone does not establish that every contractor already has the same operative contractual obligation. Applicability requires examination of implementing rules, their effective dates, and the relevant solicitation or agreement.

What post-quantum readiness covers

ML-KEM and ML-DSA perform different functions. ML-KEM establishes a shared secret that can be used with symmetric cryptography. ML-DSA generates and verifies digital signatures. Support for one does not establish deployment of the other.

This is a practical distinction in available products. CISA’s product-category guidance notes that many categories with widely available PQC capabilities support key establishment without widespread post-quantum signatures and authentication. It also recognizes that a purchased product may continue using conventional algorithms for interoperability.

A readiness statement therefore needs a defined scope:

  • Function and coverage. The assessment identifies which communications, authentication mechanisms, signing operations, and update paths have migrated. A post-quantum connection can coexist with conventional certificate or software-signing dependencies.
  • Version and deployment. An announced capability, a shipping feature, and an enabled production configuration represent different stages. The relevant evidence identifies the product version, configuration, and systems actually covered.
  • Exceptions and dependencies. Legacy peers, certificate infrastructure, embedded components, or unsupported devices may constrain migration. The record should identify those dependencies, their owners, and the intended treatment.

These distinctions give meaning to representations in procurement responses, diligence materials, and security disclosures. A statement can describe a specific capability and its limits without implying that every cryptographic function has migrated.

Supplier commitments and migration dependencies

The GSA Post Quantum Cryptography Buyer’s Guide, sections 6.1 through 6.5, addresses system interdependencies, the period for which data needs protection, vendor expertise, ongoing support, and adaptability. Those considerations provide a practical starting point for contractual analysis.

An agreement can translate a migration objective into obligations that are capable of being assessed:

  • Defined deliverables. Milestones can distinguish a supported software release, integration into a specified environment, and acceptance following testing. The agreement should identify the covered functions and allocate responsibility for configuration and deployment.
  • Evidence of acceptance. Acceptance criteria can specify configuration records, interoperability results, and any required validation evidence. A general assurance of standards alignment leaves substantial uncertainty about the evidence needed to establish performance.
  • Dependencies and change. Responsibility for third-party components, unavailable updates, and changes in standards should be explicit. Notice, remediation, and change-control provisions can address delays without obscuring the original commitment.
  • Continuing support. Maintenance periods, vulnerability response, and upgrade responsibilities matter beyond initial delivery. Commercial terms should account for who bears the cost of necessary changes and what happens when support ends.

The legal contribution is to connect technical milestones to clear allocations of responsibility. That connection helps distinguish work completed, work accepted, and work still dependent on another party.

The record supporting readiness

A defensible account of migration connects the obligation, the implementation, and the evidence. An inventory is useful when it supports decisions about priority and responsibility. Testing is useful when its scope corresponds to the claim being made.

  • The applicable requirement. The record identifies the source, edition, affected systems, milestone, and reason it applies. Guidance, binding requirements, and negotiated commitments should remain distinguishable.
  • The implemented state. Product and version information, configuration evidence, and test results establish the scope of the assessment. The record should make clear which environments and cryptographic functions were examined.
  • The remaining work. Unresolved dependencies, interim measures, responsible parties, and review dates give context to reported progress. Exceptions need enough detail to explain their significance and intended resolution.

For counsel, these records support review of security representations, procurement terms, and transaction disclosures. They also help management understand whether a reported milestone means that a capability is available, has been deployed, or has satisfied agreed acceptance criteria.

CipherLaw’s Post-Quantum Compliance practice addresses the obligations, governance, supplier commitments, and representations surrounding that work. Where migration choices also raise questions about implementation rights or standards contributions, the firm’s Standards and IP Strategy practice provides the related IP analysis.