What Is Quantum Computing Security?

Will quantum computers be able to break today’s encryption?

A sufficiently powerful quantum computer could threaten some of today’s encryption, but when such a machine will exist is uncertain. The National Institute of Standards and Technology (NIST) describes quantum computing as still being in its infancy; that uncertainty argues against panic, not against preparation.

The distinction that matters is between public-key cryptography and symmetric encryption. Quantum computing is expected to pose a more significant challenge to certain public-key methods used for tasks such as establishing keys and creating digital signatures. The effect on symmetric encryption is more limited, so “quantum computers break encryption” is too broad a summary.

That difference changes what a sensible response looks like. A transition plan should identify the particular algorithms and systems in use rather than assume that every encrypted file or connection faces the same exposure. NIST’s overview of post-quantum cryptography also stresses that the timeline for a cryptographically relevant quantum computer is unknown.

Which encryption methods are most vulnerable to quantum computing?

Public-key methods including RSA, Elliptic Curve Diffie-Hellman (ECDH), and Elliptic Curve Digital Signature Algorithm (ECDSA) are among those that will need updating, replacement, or significant alteration for quantum resistance, according to guidance from CISA, the NSA, and NIST.

These algorithms support important functions in digital systems, but an organization cannot determine its exposure just by checking a headline list of algorithms. Cryptography may be embedded in network protocols, applications, software libraries, servers, end-user systems, firmware, software updates, and products supplied by vendors. The agencies recommend that a cryptographic inventory cover those areas, because a component that is out of sight can still be part of a system’s security dependencies.

NIST finalized three post-quantum standards on August 13, 2024: FIPS 203 (ML-KEM) for key establishment, FIPS 204 (ML-DSA) for digital signatures, and FIPS 205 (SLH-DSA), also for digital signatures. NIST says the standards are ready for use and encourages system administrators to begin transitioning. Their existence gives organizations standards to plan around; it does not remove the work of finding where older cryptography is used or coordinating changes across products and suppliers.

Post-quantum cryptography (PQC) means cryptographic methods designed to protect information against attacks from both conventional and quantum computers. It is a change to the algorithms used in conventional computing systems, not a reason to assume every organization needs to replace every security product at once. The sequence is practical: discover what is deployed, understand what data and functions depend on it, and coordinate a transition with the teams and vendors responsible.

What does “harvest now, decrypt later” mean for my data?

“Harvest now, decrypt later” means an attacker collects encrypted information today and keeps it in the hope of decrypting it with a future quantum computer. That makes the risk relevant now for information whose confidentiality must last many years, even if no cryptographically relevant quantum computer is currently available.

NIST puts the issue plainly: “Some secrets remain valuable for many years.” The threat is therefore shaped by the expected useful life of the information, not only by the date a new machine might be built. If a business handles records, plans, or communications that must remain confidential for a long period, it has reason to identify those data stores and how they are protected.

The joint CISA, NSA, and NIST guidance warns that threat actors could target data today that will still require protection in the future. Their recommended starting points can be organized as a short readiness sequence:

1. Inventory cryptography. Record where cryptographic systems and algorithms appear across networks, endpoints, applications, servers, libraries, firmware, updates, and vendor products.
2. Prioritize sensitive data. Identify information that must remain confidential for many years and the systems that protect it.
3. Assess exposure and dependencies. Determine which systems rely on public-key algorithms identified for transition and how changes could affect connected services.
4. Ask vendors about migration. Request information about their post-quantum plans, product dependencies, and how updates will be delivered.
5. Build a roadmap. Use the inventory and risk assessment to sequence transition work rather than treating the change as a single switch.

For individuals, the supplied guidance does not describe a personal migration procedure or identify a product to buy. Practical steps supported by the broader transition picture are to keep software updated, pay attention to security updates from service providers, and ask providers how they plan to move to post-quantum standards. The point is to learn whether the services holding or protecting important information have a transition plan, not to infer that a familiar encryption label answers every question.