Category: Cyber Threats & Attacks

Quantum Computing Risk

Also known as: Quantum Risk, Quantum Computing Cybersecurity Risk, Quantum Threat to Cryptography

Simply put

Quantum computing risk is the danger that future, sufficiently powerful quantum computers could break the encryption that protects sensitive data and communications today. Because much of modern security relies on cryptographic methods once considered secure for decades, a capable quantum computer could expose or compromise that protected data. This is a security and technology concern rather than an insurance coverage term, and whether related losses are insurable depends entirely on specific policy wording.

Formal definition

Quantum computing risk refers to the potential for a cryptographically relevant quantum computer (CRQC) to defeat modern cryptographic algorithms, undermining the confidentiality and integrity assumptions on which current data protection depends. The primary exposure is to public-key (asymmetric) cryptography, where a CRQC could break widely deployed encryption standards; symmetric ciphers and hashing algorithms are generally considered to face a smaller reduction in effective strength rather than outright collapse. A frequently cited concern is the compromise of sensitive data, including scenarios in which currently protected information is exposed once decryption becomes feasible. Some analyses have suggested that such capabilities could emerge relatively soon, but the timeline remains uncertain and is a subject of genuine debate. This entry describes a threat to security controls (cryptography), not an insurance coverage trigger, sublimit, or resilience metric; the extent to which resulting losses, whether first-party (such as data restoration) or third-party (such as privacy liability), are covered depends on the specific policy wording, endorsements, exclusions, and jurisdiction, and insurance does not reduce the underlying likelihood of cryptographic compromise.

Why it matters

Quantum computing risk matters because a large share of the world's sensitive data is protected by public-key cryptography that was long considered secure for decades. A sufficiently powerful, cryptographically relevant quantum computer could break these algorithms, and the primary consequence would be sensitive data being lost or compromised, an impact with wide-reaching effects across industries. For organizations that hold long-lived confidential information, the concern is not only future data but data protected today, because information intercepted now could be exposed once decryption becomes feasible.

The timeline for this threat is genuinely uncertain and a subject of active debate among researchers. Some analyses have suggested that quantum computers could crack widely used security keys before the decade is over, while others regard practical, cryptographically relevant machines as further off. This uncertainty is itself part of the risk: organizations must make decisions about cryptographic migration and data-protection strategy without a settled forecast of when the capability will arrive.

It is important to keep this concern in its proper category. Quantum computing risk is a threat to a security control, cryptography, not an insurance coverage trigger, sublimit, or resilience metric. Insurance does not reduce the likelihood that cryptography is broken; it can at most transfer some financial consequences, and only to the extent specific policy wording, endorsements, exclusions, and jurisdiction allow. Whether resulting losses, whether first-party such as data restoration or third-party such as privacy liability, are covered depends entirely on the policy in question and cannot be assumed.

Who it's relevant to

Chief information security officers and security architects

CISOs and security teams own the cryptographic controls most directly threatened. They are responsible for inventorying where vulnerable public-key cryptography is deployed, prioritizing systems that protect long-lived sensitive data, and planning migration strategies. This is a risk-mitigation activity aimed at reducing the underlying likelihood of compromise, distinct from, and not replaced by, any insurance the organization may carry.

Underwriters and insurance brokers

Underwriters and brokers need to understand quantum computing risk as an emerging security threat that could affect the confidentiality and integrity of insured organizations' data. Because this is not itself a coverage term, its treatment in any policy depends on specific wording, endorsements, and exclusions. Whether losses stemming from a future cryptographic compromise, first-party or third-party, would fall within cover is unsettled and subject to the individual form and jurisdiction.

Risk managers and compliance professionals

Risk managers must weigh quantum computing risk against a genuinely uncertain and debated timeline, deciding how to balance mitigation, acceptance, and any risk transfer. Compliance professionals should track how regulators and standards bodies may come to treat cryptographic readiness, recognizing that requirements and definitions can differ across regimes and are still evolving.

Resilience and continuity planners

Planners should treat quantum computing risk as a scenario that could affect the confidentiality of protected data and the trustworthiness of security controls, informing longer-term resilience and data-protection planning. It is a technology threat rather than a resilience metric such as RTO or RPO, and addressing it complements, rather than substitutes for, continuity and recovery capabilities.

Inside Quantum Computing Risk

Harvest-now-decrypt-later exposure

The risk that encrypted data intercepted or exfiltrated today could be stored by an adversary and decrypted later once cryptographically relevant quantum computing becomes available. This is a first-party data confidentiality concern; whether resulting losses would be covered depends on policy wording, exclusions, and when the loss is deemed to occur, which is unsettled given the potential gap between the original data theft and any future decryption.

Cryptographic obsolescence

The prospective weakening of widely used public-key cryptography (such as algorithms relying on integer factorization or discrete logarithms) if sufficiently capable quantum computers emerge. This is a security and technology concept, not a coverage trigger; its insurance relevance arises only through downstream incidents such as data breaches or fraud that a policy may or may not respond to under its specific terms.

Post-quantum cryptography (PQC) migration

The process of transitioning systems to cryptographic algorithms believed to resist quantum attacks. This is a risk mitigation activity, not risk transfer; it addresses likelihood and severity of future cryptographic failure but does not by itself constitute insurance coverage or a resilience guarantee.

Cryptographic inventory and agility

The practice of cataloging where and how cryptography is used across an organization and building the ability to swap algorithms with minimal disruption. This is a security governance and resilience capability that supports migration planning; it is distinct from any policy term and does not by itself determine coverage.

Underwriting and accumulation risk

