- Federal agenciesCreates coordinated federal standards and a migration plan that could reduce the long‑term risk of successful quantum‑e…
- Potential benefitMay accelerate adoption of post‑quantum cryptographic products and services, potentially expanding commercial demand an…
- Potential benefitProvides clearer cost and resource estimates (via mandated surveys and verification), which could enable more accurate…
The National Quantum Cybersecurity Migration Strategy Act of 2025.
Read twice and referred to the Committee on Homeland Security and Governmental Affairs.
This bill requires the Subcommittee on the Economic and Security Implications of Quantum Information Science, in coordination with NIST and consultation with the Quantum Economic Development Consortium, to develop a National Quantum Cybersecurity Migration Strategy within 180 days that defines a “cryptographically relevant quantum computer,” recommends standards for identifying such machines, assesses agency-specific urgency for migrating to post-quantum cryptography (PQC), and establishes performance measures for four migration stages. The bill directs the Subcommittee to stand up a post‑quantum pilot program requiring each sector risk management agency to upgrade at least one high-impact federal system to PQC by January 1, 2027.
Urgency and timeline: liberals want strong, well‑resourced action; centrists and conservatives worry timelines (e.g., 2027 pilot) may be tight or require funding.
Relative to its intended legislative type, this bill functions as a well-scoped study and reporting mandate with defined deliverables, timelines, and oversight mechanisms, supplemented by an operational pilot requirement and cost-survey tasks.
This bill requires the Subcommittee on the Economic and Security Implications of Quantum Information Science, in coordination with NIST and consultation with the Quantum Economic Development Consortium, to develop a National Quantum Cybersecurity Migration Strategy within 180 days that defines a “cryptographically relevant quantum computer,” recommends standards for identifying such machines, assesses agency-specific urgency for migrating to post-quantum cryptography (PQC), and establishes performance measures for four migration stages.
The bill directs the Subcommittee to stand up a post‑quantum pilot program requiring each sector risk management agency to upgrade at least one high-impact federal system to PQC by January 1, 2027.
The Administrator of the Office of Electronic Government must survey agency cost estimates for migration, verify their realism, identify needed funding/resources, and advise on encouraging private-sector adoption.
On content alone, the bill is a focused, technical statute addressing a recognized national cybersecurity risk with staged implementation, clear agency roles, and oversight mechanisms—factors that historically make passage more likely. Lack of new funding authorization and the need for agencies to absorb migration costs are the primary risks that could slow adoption or prompt amendments, but these issues are commonly resolved through appropriations vehicles or committee negotiation.
Relative to its intended legislative type, this bill functions as a well-scoped study and reporting mandate with defined deliverables, timelines, and oversight mechanisms, supplemented by an operational pilot requirement and cost-survey tasks.
Urgency and timeline: liberals want strong, well‑resourced action; centrists and conservatives worry timelines (e.g., 2027 pilot) may be tight or require funding.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- Federal agenciesImposes additional regulatory and administrative burdens on federal agencies (planning, surveys, pilot upgrades, report…
- Potential burdenMigration costs for agencies (software/hardware upgrades, testing, personnel training, potential system redesign) could…
- Potential burdenThe January 1, 2027 pilot deadline may be tight for some agencies, risking rushed implementations, interoperability pro…
Why the argument around this bill splits.
Urgency and timeline: liberals want strong, well‑resourced action; centrists and conservatives worry timelines (e.g., 2027 pilot) may be tight or require funding.
A mainstream liberal would likely view this bill favorably as a proactive federal effort to protect privacy, civil servants’ data, critical infrastructure, and public services against emerging quantum threats.
They would appreciate federal leadership, standardized definitions and timelines, and the requirement for pilot upgrades and GAO oversight to ensure accountability.
They would also expect the bill to be coupled with sufficient funding and workforce investment to carry out a secure migration.
A centrist would generally support the bill as a sensible, targeted federal response to a credible technological risk, while stressing the need for realistic cost estimates, measurable milestones, and careful implementation.
They would welcome the staged performance measures, the pilot requirement, and GAO oversight as pragmatic mechanisms to manage risk and limit waste.
Their main concern would be ensuring the bill does not create unfunded mandates or unrealistic deadlines, and that OMB, OEG, and agencies coordinate tightly to avoid duplication or unnecessary spending.
A mainstream conservative would recognize the national-security rationale for preparing federal systems against quantum threats but would be wary of new federal mandates, bureaucratic expansion, and unfunded requirements.
They are likely to support targeted, defense-related measures but question whether the bill creates further federal micromanagement of agencies’ IT decisions and whether it commits funds.
Conservatives would also prefer market-driven adoption and private-sector leadership with incentives rather than federal prescriptions.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, the bill is a focused, technical statute addressing a recognized national cybersecurity risk with staged implementation, clear agency roles, and oversight mechanisms—factors that historically make passage more likely. Lack of new funding authorization and the need for agencies to absorb migration costs are the primary risks that could slow adoption or prompt amendments, but these issues are commonly resolved through appropriations vehicles or committee negotiation.
- No cost estimate or authorization of appropriations is included; it is unclear whether Congress will pair this bill with funding or expect agencies to reallocate existing resources, which affects willingness to support it.
- Feasibility of the January 1, 2027 deadline for upgrading at least one high-impact system per sector risk management agency depends on current agency readiness and technical constraints not described in the bill.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Urgency and timeline: liberals want strong, well‑resourced action; centrists and conservatives worry timelines (e.g., 2027 pilot) may be ti…
On content alone, the bill is a focused, technical statute addressing a recognized national cybersecurity risk with staged implementation,…
Relative to its intended legislative type, this bill functions as a well-scoped study and reporting mandate with defined deliverables, timelines, and oversight mechanisms, supplemented by an operational pilot requiremen…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.