TL;DR
Harvest Now, Decrypt Later collection against high-value targets has been active for years. For organizations in targeted sectors, assume some encrypted traffic is already in an adversary archive.
Q-Day only completes the exposure that has already started.
Decrypted credentials and keys in that archive may still be valid. The decrypt event is likely the precursor to a targeted attack wave.
Migration stops the ongoing collection, but it does not address data already in the archive. Both problems need separate planning tracks.
Quantum agility, the ability to move cryptographic protections and credentials quickly, applies to migration, to Q-Day response, and to the secondary attacks that follow. Build this capability before you need it.
The Harvest Now, Decrypt Later campaign against high-value targets has been a real and ongoing threat for several years. CISA, NSA, and NIST have described the collection of encrypted traffic at scale in operational guidance since at least 2022. If your organization operates in financial services, healthcare, defense, government contracting, critical infrastructure, or any sector that represents meaningful intelligence value to a nation-state adversary, assume some of your encrypted traffic is in an adversary archive.
Q-Day, the moment when a sufficiently powerful quantum computer can factor RSA-2048 and solve elliptic curve problems at practical scale, only completes the exposure that has already started. That framing creates two distinct planning problems. The first is the forward problem: stop generating traffic that will be readable at Q-Day by completing your migration before capability arrives. The second is the historical problem: some data is already gone, and when Q-Day arrives, it becomes readable and can be weaponized. The adversary already has the data, and they’re waiting for the key.
A previous piece in this series argued for crypto agility: building the organizational capability to change cryptographic protections quickly, because standards shift and algorithms fall. That argument extends beyond migration. When the archive opens, you need the same agility applied to your response: rotating credentials and keys at speed, revoking what can still be revoked, adapting to the targeted attacks that follow. Quantum agility is the capability that determines how well you come through the decrypt event.
What Has Already Left
The mechanisms of harvest-now, decrypt-later are well established. An adversary positioned to collect network traffic captures TLS sessions, VPN tunnels, and authentication exchanges. The data is stored. The encryption is mathematically sound today, but when capability arrives, it becomes solvable.
The NSA published its Commercial National Security Algorithm Suite 2.0 in 2022 with explicit urgency: the agencies responsible for protecting classified communications treat this as an active threat.
National Security Memorandum 10, signed on May 4, 2022, directed federal agencies to prioritize systems based on the value of their data to an adversary with future cryptanalytic capability.
OMB M-26-15 (June 24, 2026) moved the federal civilian PQC deadline from 2035 to December 31, 2030, implementing an Executive Order signed two days earlier.
Five years of planning runway gone in one memo, from a president briefed on classified adversary capability assessments. The technical feasibility estimates support the same urgency.
Craig Gidney’s May 2025 research estimated the qubit requirement for factoring RSA-2048 at fewer than one million noisy qubits, down from a 2019 estimate of approximately 20 million. These are engineering models rather than delivery forecasts. But the trajectory matters for planning: the gap between current hardware and the required threshold is narrowing in the direction that makes the 2030 window credible.
What is likely in an adversary’s archive for a targeted organization depends on what traversed the network. VPN and remote access sessions carry authentication material, internal communications, and operational data. TLS connections to cloud services, SaaS platforms, and business applications carry file content, credentials passed in headers, and session tokens. Long-lived private keys, if they were ever transmitted, backed up over the network, or provisioned remotely, are candidates for collection. The adversary cannot read any of this today, but that changes at Q-Day.
What Q-Day Unlocks, and What Comes Next
When the archive becomes readable, the exposure is not only historical data. Password patterns, API key formats, certificate private keys, and service account credentials that were active three years ago are often still active today, or close enough to a credential stuffing baseline that the gap is trivial to bridge. The adversary can walk in using material your network handed them years before Q-Day.
Q-Day itself will not be announced with the press release you are waiting for. Adversaries with working cryptanalytic capability have a strong incentive to use it quietly. The first indicator may be a credential appearing in a targeted phishing campaign or an API key used against a system the attacker should not know about. By the time you see those signals, the decryption is already underway.
This is where quantum agility becomes operational. Rotating credentials and keys at scale, revoking certificates across an estate, invalidating API keys in bulk, and activating incident response before the targeted attack wave fully materializes: that is a different capability from completing a TLS migration. The migration determines how much data is in the archive. The response capability determines what the attacker can do with it once the archive opens.
When it comes to compliance, the argument that data was collected at one point in time and became readable only when capability later arrived is legally novel. Your legal and compliance teams need to reason through your notification posture now, not in the 72-hour window after capability is announced.
Quantum Agility: The Capability Behind Both Tracks
The companion article in this series framed crypto-agility as a migration property: the ability to replace cryptographic protections quickly when standards shift or algorithms fall. That remains the right framing for the forward track. The organizational infrastructure required to swap algorithms at speed (centralized encryption governance, a living cryptographic inventory, tested transition procedures) is the same infrastructure you need to rotate credentials at speed after the archive opens. Agility is an organizational capability with three dimensions:
Migration agility: The ability to complete the first migration on a defined schedule and execute subsequent changes as standards evolve. Measured by migration completion date for highest-exposure systems and demonstrated time-to-change in a representative exercise.
Response agility: The ability to rotate keys, revoke credentials, reissue certificates, and invalidate API keys at the scale and speed a Q-Day response requires. An organization that has never rotated its full certificate estate does not know how long that takes. Find out before it matters.
Attack adaptation agility: The ability to detect and respond to intrusions using decrypted historical intelligence. Adversaries entering with valid credentials look like authorized access. Detection and response programs need behavioral baselines and playbooks that treat “valid credential, unexpected behavior pattern” as a high-confidence signal, because that is what Q-Day-enabled access looks like. All of these can be measured and improved now. A Two-Track Plan Track 1: Address what is already in the archive
Scope the historical exposure. Map the categories of data your organization transmitted under vulnerable cryptography over the past several years. Long-lived private keys, credential exchanges, sensitive business communications, and operational data are the priority categories. You cannot know exactly what was collected, but you can establish what was in scope and build your response planning around the worst-case subset. This is a data classification exercise owned by security architecture or GRC, combining network traffic scope analysis with existing data inventory records.
Rotate long-lived credentials and keys now. Any private key, service account credential, API key, or authentication material that was ever provisioned, transmitted, or backed up over a network under vulnerable cryptography should be considered a candidate for adversary collection. Rotate it before Q-Day. Waiting until capability is announced means competing with your own crisis response for the same operational bandwidth. The rotation capability you build for this exercise is the same one you need at Q-Day speed. This is an IAM and platform engineering function, requiring coordination with individual service owners who hold the material.
Build and test a Q-Day response plan. Define what the first 48 hours look like when credible Q-Day capability is announced: who leads the response, what the mass credential rotation procedure is, which notification obligations apply, and what triage criteria determine which systems and keys to prioritize. Run a tabletop against a realistic scenario: adversaries announce capability, credential abuse begins within days. The gaps that surface are the gaps you need to close while there is still time to close them calmly. Security operations owns the response plan; legal and compliance co-own the notification track.
Work with counsel on notification obligations. Engage legal and compliance teams now to map which regulatory frameworks apply to your most sensitive historical data categories and what a Q-Day disclosure event would require. The 72-hour window under GDPR and similar frameworks was not designed for a cryptographic event that unfolds across days or weeks. Establish your position in advance. Legal leads this; the CISO provides the security evidence base and the data classification output from the scoping exercise.
Track 2: Secure going forward
Establish a migration completion date for highest-exposure systems. Migration stops new collection from joining the archive. Set a realistic completion date for the systems generating your most sensitive long-lived data, and treat that date as the competitive number. Phased roadmaps are valuable. An unscheduled migration is not a migration.
Prioritize by exposure value and migration lead time. Systems generating data that must remain confidential for ten or more years deserve earlier placement in the migration sequence than systems carrying short-lived operational data. A service that takes two years to migrate and must carry sensitive data for a decade needed to start that work already.
Check vendor commitments against a 2028 delivery window. A vendor planning PQC support in 2031 cannot help you migrate highest-exposure systems ahead of the early end of the adversary capability window. Identify your critical-path vendors and confirm delivery timelines. The conversation that takes six months should have started six months ago.
The Plans Are What Matter
Q-Day is a fixed point in the future. What is already in adversary archives is not recoverable, but what leaves your network from here is still a choice. And how quickly you can respond when the archive opens is a capability you either have or you are building under pressure.
The migration and the response plan are the two deliverables. Move your most sensitive traffic to quantum-resistant protection before capability arrives. Have a tested response plan ready when the archive opens. Neither is complicated to describe, but both take longer to execute than most programs currently budget for.
Start both now, run them in parallel, and measure them by completion date and tested procedure.
Learn more about how Aviatrix Harvest and Decrypt Protection provides post-quantum-ready encryption and egress governance.
Frequently Asked Questions
CISA, NSA, and NIST have described it as an active threat in binding operational guidance since at least 2022. NSA CNSA 2.0 (2022) and NSM-10 (May 4, 2022) directed migration timelines based on the judgment that collection of valuable encrypted traffic was a present concern. Public attribution of specific HNDL campaigns is limited by classification and disclosure constraints, but the US signals intelligence community treating it as present-tense in policy documents that bind federal agencies is a substantive data point.
You cannot know with precision. What you can map is what your organization transmitted under vulnerable cryptography and which of that data carries long-term value. Priority categories: authentication credentials and API keys, private keys that were ever transmitted or provisioned over the network, sensitive business communications, operational and architectural data, and long-lived records (financial, personnel, strategic). That inventory, scoped to the worst-case, is your planning input.
Does Q-Day constitute a notifiable event under GDPR, HIPAA, or state law? This is legally unresolved for most organizations. Collection at one point and readability at a later point does not map cleanly onto notification frameworks designed for direct intrusions. Engage legal and compliance counsel now to establish your position. The time to reason through notification obligations is before the 72-hour clock starts.
Crypto agility, as discussed in the companion article, is the ability to replace cryptographic algorithms quickly as standards and findings evolve. Quantum agility extends that to the full lifecycle: migration before Q-Day, rapid credential and key rotation in response to the decrypt event, and adaptation to the targeted attacks that follow when adversaries weaponize what they have decrypted. The organizational infrastructure for both is largely the same.
Start with the combination of data lifetime and migration lead time for the forward track, and with credential rotation for the historical track: they are independent and can run in parallel. Systems generating data that must remain confidential for a decade or more deserve the earliest migration placement. Credentials and keys that were transmitted under vulnerable cryptography should be rotated regardless of migration status. Q-Day response planning and legal preparation can begin immediately; neither requires migration to be complete first.
Ready to see Aviatrix in action?
Get a personalized live demo walkthrough or explore our latest deep-dive cloud threat research intelligence.
Gartner Strategic Roadmap for Zero Trust Security Programs 2025 Report
Download and gain actionable insights to advance your cloud security strategy.
