# Quantum will attack your assumptions

> “We know where our cryptography is used.” “Encrypted means secure.” The assumptions post-quantum risk may break, and what to verify instead.

Source page: https://netsenx.com/en/blog/2026-11-17_quantum-attacks-assumptions · NetSenX Team · 2026-11-17

Quantum will not attack your firewall. It will attack your assumptions.

The most dangerous scenario does not begin with a red alert.

The firewall is working. Systems are available. Backups have completed. Certificates have not expired. The security report looks reassuring. The board sees a green dashboard and is told that everything remains under control.

Yet the company may already have lost a clear understanding of what actually protects its data.

That is the real essence of quantum risk.

It is not only about the moment when a sufficiently advanced quantum computer threatens parts of the cryptography used today. It is about all the assumptions organisations have built around that cryptography.

We assume that an encrypted connection is secure. We assume that a supplier knows how our data is protected. We assume that a valid certificate represents trust. We assume that the system inventory is current. We assume that we can see every place where artificial intelligence is operating. We assume that there will be enough time to migrate.

What if those assumptions are the weakest layer of protection?

## Your firewall can work perfectly and still fail to show the truth

A firewall answers important questions. Who is trying to connect, which traffic should be allowed, which traffic should be blocked and which rules have been violated.

It does not automatically answer whether the company understands the full context of the connection.

An approved supplier may use a legitimate account. An AI agent may communicate with an authorised service. An encrypted transfer may pass through a recognised cloud platform. A certificate may be technically valid.

Every individual element appears correct.

Risk emerges when we examine the relationships between them.

Why did the supplier connect at an unusual time? Why did a technical account begin reaching a system it had never used before? Why did an AI agent retrieve far more data than the task required? Why has encrypted traffic been gradually increasing for several weeks? Why did the communication route or the cryptographic negotiation suddenly change?

A conventional security tool may treat each event separately.

Mature visibility should connect them into one coherent story.

Would your board receive that story, or merely a statement that no critical incident had been detected?

## Quantum does not need to break everything to change the rules

Public debate about quantum technology is often presented in extremes.

On one side are predictions that all cryptography will suddenly collapse. On the other is the argument that quantum remains too immature for businesses to take it seriously.

Both narratives oversimplify the problem.

Future quantum computers do not need to invalidate every security mechanism. The greatest pressure concerns parts of public key cryptography that support key exchange, digital signatures, authentication, certificates, secure updates and trust between systems.

This is why the United States National Institute of Standards and Technology published the first three final post-quantum cryptography standards and encouraged organisations to begin migration planning.

This is no longer only a research topic concerning hypothetical future algorithms. Standards are available. The larger challenge is introducing them into complex environments that must continue operating throughout the transition.

The key question is no longer whether quantum will eventually change cryptography.

The question is whether the company knows where cryptography is being used today and which business processes could fail if it had to be replaced.

## The first assumption that may collapse

## We know where our cryptography is used

Most organisations know that they use encryption.

Far fewer can identify every algorithm, certificate, key, library, protocol, device and supplier service involved.

Cryptography is not located in one system managed by one team. It exists in applications, cloud infrastructure, private networks, devices, software code, backups, update mechanisms, software signatures, application programming interfaces, identity services and communication with suppliers.

Some of it was deployed years ago. Some arrived with a new cloud service. Some is controlled by a vendor. Some may be embedded in a legacy system created by people who no longer work for the organisation.

Cryptographic discovery and inventory are among the first foundations of migration. An organisation must understand where cryptography exists, how it is used and which systems and information it protects.

Without that knowledge, it is impossible to establish a credible migration order.

Does your company maintain a living picture of its cryptography, or a spreadsheet updated before an audit?

And what has changed in the environment since that spreadsheet was last reviewed?

## The second assumption that may collapse

## Encrypted means secure

The padlock icon feels reassuring.

The connection is encrypted. The certificate is valid. The protocol has been approved. The traffic cannot be read by a casual observer.

But this does not mean the entire interaction is secure in its business context.

Encryption does not tell us whether the correct party received the data. It does not explain whether an AI agent should have been able to access a document. It does not reveal that a supplier is transferring significantly more information than before. It does not prove that the cryptography will remain appropriate throughout the full lifetime of the data.

