GAO Quantum Computing Report: How to Close the Post-Quantum Cryptography Readiness Gap

The GAO quantum computing report, published October 6, 2026, delivers a clear message: no federal agency has fully prepared for the day quantum computers can break today’s encryption. Of the 24 agencies GAO reviewed, none have fully completed the three basic steps the Office of Management and Budget (OMB) asked for: inventory vulnerable cryptography, estimate the cost to migrate, and test post-quantum cryptography (PQC).

Why the lack of progress? The gap GAO describes is not from a lack of urgency. It comes from a lack of visibility into where vulnerable cryptography is in use, a lack of crypto-agility, and a migration path that doesn’t force a network rebuild. Quantum XChange and its Cryptographic Management Platform, Phio TX, are built to address those three problems at the network layer, without downtime.

What did the GAO quantum computing report find?

GAO evaluated the 24 Chief Financial Officers (CFO) Act agencies against three preparatory practices drawn from OMB guidance. The results, from GAO-27-108740:

• Inventory of vulnerable cryptography: Only one of 24 agencies fully addressed all applicable activities. One agency had no inventory at all, and most inventories missed high-impact systems or high-value assets.
• Funding to migrate: None of the 24 fully identified the funding needed. 21 had partial assessments and acknowledged the data wasn’t fully accurate. Three had none.
• Testing PQC: Only one agency fully addressed one of the two testing activities, and it still did not test PQC in its own environment. The other 23 addressed neither.

GAO made 89 recommendations in its sensitive September 2025 report. Twelve agencies agreed, two partially agreed, seven neither agreed nor disagreed, and one disagreed with three of its four recommendations. GAO maintains that all of them are warranted.

One caveat worth stating: GAO’s audit ran from February 2024 to September 2025, and the public version was released after a year of work with the agencies. Some agency positions may have moved since. Regardless, the structural problems GAO identified are still the right ones to plan around.

Why does the gap matter now? Harvest Now, Decrypt Later

GAO notes that most experts believe a cryptographically relevant quantum computer (CRQC) will eventually be built, possibly as soon as 2029 though estimates vary. That uncertainty is exactly why the timeline is a poor reason to wait. GAO describes the Harvest Now, Decrypt Later threat in plain terms: adversaries can copy encrypted data today and decrypt it once a CRQC exists. The report lists how that collection can impact operations:

• Rerouting traffic by exploiting Border Gateway Protocol vulnerabilities
• Compromising the supply chain of network devices
• Eavesdropping on wired or wireless connections, including subsea cable

Every one of these operations risks is a data-in-motion problem. GAO also points out that deriving a private key from a public key with a CRQC is not an event the victim’s security tools can detect. If your sensitive data needs to stay confidential into the mid-2030s, it is already inside the window of risk. That’s why OMB’s own guidance asks agencies to prioritize systems holding data that will still be mission-sensitive in 2035.

Why are agencies stuck?

GAO traced the incomplete progress to a handful of root causes:

1. Lack of cryptography expertise. 18 agencies reported this deficiency, and none had a plan to fill the gap.
2. No documented processes. 23 of 24 had no documented inventory maintenance process, and only one documented how to assess migration funding.
3. Few automated tools. 19 agencies did not use automated discovery tools. 15 said it was too early or that they were waiting on CISA.
4. No vendor cost data. 11 agencies said they couldn’t estimate costs because no vendors had PQC products to price.
5. “Too early to test.” 16 agencies said vendors were still early in adopting the new algorithms. GAO counters this claim by saying that open-source tools have been available for at least four years, and testing was practical well before commercial products arrived.

Large enterprises in financial services, healthcare, telecom, and critical infrastructure will recognize this list. The report may be about federal agencies, but the obstacles (hidden cryptography, scarce expertise, unclear cost, fear of disrupting production) are not unique to the government.

How can Quantum XChange and Phio TX help bridge the gap?

Phio TX is a Cryptographic Management Platform that protects data-in-motion and helps organizations become crypto-agile without taking the network down. It deploys as a quantum secure layer on existing network infrastructure, with no downtime, no hardware replacement, and no impact on network performance. It is FIPS 140-3 and FIPS 203 validated.

Here is how that maps to the gaps GAO identified.

Gap 1: Limited visibility into cryptography

Phio TX gives security teams centralized visibility and configuration management through a single management console. Visibility is the first thing GAO found missing. A centralized view of system health and key delivery across your network turns an unmanaged sprawl into something you can govern and report on.

