
If you run an IT environment, post-quantum cryptography may sound like a future problem. It is not.
This does not mean a cryptographically relevant quantum computer is breaking enterprise networks today. It means that changing the cryptography inside applications, servers, VPNs, certificates, appliances and vendor products will take years. Data encrypted today may also remain valuable long enough for someone to collect it now and attempt to decrypt it later.
For an IT manager, IT director or CTO, the practical question is therefore not, “When will a quantum computer arrive?” It is, “How long will it take us to identify and replace every quantum-vulnerable component in our environment?”
That work needs to begin now.
What is post-quantum cryptography?
Post-quantum cryptography, or PQC, is a new generation of cryptographic algorithms designed to resist attacks from both conventional and quantum computers. It runs on conventional servers, endpoints, routers and security appliances. It does not require an organization to own a quantum computer.
The main concern is with the public-key cryptography used for key establishment and digital signatures. Widely used mechanisms based on RSA, Diffie-Hellman and elliptic-curve cryptography could be broken by a sufficiently capable quantum computer.
In 2024, the US National Institute of Standards and Technology finalized its first principal PQC standards. These include ML-KEM for establishing shared secrets and ML-DSA and SLH-DSA for digital signatures. NIST now says organizations should begin applying the standards and migrating their systems.
The timelines IT leaders should know
NIST’s transition plan is aimed directly at US federal standards, but it also informs technology vendors, standards bodies and private enterprises worldwide. NIST expects quantum-vulnerable algorithms to be deprecated and ultimately removed from its standards by 2035, with higher-risk systems moving earlier.
India has set an even more immediate planning horizon. The National Quantum Mission was approved for the period from 2023–24 to 2030–31 to build India’s capabilities and ecosystem in quantum technologies. More specifically, the Department of Science and Technology’s 2026 Quantum-Safe Ecosystem in India strategy sets targets of quantum resiliency across Critical Information Infrastructure by 2029 and enterprise-wide PQC adoption by 2033.
These dates have different implications:
- Government bodies, Critical Information Infrastructure and regulated sectors should expect earlier requirements, sector-specific directions and procurement conditions.
- Private enterprises should treat 2033 as a migration horizon, not a date on which to start planning. Organizations supplying government, BFSI, telecom, defense or critical infrastructure may need to demonstrate readiness much sooner.
- NIST’s 2035 horizon is not a universal legal deadline for private companies. It is nevertheless highly relevant because operating systems, browsers, cloud platforms, certificate ecosystems, VPN protocols and security products are built around these standards.
CERT-In has also advised organizations across sectors to begin preparing for quantum-safe migration. The direction is clear even where a specific compliance deadline does not yet apply to an organisation.
The PQC clock is already running
PQC migration starts with a hybrid approach
An enterprise should not remove proven classical cryptography overnight and replace it everywhere with a new algorithm. The safer first stage is hybrid cryptography.
In a hybrid key exchange, the connection derives key material using both an established classical mechanism and a post-quantum mechanism. For example, a TLS or VPN session could combine elliptic-curve Diffie-Hellman with ML-KEM. The resulting session secret depends on both components.
This provides two useful protections. If the classical algorithm is later broken by a quantum computer, the post-quantum component protects the session. If an unexpected weakness is discovered in the newer PQC implementation, the classical component continues to provide its existing security.
Hybrid deployment is therefore a transition mechanism. It allows organizations to introduce PQC while maintaining interoperability, testing performance and retaining confidence in established cryptography. Over time, standards and implementations may move to PQC-only modes where appropriate, but the current enterprise journey begins with hybrid support and crypto agility.
Crypto agility matters just as much as the choice of algorithm. Your systems must be able to change cryptographic algorithms, certificates, libraries and key sizes without requiring a complete redesign every time a standard evolves.
AES is not being replaced
One of the most common misunderstandings about PQC is that all current encryptions must be discarded. That is not the case.
AES is symmetric encryption. It is commonly used to encrypt the actual data flowing through a TLS connection, IPsec tunnel or other secure session. PQC migration is primarily changing the public-key mechanisms used to establish that AES session key and the digital signatures used for authentication.
In a typical TLS session, elliptic-curve Diffie-Hellman is used to establish a shared secret. Keys derived from that secret are then used with an algorithm such as AES-GCM to encrypt application data. In a quantum-safe design, the vulnerable key-establishment step is replaced or supplemented with a mechanism such as ML-KEM. AES can continue to encrypt the data.
Quantum search techniques do reduce the theoretical security margin of symmetric algorithms. In practice, AES-256 is generally used where long-term quantum resistance is required. The central migration problem is not replacing AES. It is upgrading RSA, Diffie-Hellman, elliptic-curve key exchange and vulnerable digital signatures, while reviewing key sizes and configurations across the complete protocol.
What PQC actually changes in a TLS or VPN session
Change area 1: Applications that serve users
Every internet-facing and internal application that uses HTTPS depends on a cryptographic chain. That chain may include the web server, TLS library, load balancer, reverse proxy, web application firewall, CDN, API gateway, service mesh, certificate authority and the client connecting to it.
Adding PQC support to the application itself may not be enough. If TLS terminates at a load balancer or reverse proxy, that component must support the selected hybrid or post-quantum handshake. Internal service-to-service connections must also be reviewed. An external connection may be quantum-safe while traffic between the proxy and application server still uses a vulnerable key exchange.
IT teams should identify:
- Where TLS is terminated across public websites, APIs and internal applications
- Which cryptographic libraries and versions are in use
- Whether cloud platforms, CDNs, proxies and application delivery controllers support standardised hybrid key exchange
- Whether clients, browsers, mobile applications and older devices can interoperate
- How PQC affects handshake size, latency, CPU use, memory, packet fragmentation and inspection systems
- Where RSA or elliptic-curve certificates and signatures remain in the authentication chain
Digital signatures are a separate part of the transition. Even if a hybrid key exchange protects confidentiality, certificates, code signing, document signing, software updates and device identity may still depend on quantum-vulnerable signature algorithms. Both problems must be included in the roadmap.
Change area 2: VPN networks
VPNs are another priority because they protect site-to-site traffic, remote users, cloud connectivity and communications between critical locations.
IPsec, TLS-based VPNs and other tunnelling protocols normally use public-key cryptography during authentication and key establishment, then use symmetric encryption such as AES for the data plane. The VPN’s AES encryption does not automatically make the tunnel quantum-safe. If its session keys were established only through classical Diffie-Hellman or elliptic-curve Diffie-Hellman, that part of the design remains exposed to the future quantum threat.
A quantum-safe VPN should support standardised PQC or a hybrid key-establishment method, while continuing to use a strong symmetric cipher such as AES-256-GCM for tunnel traffic. It must also address peer authentication, certificate handling, rekeying and central management.
When assessing VPN products, ask vendors:
- Which standardised PQC algorithms are supported?
- Is the implementation hybrid, PQC-only or merely described as “quantum safe” without technical detail?
- Does PQC apply to key establishment, authentication or both?
- Can the feature operate across site-to-site, remote-access and cloud VPN deployments?
- What are the throughput, tunnel-establishment and hardware requirements?
- Can algorithms and policies be changed centrally as standards evolve?
- Is there a migration path for older branches and third-party peers?
PQC support should now be part of procurement requirements for firewalls, SD-WAN appliances, secure routers, VPN concentrators and SASE platforms that an organisation expects to operate into the next decade.
What should an IT leader do now?
The first task is discovery, not a large replacement project. Build a cryptographic inventory, sometimes called a Cryptographic Bill of Materials, covering algorithms, protocols, certificates, libraries, keys, appliances and third-party dependencies.
Then classify systems by the useful life and sensitivity of their data. Records that must remain confidential for ten or twenty years require earlier attention because of the risk that encrypted traffic could be captured today and decrypted later. Critical systems, long-lived devices and products with slow upgrade cycles should also move up the list.
A practical programme can follow six steps:
- Assign ownership for PQC readiness across infrastructure, applications, security, architecture and procurement.
- Inventory cryptography in web applications, APIs, VPNs, PKI, code signing, identity systems, backups and vendor products.
- Prioritise systems based on data lifetime, business criticality, regulatory exposure and replacement lead time.
- Add crypto agility and standardised hybrid PQC support to all new architecture and procurement requirements.
- Pilot hybrid key establishment in selected applications and VPN links, then measure compatibility and performance.
- Create a phased roadmap aligned with India’s 2029 and 2033 targets and NIST’s transition towards 2035.
The transition window is already open
Nobody can give an exact date on which a cryptographically relevant quantum computer will become available. An organization does not need that date to make a sound decision.
Enterprise migrations take time. Hardware refresh cycles are long. Applications depend on libraries and platforms that may not yet expose the required capabilities. VPNs must interoperate across branches, partners and clouds. Certificates, signing systems and embedded devices can remain in service for many years.
PQC is therefore not a single upgrade to schedule near 2033 or 2035. It is a multi-year change to the cryptographic foundation of the IT environment. Begin with visibility, insist on crypto agility, introduce standardised PQC through hybrid deployments, and make quantum readiness part of every technology decision made today.
The objective is simple: complete the transition before quantum risk becomes an operational emergency.
References
- NIST Post-Quantum Cryptography Project
- NIST IR 8547: Transition to Post-Quantum Cryptography Standards
- Department of Science and Technology: National Quantum Mission
- Department of Science and Technology: Quantum-Safe Ecosystem in India
- CERT-In: Transitioning to Quantum Cyber Readiness
See it in your environment
Talk to a NetSense security architect about applying this to your stack.