Quantum Security Network security

Why quantum-safe networking needs to be on your 2026 agenda

4 min. read
Placeholder for Quantum Safe NetworkingQuantum Safe Networking
Nokia

Share

The question is no longer whether quantum computing will break today's encryption. It is whether your network will be ready when it does.

Quantum computing is shifting from research into engineering. The board-level issue is not whether a cryptographically relevant quantum computer exists today; it is whether you are still assuming that today's public-key cryptography will protect long-lived data and long-lived trust for the next 10 to 15 years. And the window to act is shorter than most leadership teams assume.

Most organisations rely on public-key cryptography everywhere: for secure web traffic, VPNs, device identity, software signing, and the certificates that hold PKI together. The algorithms behind RSA, Diffie–Hellman, and elliptic-curve cryptography are expected to become breakable by sufficiently capable quantum systems. That creates two types of exposure:

  1. Confidentiality risk for data that must remain secret for many years.
  2. Integrity and trust risk when authentication and digital signatures can no longer be relied on.

A common mistake is treating this as an application problem only. It is also a networking problem because the network carries the highest-value traffic, keys and identities at scale. That is why Nomios and Nokia are focusing on quantum-safe networking, with the data centre fabric and interconnect as a priority.

The urgency is driven by “harvest now, decrypt later”

Attackers do not need quantum capability to benefit from future decryption. If traffic is captured today, it can be stored and decrypted later when quantum capability becomes available. This matters for data with a long shelf life: regulated personal data, intellectual property, long-term contracts, M&A material, energy and utility telemetry, healthcare, and state-related supply chains.

Even if you believe quantum decryption is a decade away, many networks and platforms have refresh cycles that span five to seven years. Waiting for certainty compresses the migration window into a period where you have less vendor choice, higher implementation risk, and less room for phased change.

What does “quantum-safe networking” mean in business terms?

Quantum-safe networking is not a single product or a single algorithm swap. Nokia frames it as defence-in-depth across multiple network layers, combining strong encryption, sound key management, and a roadmap for post-quantum cryptography (PQC).

For executives, it helps to translate this into outcomes:

  1. Keep sensitive traffic confidential for its full required lifetime
  2. Keep identities, trust chains, and signed updates trustworthy
  3. Avoid a “big bang” replacement by building crypto-agility into the network
  4. Meet regulatory and customer expectations as standards mature
  5. Rely on trusted network infrastructure vendors.

Why the data centre fabric and DCI should be first

The data centre fabric is where sensitive east-west traffic concentrates. It is also where automation, orchestration, and service-to-service dependencies amplify the impact of weak cryptography. The same is true for data centre interconnect (DCI), where replication and backup streams are often the first targets for traffic capture.

Starting with the fabric and DCI is a pragmatic decision:

  • The highest-value traffic is there
  • There are clear choke points where encryption and key control can be standardised
  • Network refresh and expansion projects create natural delivery milestones
  • You can improve the situation now without waiting for every application to migrate

This is the same practical mindset Nokia uses in mission-critical sectors like utilities, where long asset lifecycles and long-lived data are normal.

Placeholder for Hetportretbureau HR T1 A0593Hetportretbureau HR T1 A0593

Standards momentum: this is no longer speculative

NIST has approved the first set of post-quantum cryptography standards as FIPS 203, 204 and 205.

That matters because it drives vendor roadmaps, procurement requirements, and long-term interoperability. It also reduces the risk of betting on approaches that never become widely supported.

Your organisation does not need to migrate everything to PQC tomorrow. It does need a plan that keeps your network and identity foundation aligned to these standards as vendors roll support into mainstream releases.

What can be done now, and what belongs in the roadmap

A useful way to steer this programme is to split work into “now” and “next”.

Now: reduce exposure on the highest-value links

  • Use proven, strong encryption on the links that carry your crown-jewel traffic, including fabric uplinks and DCI. Nokia’s quantum-safe networking guidance highlights multi-layer cryptography and operational key management as the near-term baseline.
  • Make key governance a network KPI: key size, quality and rotation, separation of duties, audit trails, and monitoring.

Next: migrate the trust layer to post-quantum cryptography

  • Plan how device identity, certificates, management-plane access, and secure automation will adopt PQC, often via hybrid approaches during the transition phase.
  • Build in crypto-agility so you can change algorithms without redesigning the network every time standards evolve.

Nokia’s view of quantum-safe networking as a journey, not a label, is relevant here. You are building a security posture that stays current over time, rather than declaring a one-off project “done”.

Where quantum key distribution fits

You will hear about quantum key distribution (QKD), including satellite-based approaches. It is advancing, but most enterprises should treat it as selective rather than universal in the near term. Industry commentary on space-based QKD is clear that early commercial use is still a few years away.

A sensible leadership position is: do not wait for QKD to act. Build a network security architecture that can incorporate QKD where it fits later, while upgrading encryption and preparing for PQC now.

Next steps for the upcoming 6–12 months

A C-level sponsor should ask for four concrete deliverables:

  1. A crypto exposure map for the network
    Where public-key cryptography is used for authentication and key exchange, and which links carry long-lived sensitive data.
  2. A fabric and DCI quantum-safe baseline
    A target design for link and transport encryption, key governance, monitoring, and operational ownership.
  3. A PQC readiness plan for the trust layer
    Certificates, device identity, management-plane access, automation tooling, and vendor roadmap alignment.
  4. Procurement and contract language
    Requirements for standards alignment, crypto-agility, and upgrade paths, tied to refresh programmes.

Nomios and Nokia can deliver this as a staged programme that matches your refresh cycles and risk priorities, starting where you get the fastest reduction in long-lived exposure: the data centre fabric and the links that connect your sites.

Get in touch

Do you want to know more about this topic?

Our experts and sales teams are at your service. Leave your contact information and we will get back to you shortly.

Call now
Placeholder for Portrait of french manPortrait of french man