Not the dramatic kind. No zero-days, no ransomware war rooms, no breach notifications landing at 3am. The slow, structural kind, the threats that don't trigger any alarm, don't show up in any dashboard, and won't become visible until it's far too late to act.

And right now, there's one of those threats that the industry is systematically underestimating.

Your encrypted data has already been stolen. The attackers are just waiting for the right moment to read it.

The Heist That Already Happened

Here's what's going on.

Nation-state actors, and we're talking serious, well-funded operations, have been quietly intercepting encrypted network traffic for years. VPN tunnels. TLS sessions. Sensitive documents in transit. IBM's X-Force Threat Intelligence Index 2026 reports that supply chain and third-party breaches quadrupled over the past five years, much of it exfiltrated data that hasn't been exploited yet. They're not trying to crack it today. They don't need to.

The strategy has a name: Harvest Now, Decrypt Later (HNDL). The logic is brutal in its simplicity: collect the ciphertext today, decrypt it once quantum computers are powerful enough to break RSA and elliptic curve encryption. CISA, NSA, and NIST have all issued formal warnings about this exact attack vector.

Gartner now officially predicts that quantum computers will break today's asymmetric cryptography by 2030. That's six years. One product lifecycle. Half a career.

Why This Is Different From Every Other Threat

Every cyberattack I've ever responded to had one thing in common: urgency. Ransomware locks your files now. A phishing attack happens this afternoon. You see it, you fight it, you recover.

HNDL doesn't work like that. There's no alarm. No incident ticket. No moment where you realize something went wrong.

The breach already happened. Silently. Cleanly. Maybe three years ago.

Think about what your organization encrypted and sent over the wire in the last five years:

• Medical records. Legal agreements. M&A communications.
• Government contracts. Long-term financial plans.
• The email where your CEO described exactly how much you'd pay in that acquisition.

That data doesn't expire quickly. Its value compounds over time. And somewhere, it's sitting in a database, waiting.

The Part Nobody Tells You About Hardware

Most of the industry conversation about post-quantum migration focuses on software: swap RSA for ML-KEM, update your TLS libraries, done. That's dangerously incomplete, because Cryptography doesn't only live in code, tt lives in silicon too.

Hardware Security Modules (HSMs) protect the master keys of your PKI, your payment infrastructure, your code signing pipelines. Secure Elements execute cryptographic operations in isolation from the rest of the system, precisely because software can't be trusted for this job.

These devices exist in the hundreds of millions. And almost all of them were designed around RSA or ECC.

Here's the problem: you can't patch hardware with a config file. A Secure Element embedded in a deployed payment terminal or an ePassport doesn't get a software update pushed overnight. An HSM certified under FIPS 140–3 or Common Criteria goes through a re-evaluation process before its algorithm list changes. That process takes months. Sometimes years. The BSI (Germany's federal cybersecurity authority) explicitly flags this hardware lifecycle constraint as one of the central migration challenges in their PQC transition guidance [13].

The full migration chain, from algorithm deprecation to updated standard, to new certified hardware, to procurement, to deployment at scale, easily spans 5 to 7 years for regulated industries, sometimes more. The NSA reached the same conclusion in CNSA 2.0, setting migration deadlines for national security systems that assume this kind of lead time.

That timeline started before most organizations even opened their first post-quantum workstream.

The organizations that understand this are already auditing their hardware estates, mapping which devices support cryptographic agility and which need full replacement. The ones waiting for a crisis will execute this migration under fire, at triple the cost, against a deadline they can't move.

What You Can Actually Do Right Now

NIST published the first post-quantum cryptography standards in 2024. They're finalized. They're production-ready. There is no excuse to wait.

The first step isn't technical. It's a question:

"If an adversary has been collecting our encrypted traffic for the past three years, what could they read in 2030 that would hurt us?"

If the answer is "not much", you're probably fine prioritizing other things.

If the answer made you pause, even for a second, that pause is your risk register entry.

Start with a cryptographic inventory. Map every certificate, every key, every algorithm in production. You'll find shadow PKI infrastructure you didn't know existed. Forgotten VPN endpoints. TLS 1.0 somewhere in a legacy system nobody has touched in four years. That's where the real work begins.

The Clock Is Running

I'm not trying to sell you fear. I'm trying to sell you time, because that's the one resource this threat is designed to consume.

The data is already gone. The quantum computers are being built. The standards are ready.

The only open question is whether your organization will be the one that migrated methodically, or the one that's still running legacy RSA when Q-Day arrives.

Six years sounds like a long time. Ask anyone who's ever run an enterprise PKI migration.