Cryptographic system or standard | Function | Current use cases | Resistance level |
---|---|---|---|
RSA-2048 | Encryption and identity validation | Internet traffic, including websites of European banks, energy and transport companies, and other institutions. | Broken by quantum computing |
RSA-3072 | Encryption and identity validation | VPNs, financial transactions, security level required for intelligence, and e-passports. | Broken by quantum computing |
DH-3072 | Key exchange | Internet protocols such as SSL/TLS, SSH, and IPSec. | Broken by quantum computing |
256-bit ECDSA | Identity validation | Bitcoin and Ethereum exchanges, as well as internal enterprise communications. | Broken by quantum computing |
In light of these vulnerabilities, organizations need to act now to ensure their data stays secure. Due to the complexity of retrofitting cryptographic infrastructure—including updates to software, hardware, and third-party vendor systems—it can take up to 10 years to transition fully. Organizations that wait until quantum computers become mainstream risk exposing decades of sensitive data.
Post-quantum cryptography refers to encryption methods that are designed to withstand attacks from both classical and quantum computers.
Unlike traditional algorithms, post-quantum cryptography uses mathematical problems that are considered intractable—even for quantum machines.
Examples include lattice-based, hash-based, and code-based problems. It’s worth noting that these are all compatible with existing infrastructure and can enhance classical security.
Governments and standardizing bodies are already driving the shift to post-quantum cryptography.
NIST finalized their first PQC standards in 2024, including lattice-based algorithms such as ML-KEM (for encryption) and ML-DSA (for digital signatures).
Similarly, the U.S.-based National Security Administration mandates post-quantum cryptography adoption for national security systems by 2025.
The EU is leading collective adoption of post-quantum cryptography to avoid individual countries developing their own separate policies.
The UAE has also announced a new post-quantum cryptography regulation.
Transitioning to post-quantum cryptography, while essential, is complex.
There are several hurdles:
Post-quantum cryptography algorithms require larger keys and more processing power, impacting systems with limited resources.
Most organizations lack visibility into where and how encryption is used across their tech stack.
Many software/hardware providers are still unprepared to support post-quantum cryptographic standards.
With NIST still evaluating additional algorithms, some companies worry about backing the “wrong” standard.
A transition of this scale has no precedent. The technical complexity creates hesitation about disrupting critical systems during the transition.
If quantum computers advance more quickly than expected, organizations preparing for the transition now may need to adopt more advanced solutions in the future.
The transition to post-quantum cryptography requires significant time and resources, encompassing updates to hardware, software, and digital infrastructure, as well as retraining staff.
Many organizations choose to manage the challenges of the transition using a hybrid approach to cryptography. Hybrid systems combine classical encryption with quantum-resistant algorithms, creating two layers of protection.
This strategy is endorsed by several leading institutions with strong security postures:
The National Institute of Standards and Technology (NIST) recommends hybrid deployments to mitigate risks during the transition from classical to post-quantum cryptography.
Google Chrome and Meta already use hybrid TLS, ensuring backward compatibility while testing PQC at scale.
The Internet Engineering Task Force (IETF) is in the process of standardizing hybrid key exchange for TLS 1.3, streamlining adoption across industries.
Organizations can deploy and test new quantum-resistant algorithms while ensuring they are still protected by an existing secure algorithm.
Even if one algorithm fails, the other maintains security.
Hybrid security models protect against "harvest now, decrypt later" attacks, which 74% percent of organizations are concerned about.
Older systems that will be phased out before the transition is complete can continue to use classical cryptography, which eases the transition process.
Hybrid approaches can be complex to implement given the challenges of coordinating dual algorithms across hybrid cloud and on-premises systems. They can also lead to increased performance overhead. Additionally, compliance requirements are evolving constantly, which can create uncertainty.
Fortunately, while hybrid post-quantum cryptography does introduce some additional latency, the increase is often manageable and becomes less significant with larger data transfers or under challenging network conditions. Additionally, some post-quantum algorithms like Kyber and Dilithium can outperform their classical counterparts in certain operations, potentially offsetting some of the latency increases.
There are several approaches for managing the
latency and other potential challenges:
These strategies, combined with frequent audits, will help organizations balance security and efficiency during their transition to post-quantum cryptography.
We recommend beginning your transition to post-quantum cryptography with a high-level roadmap such as the following:
Based on your data and system shelf life, organizations should assess the urgency for their transition to post-quantum cryptography. McKinsey recently released a report outlining the risk levels for various industries. Banking, insurance, and the public sector are already at risk, with life sciences, global energy and materials, and advanced industries at risk in the next five years.
Use automated tools like QuantumGate’s Crypto Discovery Tool to create a comprehensive inventory of cryptographic assets and identify vulnerabilities.
Test NIST-approved algorithms such as Kyber and Dilithium in non-critical workflows and apply the lessons learned to higher-stakes systems.
Ensure third-party tools such as cloud service providers can integrate their services with your post-quantum cryptography roadmap.
Follow the EU’s CEPS Task Force, NIST, or news about your region’s regulatory updates to ensure you stay compliant.