The insurer-side concern that a broad cryptographic break could affect many insureds simultaneously, creating correlated or systemic losses. This is an insurance market and portfolio concept relevant to capacity, sublimits, exclusions, and pricing, rather than a resilience metric for any individual organization.

Coverage uncertainty and exclusionary language

The unresolved question of how existing cyber policies would respond to quantum-enabled incidents, including how loss timing, causation, and any infrastructure, war, or failure-to-maintain-standards exclusions might apply. Outcomes are subject to the specific wording, endorsements, conditions precedent, and jurisdiction; no standard treatment should be assumed.

Common questions

Answers to the questions practitioners most commonly ask about Quantum Computing Risk.

Does a cyber policy today specifically cover losses caused by quantum computing attacks?

Not as a distinct category in most current forms. Quantum computing risk is not typically named as a separate coverage grant, exclusion, or trigger. Whether a loss involving cryptographic compromise would respond depends on the specific policy wording, applicable exclusions, and how the loss is characterized (for example, as a data breach, network security failure, or business interruption). Because insurer forms and endorsements vary and this is an evolving area, you should not assume either coverage or exclusion without reading the specific contract and, where needed, obtaining a coverage opinion.

Is buying cyber insurance a substitute for preparing my cryptography for quantum-related threats?

No. Insurance is a risk-transfer mechanism that may help finance certain losses after an event; it does not reduce the likelihood that cryptographic protections are compromised and does not itself migrate your systems to more resilient algorithms. Preparedness activities such as inventorying cryptographic assets and planning algorithm transitions are risk-mitigation measures. The two are complementary but distinct, and insurers increasingly weigh an organization's security posture when underwriting rather than treating coverage as a replacement for controls.

How should we begin assessing our exposure to quantum computing risk?

A common starting point is building a cryptographic inventory: identifying where and how encryption and digital signatures are used across systems, data at rest, data in transit, and third-party dependencies. This is a resilience and security exercise rather than an insurance one. Understanding which assets rely on cryptography most sensitive to future compromise helps prioritize migration planning and informs conversations with brokers about how existing coverages might respond, subject to the specific wording.

What is the concept of 'harvest now, decrypt later,' and why does it matter for planning?

It refers to the possibility that data intercepted or stored today could be decrypted in the future if the protecting cryptography becomes vulnerable. This matters most for data with long confidentiality lifespans, because a present-day interception could result in a future disclosure. For planning, it shifts attention to data retention practices and the sensitivity horizon of information, and it complicates loss timing questions for insurance, since the interception and the eventual disclosure may occur in different policy periods.

How does quantum computing risk relate to our RTO and RPO planning?

Recovery time objective and recovery point objective are resilience metrics addressing how quickly operations resume and how much data loss is tolerable after a disruption; they are distinct from cryptographic risk and from any insurance coverage trigger. Quantum-related concerns are primarily about confidentiality and integrity of protected data and communications rather than availability recovery. That said, a scenario forcing rapid re-encryption or system changes could carry operational impacts, so continuity and disaster recovery plans may warrant review, but do not treat cryptographic migration as an RTO or RPO parameter.

What should we ask our broker or underwriter about quantum computing risk at renewal?

Useful lines of inquiry include how the current form treats cryptographic failure or compromise, whether any exclusions (such as those addressing infrastructure or failure to maintain security standards) could apply to such scenarios, how loss timing would be handled for events spanning multiple policy periods, and whether the insurer expects specific cryptographic controls as underwriting conditions. Frame these as questions about existing wording rather than assuming dedicated quantum coverage exists, and document responses, since interpretations vary among underwriters and brokers.

Common misconceptions

Quantum computing risk is a distant, purely future problem, so nothing needs to happen now.

Even if cryptographically relevant quantum computing is not yet available, the harvest-now-decrypt-later dynamic means data with a long confidentiality lifespan can be exposed by activity occurring today, which can inform present-day mitigation and inventory decisions.

A cyber insurance policy will cover losses from a future cryptographic break the same way it covers a data breach today.

Whether such losses are covered is genuinely uncertain and depends on the specific policy wording, the timing of when a loss is deemed to occur, causation, and applicable exclusions. Insurance transfers financial consequences under defined terms; it does not reduce the likelihood of a cryptographic failure or substitute for migration and other controls.

Adopting post-quantum cryptography makes an organization resilient to quantum risk.

PQC migration is a mitigation measure addressing one specific exposure. It is not the same as business continuity, disaster recovery, or insurance, and it does not by itself establish organizational resilience; it should be one element within broader continuity, incident response, and risk-transfer planning.

Best practices

Build and maintain a cryptographic inventory identifying where public-key cryptography is used and which data assets have long confidentiality requirements most exposed to harvest-now-decrypt-later risk.

Prioritize cryptographic agility so algorithms can be replaced with minimal disruption, treating this as risk mitigation distinct from and complementary to any insurance arrangement.

Engage brokers and underwriters early to clarify, in writing, how current policy wording, loss-timing provisions, and exclusions might apply to quantum-enabled incidents rather than assuming standard coverage.

Sequence post-quantum cryptography migration by data sensitivity and retention lifespan, focusing first on information whose value persists long enough to be decrypted in the future.

Integrate quantum-related scenarios into incident response and business continuity planning, keeping RTO/RPO objectives, disaster recovery, and crisis management responsibilities clearly delineated.

Avoid treating insurance as a substitute for controls; document risk-transfer, mitigation, acceptance, and avoidance decisions separately so gaps in coverage and residual risk are visible to governance stakeholders.