An encrypted channel can protect legitimate communication.

It can also protect an unwanted transfer from being noticed by the data owner.

Organisations need more than confirmation that traffic is encrypted. They should understand who is communicating with whom, for what purpose, how often, under which protection and whether that behaviour remains consistent with the historical pattern.

Otherwise, encryption may protect information from interception while simultaneously hiding its loss from the company itself.

Can your organisation distinguish between a secure connection and a securely concealed problem?

## The third assumption that may collapse

## We still have plenty of time

We do not know the exact date when a quantum computer may become capable of threatening widely used public key cryptography.

That is true.

But uncertainty about timing does not make delay safe.

The United Kingdom’s National Cyber Security Centre has outlined migration stages that include completing discovery and initial planning by 2028, carrying out the highest priority migrations by 2031 and completing the transition by 2035.

The European roadmap expects a coordinated transition to post-quantum cryptography to begin by the end of 2026. Critical infrastructure should move as early as possible and no later than the end of 2030.

These timelines were not created because anyone knows the date of a breakthrough.

They exist because discovery, dependency analysis, product modernisation, supplier coordination, interoperability testing and cryptographic replacement take years.

Would a board consider a transformation lasting close to a decade to be something that can safely be postponed for several more years?

## The fourth assumption that may collapse

## Data captured today is only a problem today

Some information loses its value very quickly.

Other information remains strategic for decades.

Research documentation, intellectual property, product designs, medical information, contracts, investment strategies, infrastructure data, ownership structures and board communications may remain valuable long after the original project has ended.

Encrypted data can be intercepted today, stored and targeted for future decryption.

This does not mean that every organisation is currently the target of a state-sponsored intelligence operation.

It means that information security cannot be assessed solely against the threats that exist on the day the information is sent.

Two periods must be compared.

How long the information needs to remain confidential and how long the organisation can reasonably trust the mechanism protecting it.

Does your organisation classify information according to its future value as well as its present sensitivity?

Which information held today could damage the company, its customers or even national interests if it were exposed in 2035?

## The fifth assumption that may collapse

## Suppliers will solve the problem for us

A large part of corporate cryptography exists inside products and services the organisation did not build.

Cloud platforms, business systems, network equipment, applications, communication platforms and external services will migrate according to the schedules of their manufacturers.

This creates a dependency that cannot be removed by a board decision alone.

A supplier may claim to be preparing for post-quantum migration. The customer still needs to understand which business processes depend on that supplier, which information flows through its systems, how access is being used and whether observed activity remains consistent with expectations.

Supplier declarations are important.

Observed reality is more important.

Does the company know which external partner would be hardest to replace?

Can it demonstrate how that partner actually uses its access, or does it know only what the contract says the supplier is allowed to do?

## The sixth assumption that may collapse

## AI is a separate subject

AI and quantum still appear in separate presentations.

AI sits in the innovation strategy. Quantum appears in a future technology report. Cybersecurity belongs to the information technology team. Supplier risk remains with procurement. Cryptography sits somewhere between architecture and compliance.

In the real environment, all these areas already meet.

An AI agent may use a technical account, retrieve documents, communicate with an external model and trigger a process inside a supplier’s system. Every step creates a connection, a permission, a data flow and a cryptographic dependency.

On paper, the organisation introduced a productivity tool.

In practice, it may have created an entirely new route through which information can leave the controlled environment.

Did anyone see that route appear?

Does the organisation know which model processes the information, in which jurisdiction and under which permissions? Can the agent’s behaviour be compared with its normal pattern? Can the company reconstruct a month later which information the agent received and which actions it performed?

AI can increase productivity.

It can also multiply invisibility.

Quantum does not create this problem. It increases the possibility that the consequences of lost control may survive far longer than the AI tool that caused them.

## The answer is not another thousand alerts

Companies already possess enormous volumes of security signals.

The problem is that those signals are distributed across different systems.

One tool sees the device. Another sees the login. A third monitors the cloud. Another tracks certificates. Separate processes manage incidents, suppliers and AI activity.

Yet risk often exists between those points.

Organisations therefore need a connected picture of the real behaviour of their digital environment.

