Harvest Now, Decrypt Later: Why Credentials Are the First Casualty of Q-Day
Captured ciphertext today becomes plaintext tomorrow. Credentials sit at the top of the target list.
Key points
- Adversaries are capturing encrypted traffic now, betting a future quantum computer will break the public-key cryptography protecting it.
- Credentials are the highest-value target because they retain operational power long after they're captured.
- NIST finalized its first post-quantum standards in August 2024, covering key encapsulation and digital signatures.
- Only 5% of security teams had a defined post-quantum strategy a year after those standards landed.
- Shortening credential lifetimes and inventorying where secrets travel are the highest-use near-term steps.
What is the harvest now, decrypt later threat?
The threat model is uncomfortable but simple. Adversaries, including state-aligned collectors with the patience and storage budget to play a long game, are capturing encrypted traffic today on the assumption that a sufficiently capable quantum computer will eventually break the public-key cryptography protecting it. No machine in operation today can break RSA or elliptic curve cryptography. That isn't the question. The question is what an attacker who hoarded TLS sessions in 2024 can read in 2032 or 2035.
The pattern, sometimes abbreviated HNDL or store-now-decrypt-later, has been flagged by NSA, CISA and NIST for several years. NIST finalized the first batch of post-quantum standards in August 2024: ML-KEM for key encapsulation, ML-DSA for digital signatures, and SLH-DSA as a hash-based signature backup. CISA's quantum-readiness guidance tells operators to inventory cryptography now and prioritize data with long confidentiality requirements. When we first covered HNDL adoption on 12 June, only 5% of security teams had a defined strategy despite those standards being a year old.
Why credentials specifically?
Unlike a leaked memo or an old purchase order, credentials retain operational value long after capture. A static API key, a service account password, a long-lived OAuth refresh token, a SAML signing key: these often outlive the cryptographic envelope that originally protected them in transit. Rotate them rarely, and you've effectively pre-positioned a future intrusion against yourself.
Should you worry about attribution?
Attribution of active HNDL collection is hard and worth flagging with appropriate caveats. Public reporting on bulk-collection programs is largely circumstantial. With medium confidence, several SIGINT-capable services have both the capability and the intent to retain encrypted sessions of intelligence value. Capability isn't the same as a confirmed program, and the analyst community should keep that distinction clean.
What should you do now?
Inventory where credentials traverse the wire and where they sit at rest. Long-lived secrets in CI/CD pipelines, machine identities and root certs deserve priority. Then shorten credential lifetimes aggressively: a token that expires in an hour is uninteresting to a 2035 decryptor. Track your vendors' PQC roadmaps; Apple's PQ3 for iMessage and Cloudflare's hybrid post-quantum TLS are useful reference points. Plan for crypto-agility as well, because the migration won't be one-and-done and hybrid schemes are the near-term reality.
The quantum timeline is genuinely uncertain. The collection timeline isn't. Anything transmitted today under equivalent protection should be treated as eventually readable, and credentials are where that math hurts first.
