A 'Q-Day' Readiness Scanner Shipped as a Product This Week. But 60-80% of Your Cryptography Is Undocumented, and a Scan Doesn't Rotate a Single Key

This week, quantum readiness became something you can buy.

On June 8, a quantum security-assessment platform launched as a packaged product: AI-driven readiness scoring, continuous monitoring, and reporting, sold as a subscription. A second quantum threat-intelligence platform shipped the same week. The category is real now. You can put "post-quantum assessment" on a purchase order.

The government side moved in parallel. CISA published its strategy for migrating to automated post-quantum cryptography discovery and inventory tools, mandating that federal civilian agencies deploy scanners to find cryptography vulnerable to a future quantum computer and feed the results into existing dashboards. Even CISA admits the gap in its own plan: it has not been able to confirm the full scope of what these automated tools can actually detect, and it still expects manual inventory work alongside the scanners.

That admission is the whole story.

A scan is a screenshot

A discovery scan tells you what algorithms you're running right now. That's useful. It's also the easy 20% of the problem, and it rotates exactly zero keys.

Here's the part the product launches gloss over. Cryptographic-discovery exercises at financial institutions keep finding the same thing: roughly 60 to 80% of in-scope cryptography is undocumented. Treat that as an industry estimate from practitioners and consultancies rather than a single peer-reviewed number, because that's what it is. But the direction is consistent everywhere people actually look.

Why so much hidden crypto? Because you didn't write most of it. Industry analysis puts 70 to 90% of enterprise software at assembled-from-third-party-components, and every one of those components carries cryptographic defaults nobody on your team chose. Add the keys living inside hardware security modules with vendor-dependent firmware paths, the certificates buried in TLS endpoints, the secrets baked into CI/CD pipelines, and a single enterprise estate can hold hundreds of thousands of cryptographic assets. Most organizations have documented a small slice.

A scanner hands you a list. It does not hand you the ability to act on the list.

The deadlines are real, and they moved up

NIST's IR 8547 roadmap sets two dates. By 2030, the common public-key algorithms protecting most of the internet today (RSA-2048, the P-256 elliptic curve) are deprecated. By 2035, every quantum-vulnerable public-key algorithm is disallowed, at any key length. That schedule was pulled forward from an earlier 2031 target.

A trap worth naming: "we'll just use bigger keys" does not work. Moving from RSA-2048 to RSA-4096 costs an attacker with a quantum computer only about eight times more work, not exponentially more. Any machine that can break one can break the other. Symmetric encryption like AES-128 is fine. The problem is specifically public-key, and the only real fix is migration to the new standardized algorithms.

The reason any of this is urgent today, years before a working quantum computer exists, is harvest-now-decrypt-later. Adversaries are already collecting encrypted traffic and storing it, betting they can decrypt it once the hardware arrives. Anything you need to keep secret for the next 5 to 15 years is already exposed if it crosses the wire protected by today's algorithms.

What "ready" actually looks like

There's a live proof of the real thesis, and it's encouraging rather than scary.

As of early 2026, one major content-delivery network reports that over 60% of human web traffic to its edge now uses hybrid post-quantum key exchange, up from about a third a year earlier. Major browsers turned it on by default. That migration happened quietly, with no enterprise project plan, because the infrastructure supported rotation. The algorithm swapped itself out and almost nobody noticed.

Now the contrast. That 60% is only key exchange. The certificate side, which depends on digital signatures and requires real PKI re-issuance, is stuck near zero. Post-quantum signatures add roughly 15 KB to every handshake, and broad certificate adoption isn't expected until 2027.

Read those two facts together and the lesson is exact. The cryptography that could rotate itself, did. The cryptography that needs a human to touch every endpoint, didn't. The deliverable that matters is not the assessment. It's crypto-agility: infrastructure that can change an algorithm without a migration project for each key.

This is why discovery alone is taking tier-1 banks 9 to 14 months, and full migration across PKI, TLS, HSM fleets, and supplier chains routinely runs 5 to 10 years. The scan is month one of a decade.

For most businesses, this is a vendor problem

If you're a creator, a small business, or an agency, the move is not to go run a discovery tool against your own stack. You don't operate most of the cryptography that protects you. Your providers do.

So your quantum readiness is capped by your least-prepared vendor. The practical action is contractual: require your SaaS, cloud, and managed-service providers to show a documented post-quantum roadmap, and make it a term of the relationship. Managed service providers carry the most exposure here, because they hold privileged access across many clients at once. Cyber-insurance underwriters have started asking the same question, evaluating whether you have a migration roadmap before they price your policy. Inventory is moving from a compliance report to a balance-sheet line.

The emerging unit of work for all of this is the cryptographic bill of materials, an ingredients list of every crypto component in a system, the way an SBOM lists software. Expect to start asking vendors for one.

Where LTFI sits

We build on dedicated infrastructure for every client, not shared tenancy. That includes hardened Debian servers running post-quantum SSH already, automated patching, and DNS and SSL automation through unified fleet management. The point isn't that we ran a scan once. It's that key and certificate rotation is part of how the infrastructure is operated, not a one-time event bolted on later.

That's the difference between a screenshot and an operating capability. A scanner can tell you 60-80% of your cryptography is undocumented. It can't rotate any of it. The managed infrastructure that can swap an algorithm, reissue a certificate, and patch a server fleet without a human visiting every node is the thing that gets you to the 2030 and 2035 deadlines on time.

Quantum readiness shipped as a product this week. The product measures the problem. Solving it is operational work that runs for years, and it needs infrastructure built to rotate.

See what our platform finds: ltfi.ai/report