The most common mistake in quantum security is thinking the deadline is the day a quantum computer breaks RSA. It isn’t. For any data that must stay confidential past roughly 2030, the deadline already passed because that data is being intercepted and stored today, by adversaries who are content to wait years to decrypt it. The quantum threat is not a future physics event. It is a data-retention problem that is live right now.
The Deadline Isn’t When Quantum Arrives
A cryptographically relevant quantum computer, one powerful enough to break the RSA and elliptic-curve encryption that protects most of the internet does not exist yet. The most credible projections place its arrival somewhere between 2030 and 2035, with real uncertainty on either side. That distance is exactly why so many organizations file quantum under “later.”
Filing it under later is the error. An adversary does not need a working quantum computer today to compromise your encrypted data today. They need a hard drive and patience. Capture the ciphertext now, store it cheaply, and decrypt it when the math becomes possible. The technique has a name – harvest now, decrypt later and well-resourced nation-state actors are already doing it against intercepted traffic, encrypted email, file transfers, and stored archives.
The deadline already passed for any data that needed to stay confidential for a decade. Harvest-now-decrypt-later requires no quantum capability at the moment of collection, only patience the adversary already has.
Propelex Security Intelligence
This reframes the entire problem. The question is not “when will quantum break my encryption.” It is “how long does my data need to stay secret, and will a quantum computer exist before that clock runs out.” For a great deal of enterprise data: patient records, financial histories, trade secrets, government and legal material, long-lived credentials, the answer is that the data outlives the timeline. That data is exposed now, not in some distant future.
Mosca’s Theorem: The Only Math That Matters
You do not need to model quantum hardware to know whether you have a problem. You need one simple inequality, formulated by cryptographer Michele Mosca, that turns quantum risk from a physics debate into an arithmetic one.
The logic is unforgiving. If your data must remain confidential for 10 years (X), and migrating your cryptography will take 10 years (Y), then the total is 20 years. If a capable quantum computer arrives in less than that say, 8 years (Z), then data you encrypt today will be exposed before you finish protecting it. You are already late, and no amount of urgency later closes a gap that opened today.
Run the numbers with the current best estimates and most organizations fail the test. A 10-plus-year migration timeline, data with confidentiality requirements stretching into the 2030s, and a quantum arrival estimate inside that same window means X plus Y already exceeds Z for a meaningful slice of enterprise data. The theorem does not tell you to panic. It tells you which data can no longer afford to wait.
Separating Real Risk From Vendor Urgency
The quantum conversation has a hype problem, and it cuts both ways. Some vendors sell it as an extinction-level emergency requiring you to rip out and replace everything immediately. Some organizations, tired of the noise, dismiss it as a decade-away abstraction. Both are wrong, and the honest position sits between them.
Here is what is genuinely urgent: identifying the data whose shelf-life exceeds the quantum timeline, and beginning to protect it. Here is what is not urgent, and where much of the sales pressure lives: replacing cryptography on data that will be worthless by the time a quantum computer exists. A session token that expires in an hour does not need post-quantum protection. A sealed record that must stay confidential until 2045 does. Treating those two the same, in either direction wastes money or courts a breach.
You do not need to panic-buy quantum cryptography. You need to know which of your data is already being harvested to be decrypted later and protect that first. Everything else follows a schedule, not an alarm.
Propelex Security Intelligence
This is where a vendor-neutral view earns its keep. A company selling a specific quantum product has an incentive to make every byte feel urgent. An independent assessment starts from your data, your retention requirements, and your actual risk and often concludes that the right first move is inventory and prioritization, not procurement. The standards themselves are settled: NIST has finalized the core post-quantum algorithms, FIPS 203, 204, and 205, with a fourth for constrained environments. The technology question is largely answered. The open question is sequencing, and sequencing is a strategy problem, not a shopping problem.
Where Quantum-Vulnerable Crypto Actually Hides
Most organizations underestimate their exposure because they think of encryption as one thing they can point to. In reality, quantum-vulnerable cryptography is woven through the entire stack, often in places nobody owns.
- TLS everywhere. Every HTTPS session, API call, and encrypted connection uses key exchange that a quantum computer breaks. Harvested TLS traffic is the canonical harvest-now-decrypt-later target.
- Code signing. The signatures that verify your software is authentic rely on the same math. A future quantum forge of a signing key undermines software supply-chain trust retroactively.
- VPNs and PKI. The certificate authorities and VPN tunnels holding your network together are built on RSA and elliptic-curve cryptography throughout.
- Long-term encrypted archives. Backups and data lakes encrypted for decades of retention are the highest-value harvest target, because their whole purpose is to stay readable and confidential for a very long time.
- Embedded, OT, and IoT devices. Hardware with 10-to-20-year field lifespans and cryptography baked into firmware is the hardest to migrate and the easiest to forget.
- Your third parties. Every vendor in your data path has the same problem. Their harvested data is often your data, and their migration timeline is now part of your risk.
You cannot migrate what you cannot find, and only about 38% of Fortune 500 firms had completed even a partial cryptographic inventory by early 2026. A crypto inventory, what algorithms you use, where, protecting what data, with what retention requirement is the single prerequisite for every other decision. Without it, both the panic-buy and the do-nothing camps are guessing.
The No-Panic Migration Roadmap
A quantum migration spanning 2026 to 2035 is a multi-year commitment, but it does not have to be an emergency or a budget shock. Spread across the hardware and software refreshes you were already going to make, it becomes a planned program rather than a scramble. Five steps, in order.
- Build a cryptographic inventory. Map what cryptography you use, where it lives, what data it protects, and how long that data must stay confidential. This is the foundation and the most commonly skipped step.
- Classify by data shelf-life, not by system. Apply Mosca’s inequality. Rank your data by how far its confidentiality requirement extends past the quantum timeline. The longest-lived, most sensitive data is your first migration target, everything else is scheduled behind it.
- Build crypto-agility into your standards now. The goal is architecture that lets you swap algorithms without re-engineering the whole system. Even before you migrate a single service, requiring crypto-agility in new development stops you from digging the hole deeper.
- Deploy hybrid post-quantum TLS on public-facing infrastructure first. Hybrid key exchange — classical plus post-quantum together is already deployed at scale by the largest providers. It is the highest-impact early move, because it directly shuts the harvest-now-decrypt-later window on traffic in transit.
- Put quantum-safe requirements into procurement. The cheapest migration step you will ever take is a clause requiring post-quantum readiness in your next hardware, software, and vendor contracts. It costs nothing today and saves an emergency replacement later.
The Bigger Picture
Quantum readiness is not, at its core, a cryptography project. It is a data-retention decision that happens to involve cryptography which makes it a board-level question, not just a technical one. The board can answer the question that actually drives everything: how long does our most sensitive data need to stay secret, and are we comfortable that it is being harvested today against that horizon.
Framed that way, the Risk, Value, and Cost balance is clear. The risk is long-lived data harvested now and decrypted later, entirely outside your ability to detect it. The cost is a multi-year migration, which is far cheaper absorbed into planned refresh cycles than executed as a post-breakthrough emergency. The value is doing it in the right order, protecting what genuinely outlives the timeline first, and not wasting a dollar hardening data that will be worthless before quantum arrives.
The organizations that win at quantum readiness are not the ones that spend first. They are the ones that inventory first, classify by shelf-life, and protect their longest-lived data before the harvest that has already started pays off.
Propelex Security Intelligence
A quantum computer capable of breaking today’s encryption may be five years away or fifteen. That uncertainty is not a reason to wait, it is the entire argument for starting. The data being harvested today does not care when the decryption happens. It only cares whether you protected it before it was collected. For a growing share of enterprise data, that answer is being written right now.
Propelex helps organizations cut through the quantum hype with a vendor-neutral readiness assessment, building your cryptographic inventory, classifying data by shelf-life against the quantum timeline, and sequencing a no-panic migration that protects your longest-lived data first while keeping risk, value, and cost in balance. Fortune 50-experienced consultants, no product to sell you.