Which devices communicate with each other. Where data travels. Where AI is being used. How suppliers behave. Which technical accounts and non-human identities take action. Which certificates, keys and protocols protect communication. When behaviour departs from its normal pattern.

Detecting a deviation is still not enough.

Leadership should receive an explanation of why the change matters, which information was involved, which systems create the dependency and whether the event can later be reconstructed from evidence.

That is the difference between an alert and understanding.

Between a dashboard and control.

Between knowing that something happened and being able to prove what actually happened.

## Quantum will attack the static picture of the company

One of the most dangerous assumptions is this.

Our documentation accurately describes our environment.

In reality, documentation describes the environment at the moment it was created.

Since then, someone may have deployed a new service. A supplier may have changed its infrastructure. An employee may have introduced an AI tool. A certificate may have been replaced. An account may have received new permissions. Data may have started travelling along a different route.

That is why inventory cannot remain a one-time project.

It must become an ongoing process of observing change.

This applies to devices, connections, suppliers, AI, technical identities and cryptography. The organisation needs a current picture, not a historical sense of order.

Post-quantum migration also requires the ability to replace algorithms, protocols and components without causing uncontrolled disruption to the business.

This capability is often described as cryptographic agility.

A future-ready company is therefore not simply one that has deployed a new algorithm.

It is an organisation capable of discovering cryptography, understanding dependencies, measuring change and moving safely between different solutions.

## The board does not need to understand quantum physics

A CEO does not need to understand the structure of a qubit or the mathematics behind Shor’s algorithm.

The board should, however, be able to ask several questions that determine the quality of the organisation’s preparation.

Do we know which information requires the longest protection?

Do we have a current map of cryptography, suppliers and dependencies?

Can we see actual information flows rather than only the architecture described in documentation?

Can we identify Shadow AI and agents operating outside their expected profile?

Do we know which systems will be hardest to migrate?

Can we reconstruct a complete incident and support our explanation with evidence?

Governments, alliances and security institutions increasingly treat quantum as part of resilience, strategic advantage and long-term information protection.

If national institutions consider this a strategic issue, can companies continue treating it solely as a technical problem for the IT department?

## The most important decision begins with an uncomfortable question

Quantum is unlikely to arrive inside the company as one clearly defined incident.

It will first expose that the organisation did not know its own cryptography. That it trusted static documentation. That it assessed suppliers through questionnaires. That it treated AI as a productivity tool without observing the data paths it created. That it possessed thousands of alerts but could not connect them into evidence.

This does not mean that every company should immediately replace all of its systems.

It means every company should already know where it would need to begin.

The best first step is not buying the most fashionable quantum product.

It is building a truthful picture of the organisation’s environment.

A picture that connects data, networks, suppliers, AI, cryptography, behaviour and evidence.

Does your organisation have that picture?

Or does it simply assume that it does?

That question may be more important today than predicting the date of a quantum breakthrough.

## Quantum will not attack your firewall

It will attack the belief that you know every connection.

It will attack the belief that encryption always means security.

It will attack the belief that suppliers will solve the problem on your behalf.

It will attack the belief that AI belongs in a separate category.

It will attack the belief that documentation represents current reality.

It will attack the belief that the organisation will have enough time.

The most dangerous assumptions are those that have never been tested.

Which security assumption is currently the most dangerous in large organisations?

Should boards already treat cryptographic visibility, AI oversight and supplier activity as one strategic area?

Should post-quantum preparation begin with new algorithms, or with discovering what the company still cannot see?

Where is the greatest weakness today? In technology, internal processes, suppliers, or in the board’s belief that someone else already has everything under control?

Please pass this article to someone responsible for strategy, cybersecurity, artificial intelligence or operational resilience.

Not to begin with a product presentation.

First, it is worth establishing what the company genuinely cannot see.

**Further reading:** [what NetSenX detects and how each alert explains itself](/en/features), [how NetSenX supports NIS2, GDPR and the AI Act](/en/compliance) and [the NetSenX plans and prices](/en/pricing).

---

*Written by the NetSenX Team at TriStiX S.L. Questions: [info@netsenx.com](mailto:info@netsenx.com).*