Gap 2: No safe way to test PQC

GAO found that agencies have not tested PQC in their environments. Phio TX separates key generation and delivery from the data plane. That architecture lets teams pilot new PQC algorithms as an overlay while production stays stable. Testing becomes a controlled step, not a risky one.

Gap 3: Cost and disruption uncertainty

Agencies told GAO they couldn’t estimate migration costs without commercially available PQC products. A FIPS 203 validated platform that adds a quantum secure layer to existing infrastructure changes the math. There is no rip-and-replace project to price, and Phio TX deploys in days rather than months. That gives finance and program teams a concrete, phased starting point instead of a placeholder.

Gap 4: Scarce expertise

With Phio TX, an algorithm change is as simple as a few clicks from the Centralized Management Console (CMC). There is no need to schedule a maintenance window or touch every endpoint or application. That means fewer specialists spread across fewer, simpler changes, and no emergency application rewrites when standards shift.

Gap 5: Systems that can’t be upgraded

GAO emphasizes identifying legacy systems that cannot support PQC. Many of those can’t be swapped out quickly. Phio TX protects the network path in which the data travels, rather than waiting on each legacy system, which helps organizations reduce Harvest Now, Decrypt Later exposure while longer-term replacement plans catch up.

Built for what comes next

Algorithms will keep changing – NIST has already changed the PQC landscape more than once. NIST continues to evaluate additional algorithms beyond its initial standards, and early implementations may need updates as cryptanalysis advances. Phio TX supports hybrid classical and post-quantum operation during migration and lets teams swap algorithms as standards evolve. The goal is to be ready for the next change and avoid a recurring emergency.

What Phio TX does not replace

Honest scoping builds trust. Phio TX is not a substitute for an enterprise-wide cryptographic discovery effort across every application and endpoint, and it doesn’t replace the documented inventory, funding, and testing processes GAO calls for. It protects and manages data-in-motion, and it gives you a platform that works alongside those programs. The two efforts reinforce each other: discovery tells you where the risk is, and a crypto-agile network layer lets you act on it without waiting for a multi-year rebuild.

Where should you start?

1. Name the networks that house your priority data. Start with systems and traffic that must stay confidential past 2035.
2. Map your data-in-motion paths. Include carrier links, data center interconnects, and remote sites, since those are where GAO’s harvesting examples play out.
3. Stand up a PQC test plan. Use the pilot approach GAO recommends, with a defined environment and owner.
4. Choose crypto-agility over a single-algorithm bet. Assume you will change algorithms more than once.
5. Talk to a team that has done it. Request a Phio TX demo, download The CISO and CIO Guide to PQC, or read The Harsh New Reality for the architecture behind it.

Frequently asked questions

What does the GAO quantum computing report say about federal readiness?

GAO found that none of 24 reviewed agencies fully addressed the three OMB-based preparatory practices: building a prioritized inventory of vulnerable cryptography, identifying migration funding, and testing PQC. Only one agency fully completed all applicable inventory activities.

What is Harvest Now, Decrypt Later?

Harvest Now, Decrypt Later is a strategy in which adversaries collect encrypted data today and store it until a cryptographically relevant quantum computer can decrypt it. Data in transit is a primary target.

What is a cryptographically relevant quantum computer (CRQC)?

A CRQC is a quantum computer large and capable enough to break certain public-key cryptography, such as RSA, using methods like Shor’s algorithm. None exists today, and estimates for when one will exist vary widely.

What is crypto-agility, and why does it matter?

Crypto-agility is the ability to change cryptographic algorithms without rewriting applications or taking systems offline. It matters because post-quantum standards are still evolving, and organizations should expect more than one round of updates.

Does Phio TX meet federal validation requirements?

Phio TX is FIPS 140-3 and FIPS 203 validated. FIPS 203 is the NIST standard for the module-lattice-based key-encapsulation mechanism (ML-KEM).

Does Phio TX require replacing existing network equipment?

No. Phio TX deploys as a quantum secure layer on existing network infrastructure, with no downtime, no hardware replacement, and no impact on network performance.

Sources

• U.S. Government Accountability Office, Quantum Computing: Federal Actions Needed to Prepare for Emerging Cyber Threat, GAO-27-108740, October 6, 2026
• National Institute of Standards and Technology, FIPS 203