Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article is part of the Microsoft Security Adoption Framework (SAF) concept and reference guidance.
Post-quantum readiness is primarily a cryptographic agility challenge: your organization must be able to discover, prioritize, and update cryptographic dependencies over time at enterprise scale.
Cryptographic agility is the ability of an organization to rapidly and safely change which cryptographic algorithms it uses. Building this capability is foundational for becoming quantum-safe.
The likelihood is increasing that quantum computing will eventually defeat some current cryptographic algorithms that underpin technical controls across modern environments. This topic is commonly referred to as post-quantum cryptography (PQC).
How this impacts security and organizational risk
If quantum-capable attackers can break vulnerable public-key cryptography in use, they can undermine trust in core security controls and significantly increase organizational risk.
Cryptography provides foundational trust for much of the technology environment. Authentication, digital signatures, software integrity, and secure communications such as TLS depend directly on cryptography, while many other security controls depend indirectly on those capabilities. This means post-quantum readiness affects far more than encryption: it can affect identities, applications, infrastructure, devices, software updates, communications, and the trust relationships between them.
PQC readiness affects almost all security domains because authentication, signing, and encryption are embedded across:
- Cloud and on-premises applications
- Identity and access systems
- Security service edge (SSE) and VPN infrastructure
- Network, storage, and platform infrastructure
- IoT and OT systems
- Partner and supply-chain integrations
What causes this challenge
Current cryptography depends on hard mathematical problems that are practical in one direction and difficult to reverse with classical computing.
Quantum computing changes this balance for some algorithm families. As capability matures, organizations need to:
- Identify vulnerable algorithms and dependencies.
- Replace them with quantum-resistant alternatives.
- Maintain readiness to evolve again as standards and implementation guidance continue to mature.
This is why cryptographic agility is critical, not optional.
The objective isn't only to replace today's vulnerable algorithms. Organizations need the ability to change cryptography repeatedly as standards, threats, implementations, and cryptanalytic understanding evolve. PQC creates the immediate migration need; cryptographic agility creates the durable ability to adapt as cryptography changes again.
How urgent is quantum-safe planning
Two factors make early action important:
- Transition lead time is long: large estates need multiyear planning, dependency mapping, and phased rollout.
- Harvest now, decrypt later risk exists now: long-lived sensitive data can be captured today and decrypted later.
At an operational level, becoming quantum-safe is a large-scale software, hardware, and infrastructure modernization program. Cryptography is embedded throughout operating systems, applications, services, protocols, certificates, libraries, firmware, devices, and partner dependencies. Organizations should therefore treat PQC readiness as a multiyear migration rather than a single cryptographic upgrade.
Starting early can also help organizations avoid resource and supply constraints as adoption accelerates. Some changes might require only software or configuration updates, while others might require new libraries, firmware, certificates, hardware, or replacement of systems whose vendors no longer provide suitable updates. Many organizations could need the same specialized products and services at roughly the same time.
This creates a dynamic similar to preparing for a natural disaster: organizations that prepare early can obtain the resources they need deliberately, while organizations that wait until urgency is widespread might face shortages, higher costs, limited alternatives, and increased exposure to low-quality products or scams.
Delaying increases the chance of compressed timelines, supplier constraints, and rushed implementation risk.
SAF approach for PQC readiness
Use SAF to coordinate cross-functional execution:
- Strategy and governance: establish ownership, sponsorship, priorities, and risk tolerance.
- Architecture: build enterprise cryptography and trust-chain inventory and dependency maps.
- Disciplined execution: sequence changes by risk, business criticality, and attack-path impact.
- Operations and validation: monitor rollout quality, regressions, and control effectiveness.
Planning a quantum-safe program
A practical transition plan should include:
- Discover where vulnerable algorithms are used and which systems depend on them.
- Evaluate vendor and platform support timelines for quantum-resistant options.
- Plan phased migration waves and rollback-safe change windows.
- Implement with governance, testing, and evidence tracking.
Additional planning considerations:
- Treat this as a program: PQC readiness spans multiple teams and disciplines.
- Prepare for different update types - Migration paths can vary significantly. Some dependencies can be addressed through software or configuration updates, while others might require new cryptographic libraries, certificates, firmware, hardware, or replacement of systems whose vendors no longer provide suitable updates. Track vendor support and quantum-resistant implementation timelines as part of migration planning.
- Prioritize strategically: focus first on high-value assets, identity/control planes, core trust services, and long-sensitivity data paths.