Q-Cyber Magazine

Enterprise · 21 November 2026 · 6 min read

Harvest now, decrypt later: Protecting institutional communications first

Recorded traffic cannot be protected after the fact. Institutions should move key establishment for messaging, calls, VPNs and file exchange to hybrid post-quantum constructions first, using FIPS 203 and the IETF's 2026 hybrid TLS standard.

Abstract graphic of a lattice of connected points in Knowlcom blue

Most post-quantum programmes begin with servers and certificates. For harvest-now-decrypt-later, a better starting point is the network path: the messages, calls, files and tunnels that an adversary can copy today and keep.

Why communications come first

Stored data can be re-encrypted. A copy of network traffic taken last year cannot. If the session keys for that traffic were agreed with RSA or elliptic-curve Diffie–Hellman, its confidentiality depends on those algorithms surviving for as long as the content matters. NIST's announcement of NIST IR 8547 on 27 October 2026 is direct: today's encrypted data is already at risk, because adversaries can collect it now and decrypt it when quantum technology matures.

India's DST task force report draws the operational conclusion. Planning is to proceed under an "assume-breach" principle, because retrospective mitigation is not feasible after Q-Day. Prioritisation is not limited to designated critical sectors: any network handling data with a long shelf life or extended confidentiality requirements is to be prioritised.

For most institutions, that network includes the communications layer. Board deliberations, negotiations, investigations, patient referrals, research collaboration and operational instructions travel as messages, calls and attachments. Their confidentiality life is usually longer than the life of the system that carried them.

The Mosca test, applied to a conversation

TEC's technical report on PQC migration recommends the Mosca model. Let X be the years the information must stay secure, Y the years needed to migrate, and Z the years until a capable quantum computer exists. If X plus Y is greater than Z, the data is at risk.

Applied to communications, X is set by the content, not the channel. A scheduling message may need protection for weeks. A procurement negotiation, a legal strategy or the identity of a source may need it for a decade or more. Y is the time needed to replace key establishment in every client, gateway and relay that carries those conversations, and for most institutions it is measured in years. The DST report notes that research estimates of the window converge on 2030 to 2032, while stressing that the timing is uncertain and that the threat to recorded data starts earlier.

The result is a simple rule. Where X is long, key establishment for the channel should move now, even if signatures and certificates follow later.

Exhibit 1

First post-quantum moves by communication channel

ChannelWhat can be recorded todayFirst moveReference
Web and API traffic (TLS 1.3)Handshakes and encrypted sessionsEnable a hybrid group such as X25519MLKEM768RFC 10024; FIPS 203
Site-to-site and remote-access VPNs (IKEv2)Tunnel set-up and tunnelled trafficAdd a post-quantum key exchange alongside (EC)DHRFC 9370; FIPS 203
Messaging, calls and file exchangeMessages, media and attachments in transitRequire end-to-end encryption with hybrid post-quantum key establishment; keep relays outside the trust boundaryNIST IR 8547; DST report
Email and message archivesStored and forwarded copiesInventory the protection in use; plan re-encryption of stored copiesTEC 910018:2025; CERT-In CBOM guidelines

Source: Knowlcom framework drawn from RFC 10024 (August 2026), RFC 9370 (May 2023), NIST FIPS 203 and IR 8547, the DST task force report (May 2026), TEC 910018:2025 and CERT-In's BOM guidelines (9 July 2025). Qualitative; it does not assign probabilities or counts.

Key establishment first, signatures next

Confidentiality and authenticity are separate tracks. Harvest-now-decrypt-later is a confidentiality problem, and its remedy is post-quantum key establishment. The DST report also names "trust now, forge later", which concerns signatures and certificates; its remedy is ML-DSA or SLH-DSA in the PKI, under FIPS 204 and FIPS 205. Both need plans, but key establishment for long-lived traffic comes first.

Hybrid key establishment is the practical bridge. RFC 10024, published by the IETF in August 2026, defines three hybrid groups for TLS 1.3: X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024. Each combines ML-KEM with an elliptic-curve exchange, so the session stays secure as long as either component holds. For VPNs, RFC 9370 extends IKEv2 to run several key exchanges when a security association is set up, so that a post-quantum exchange can sit alongside (EC)DH. NIST accommodates hybrid constructions, noting that they are more conservative but need more computation. TEC's report recommends hybrid solutions to mitigate short-term risk during the transition.

The overheads are real but bounded. Under RFC 10024, the X25519MLKEM768 client share is 1,216 bytes and the server share 1,120 bytes, against 32 bytes each for X25519 alone. That cost is paid in the handshake, once per session. The DST report observes that long-lived sessions see minimal impact, while frequent renegotiation and short sessions amplify PQC costs, and that microsecond-level environments in defence and telecom need specific engineering.

Design choices that limit what can be harvested

Algorithms are only part of the answer. Three architectural choices reduce what an adversary can usefully collect.

End-to-end encryption. If content is encrypted between endpoints, a compromised relay, gateway or carrier yields only ciphertext. The harvest target moves from the network to the endpoints.

Ephemeral session keys. Fresh key agreement for each session limits what any single recorded exchange can reveal. Combined with post-quantum key establishment, it stops one future break from unlocking a whole archive.

Deployment that matches sensitivity. Institutions with the longest confidentiality lives often choose self-hosted or tenant-hosted infrastructure, so that relays and storage remain under their own operational control.

Naad Secure, one of Knowlcom's applications, is a secure communication and collaboration platform for government, defence and enterprise. It is end-to-end encrypted with PQ hybrid sessions; relays cannot read content.

A first-quarter plan for institutions

  1. List the channels that carry long-lived content: executive and board communication, legal, investigations, research collaboration, citizen or patient data exchange and operational instructions.
  2. Record what protects each channel today: the key establishment in use, and who controls the relays, gateways and storage.
  3. Enable hybrid key agreement where products already support it, starting with internet-facing TLS and inter-site VPNs.
  4. Ask suppliers for evidence. Request a CBOM and a dated plan for post-quantum key establishment from messaging, conferencing and file-transfer suppliers, as CERT-In's BOM guidelines and the DST procurement recommendations anticipate.
  5. Shorten retention where you can. Content that is not kept cannot be exposed later from stored copies.

Implications

  1. Start with the path, not the server. Traffic copied today is the exposure that cannot be undone.
  2. Move key establishment first, using FIPS 203 in hybrid form.
  3. Keep relays outside the trust boundary with end-to-end encryption.
  4. Make supplier road maps a procurement criterion.

What this means for enterprise

Every month that sensitive conversations travel under classical-only key establishment adds to an archive that may later be readable. The standards to stop that accumulation are published. What remains is inventory, configuration and procurement, and none of it needs to wait.

Sources

  1. NIST Report Provides Guidelines for Transition to Post-Quantum Cryptography Standards (27 October 2026)
  2. NIST IR 8547, Transition to Post-Quantum Cryptography Standards
  3. NIST FIPS 203, 204 and 205 announcement (13 August 2024)
  4. RFC 10024, Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3 (August 2026)
  5. RFC 9370, Multiple Key Exchanges in IKEv2 (May 2023)
  6. DST, Quantum-Safe Ecosystem in India: Roadmap to Quantum Resiliency (May 2026)
  7. TEC 910018:2025, Technical Report on Migration to Post-Quantum Cryptography
  8. CERT-In, Technical Guidelines on SBOM, QBOM & CBOM, AIBOM and HBOM, Version 2.0 (9 July 2025)