Harvest-now-decrypt-later (HNDL) is a procurement decision because the contracts you sign today determine whether encrypted data collected right now can be decrypted in three to five years, when quantum computers capable of breaking current encryption become viable. Security teams can patch software. They cannot retroactively re-encrypt data that has already left the building. That makes vendor selection, contract terms, and supply chain requirements the real line of defense. This article works through the specific questions procurement and security leaders need to answer together.
What data are attackers actually collecting right now?
Attackers are collecting anything encrypted with classical asymmetric cryptography, specifically RSA (Rivest-Shamir-Adleman) and ECC (Elliptic Curve Cryptography) key exchanges. That includes VPN (Virtual Private Network) session traffic, TLS (Transport Layer Security) handshakes, authentication tokens, and bulk data transfers. The content looks useless today. That is the point. The bet is that quantum hardware will make it readable later.
The targets are not random. Nation-state actors and well-resourced criminal groups prioritize long-shelf-life data: intellectual property, defense procurement documents, regulated health records, financial transaction histories, and government communications. If the data will still matter in five to ten years, it is worth storing now.
For organizations in the defense industrial base, this is not theoretical. Classified and controlled unclassified information (CUI) flowing between contractors, subcontractors, and government agencies travels over networks every day. Much of that traffic uses encryption standards that post-quantum computers will eventually break. The collection is already happening. The decryption is the part that is coming.
When does harvested data become a real liability?
Harvested data becomes a liability the moment a sufficiently powerful quantum computer, often called a cryptographically relevant quantum computer (CRQC), can run Shor’s algorithm against the key exchange that protected it. Most credible estimates place that window somewhere between 2030 and 2035, though some government agencies are planning for earlier. The liability is not gradual. It is a threshold event.
The practical implication is that data collected in 2024 or 2025 could be fully exposed in 2031. That means any sensitive information your organization transmitted before migrating to post-quantum cryptography (PQC) is permanently at risk. You cannot patch the past. You can only limit what gets collected going forward by migrating now.
For regulated industries, the liability extends beyond exposure. If harvested data includes protected health information, financial records, or defense-related intellectual property, the breach notification and compliance consequences apply at the point of decryption, not the point of collection. Legal and regulatory exposure can arrive years after the original interception.
Why does quantum risk show up in procurement, not just security reviews?
Quantum risk surfaces in procurement because the encryption a vendor uses today is baked into their product architecture, and changing it requires the vendor to act, not you. If a vendor’s platform relies on classical key exchange and has no post-quantum migration roadmap, you are locked into that exposure for the life of the contract. Security reviews catch current vulnerabilities. Procurement decisions determine future ones.
This is where defense contractor network security intersects directly with supply chain risk. A prime contractor can adopt post-quantum standards internally, but if a subcontractor’s software-defined networking layer still uses RSA-2048 for key exchange, the entire chain is exposed. The weakest cryptographic link determines the actual security posture.
There is also a regulatory driver. The NSA’s (National Security Agency’s) CNSA 2.0 (Commercial National Security Algorithm Suite 2.0) sets a migration deadline of 2030 for most national security systems. NIST (National Institute of Standards and Technology) finalized its first post-quantum cryptographic standards in 2024. Procurement teams that do not include PQC readiness in vendor requirements today will face emergency re-procurement cycles as those deadlines approach. That is expensive, disruptive, and avoidable.
What should procurement teams actually ask vendors?
Procurement teams should ask vendors four direct questions about post-quantum readiness. Vague answers about “monitoring the space” or “evaluating standards” are not acceptable responses in 2026. You need specifics.
- Which key exchange algorithms does your platform use today? If the answer is RSA or ECC without a hybrid post-quantum layer, ask when that changes.
- Have you implemented any NIST-standardized post-quantum algorithms? ML-KEM (Module Lattice Key Encapsulation Mechanism, formerly Kyber) and ML-DSA (Module Lattice Digital Signature Algorithm, formerly Dilithium) are the current standards. Vendors should be able to name them.
- Is your post-quantum implementation hybrid? Hybrid cryptography combines classical and post-quantum algorithms so that security does not degrade if a post-quantum algorithm is later found to have weaknesses. This is the recommended approach during the transition period.
- Can your platform be deployed in air-gapped or sovereign configurations? For defense industrial base and government customers, data sovereignty requirements mean cloud-only vendors may not qualify regardless of their cryptographic posture.
Also ask for a written cryptographic migration roadmap with dates. A vendor that cannot produce one is not ready, and that is a procurement risk, not just a security concern.
Which industries face the highest HNDL exposure?
The industries with the highest harvest-now-decrypt-later exposure are those where data has long-term strategic or regulatory value. Defense and aerospace top the list. Intellectual property, procurement data, and technical specifications for weapons systems or dual-use technology retain value for decades. Nation-state adversaries have strong incentives to collect and hold that data.
Healthcare and life sciences face significant exposure because patient records, clinical trial data, and genomic information carry long retention requirements and high black-market value. Financial services face exposure to transaction records, trading strategies, and client data. Government agencies and their contractors face exposure to anything classified or controlled.
Manufacturing and industrial sectors, particularly automotive and critical infrastructure, face a different flavor of risk. The concern is less about personal data and more about proprietary designs, supply chain configurations, and operational technology (OT) network traffic. For a Tier 1 automotive manufacturer, harvested design data could compromise competitive position years before a product launch.
The common thread is data longevity. If the information you transmit today will still be sensitive in 2031, you have HNDL exposure. Most organizations in regulated industries do.
How does post-quantum readiness differ from general encryption compliance?
Post-quantum readiness is not the same as encryption compliance. General encryption compliance, such as meeting FIPS-140 (Federal Information Processing Standard 140) requirements or enforcing TLS 1.3, confirms that your encryption meets current standards. Post-quantum readiness confirms that your encryption will survive a future threat model. The two are related but not interchangeable.
A system can be fully FIPS-140 compliant today and still be completely vulnerable to a CRQC. FIPS-140 validates the implementation quality of approved algorithms. It does not mandate post-quantum algorithms, though NIST is actively updating FIPS standards to include them. Compliance with today’s standards is necessary but not sufficient.
The practical difference shows up in audits and assessments. A compliance audit asks whether you are using approved algorithms correctly. A post-quantum readiness assessment asks whether those algorithms will hold against quantum-enabled adversaries and whether you have a migration path if they do not. Organizations that conflate the two will pass compliance audits while remaining exposed to HNDL attacks.
For defense industrial base quantum security specifically, the bar is higher. CNSA 2.0 mandates post-quantum algorithms for national security systems on a defined timeline. Meeting that requirement means going beyond general encryption compliance into active algorithm migration, which requires vendor support, updated network infrastructure, and in many cases, a rethink of how software-defined networking defense layers are architected.
How ZeroTier Quantum addresses HNDL risk
ZeroTier Quantum is ZeroTier’s next-generation encrypted overlay networking platform built specifically for post-quantum cryptographic security. It is designed for organizations that cannot afford to wait on their vendors to catch up. Here is what it delivers:
- Hybrid post-quantum cryptography at the transport layer: The ZeroTier Transport Protocol (ZTP) embeds NIST-standardized post-quantum algorithms directly into the key exchange, using a hybrid approach that maintains classical security during the transition period.
- FIPS-140 and CNSA 2.0 alignment: The platform meets the compliance requirements that defense contractors and government agencies face today, not just the ones that existed five years ago.
- Deployment flexibility for air-gapped environments: ZeroTier Quantum supports SaaS cloud, sovereign-gapped, and fully air-gapped configurations, which matters for defense industrial base customers with strict data residency requirements.
- Memory-safe architecture: Built in Rust, the platform eliminates entire classes of memory vulnerabilities that create additional attack surface in legacy networking stacks.
- Minimal footprint, high throughput: Up to 40 Gbps throughput with a memory footprint as small as 2 MB, designed for production environments where performance cannot be traded for security.
If your organization is evaluating how to address HNDL exposure before the procurement window closes, ZeroTier Quantum is built for exactly that conversation. Talk to the team about what a post-quantum migration looks like for your environment.
Related Articles
- Is SD-WAN actually enough to secure your government network?
- What does Salt Typhoon tell us about the limits of perimeter-based security?
- What does 'assume breach' mean for how you design your network today?
- NIST FIPS 203 Explained for Defense and Government Network Architects
- CNSA 2.0 Compliance and What It Actually Requires of Government IT Teams