Blog: BORIS for SolidWorks - Secure Your CAD Designs

AXA XL Warns a Cyberattack Can Stop Your Factory Without Touching a Machine: What It Means for SOLIDWORKS Teams, PDM Vaults and Cyber Insurance | SolidWorks | Register and Certify IP of CAD design

2026-11-20 14:22 News
On 19 November 2026, the insurer AXA XL published a report warning that a cyberattack can stop a factory without ever touching a machine. The report, "Operational Resilience: Managing cyber risk when digital systems meet physical processes", was produced with expert input from Deloitte and DeNexus. It says the loss, compromise or even suspected compromise of connected IT systems can be enough to halt production, and that the costs can land on several insurance policies at once.
The report is written for operations, risk and business leaders in manufacturing, energy, water, transport and logistics. It is not about SOLIDWORKS. But it names things every SOLIDWORKS team will recognise: engineers' accounts, engineering workstations that configure equipment, remote maintenance by suppliers, and the configuration files, software versions and engineering documentation a company needs to restart safely after an attack.
The same week showed how quickly this becomes real. On 17 November 2026, the Norwegian energy company Equinor said it had detected an ongoing cyberattack against certain IT systems. On 20 November it said the attack had been stopped, that production was running as normal and that there was no indication that data had been stolen or altered. This article explains what the AXA XL report says, why design and manufacturing data sit at the centre of it, and what SOLIDWORKS teams can do now.
TL;DR: your machines can be fine and your factory can still stop

AXA XL's report, published on 19 November 2026, says production can halt when the IT systems, identities, suppliers or data behind it are lost or cannot be trusted, even if no machine is attacked. It cites a SANS 2025 survey in which only 12% of industrial respondents had full visibility of how an attack could move from IT to physical processes, and one in five said full remediation takes more than a month. Costs may touch cyber, property, business interruption, equipment breakdown, environmental, casualty or liability cover, depending on the facts and policy terms. For SOLIDWORKS teams, the message is practical: know which CAD, PDM, licence and CAM systems production depends on, control supplier access, keep clean and trusted copies of drawings and programs, and decide in advance who can stop and restart work.

What does the AXA XL report say?

According to the AXA XL press release of 19 November 2026, the report looks at operational technology (OT), the systems that control physical processes such as production lines, utilities and building systems. Its core point is that these systems now depend on a much wider footprint: cloud platforms, enterprise applications, remote access, shared identity services, virtualization, external suppliers and links between sites. Each of those connections is useful, and each is another route by which disruption can reach production.
The executive summary lists five developments:
  • Cyber risks are becoming physical. An incident does not need to compromise machinery. The loss, compromise or suspected compromise of connected IT systems can be enough to halt production.
  • Resilience depends on operational context. Leaders need to know which systems are vulnerable, what they control, what depends on them and how a process could be run or restored safely.
  • Connectivity extends the path to disruption. Cloud services, remote access, shared identities and suppliers all create routes towards critical processes.
  • OT changes the risk calculation. Equipment runs for decades, has strict safety requirements and short maintenance windows, so IT security controls cannot simply be copied across.
  • Consequences go beyond cyber. Lost output, wasted materials, missed customer commitments and supply chain disruption can follow, and in severe cases injury or environmental harm.
Jonathan Salter, Head of Risk Consulting at AXA XL, summed it up in the press release: "A business can have functioning machinery and still be unable to produce, deliver or operate safely because of a cyber attack on the operational technology that controls that machinery."

What evidence does the report give?

The report draws on public surveys and two anonymised case studies:
  • Visibility is low. In the SANS 2025 ICS/OT survey, only 12% of respondents had full visibility of how an attack could progress from an initial IT compromise to controllers and physical processes.
  • Recovery is slow. One in five respondents in the same survey said full remediation takes more than a month, because teams may need to validate controller logic, inspect equipment and restart machinery in a safe sequence.
  • Ransomware groups are multiplying. Citing Dragos, the report says 119 ransomware groups affected more than 3,300 industrial organisations in 2025, an increase of almost 50% in active groups, and that Dragos saw significant operational disruption in every OT ransomware case its incident response team handled.
  • Case study one. A cyber incident disrupted critical IT systems at a major manufacturer, which paused production across multiple sites. Operations came back gradually after an extended period of downtime, and companies in its supply chain felt the effects. Machinery and control systems were not directly compromised.
  • Case study two. A ransomware attack hit parts of the corporate network of a major industrial services company. Critical operational systems were not directly compromised, but several activities were restricted while the company investigated, and operations were restored over the following days.
The report does not name either company. The pattern will be familiar to readers of our article on the Kinnarps cyberattack, where the Swedish furniture maker shut down systems and stopped three factories to contain an attack, and of our report on ransomware groups listing CAD drawings as loot.

Why does this matter for SOLIDWORKS teams?

Most SOLIDWORKS users never touch a controller. But the systems they run are often what the shop floor depends on. The report gives an example that could have been written about an engineering department: "A little-known engineering workstation, for example, may be critical if it is used to configure equipment across several sites."
In a typical SOLIDWORKS company, production depends on:
  • Released drawings and models in SOLIDWORKS PDM or on a file server, which purchasing, quality and the shop floor use every day.
  • CAM and CNC programs generated from those models and sent to machines over the network.
  • A SolidNetWork licence server or online licensing, without which nobody can open or change a design.
  • The PDM database server and archive server, often virtual machines on one host, as we explained in our article on attackers wiping ESXi hosts behind a firewall.
  • Remote access for resellers, IT providers and suppliers, the route the report singles out as a way in.
If any of these is locked, offline or no longer trusted, a factory with perfectly healthy machines may not be able to build the next order. And the report makes a point engineers should take seriously: when an engineer's account is compromised, "instructions and system changes" can no longer be trusted. For a design team, that means drawings, models and programs. If you cannot show which version of a file is the real one, you may have to stop and check everything.

Which insurance policy pays when production stops?

This is the part of the report most aimed at insurers and brokers, and it matters for small manufacturers too. The report says the costs of an OT incident "may touch cyber, property, business interruption, equipment breakdown, environmental, casualty or liability policies, depending on the circumstances and the terms of cover". It adds that a shutdown taken as a precaution may raise different questions from physical damage caused by malicious manipulation.
In other words, if you shut down your own systems to contain an attack, as Kinnarps did, do not assume your policy treats that the same way as a fire or a broken machine. AXA XL's own disclaimer says no specific coverage should be assumed and that each case depends on the policy and the facts. Three questions are worth asking your broker before anything happens:
  • Does our cyber policy cover business interruption when we shut down systems ourselves as a precaution, with no physical damage?
  • Does our property or business interruption policy exclude losses caused by a cyber incident?
  • What evidence will the insurer want to see about our systems, backups and recovery steps, and do we have it?
For the IP side of insurance, see our guide to IP insurance for CAD design companies.

Which SOLIDWORKS systems can stop production?

Use this table to map the report's dependencies to the systems a SOLIDWORKS team usually runs.
Dependency in the reportSOLIDWORKS equivalentWhat to prepare
Engineer's account compromisedWindows, PDM and 3DEXPERIENCE accounts of designersMFA, separate admin accounts, a way to check which file changes are genuine
Control or scheduling platform lockedPDM vault, ERP link, released drawing foldersTested restore of database and archive, read-only copies of released drawings
Engineering workstation that configures equipmentCAM workstation and post-processors, CNC program shareInventory, offline copies of current programs and post-processors
Shared virtualization and identityPDM, SQL and licence servers on one host, one domainSeparate backups, offline or immutable copies, documented rebuild order
Remote maintenance provider breachedReseller, IT provider or PDM partner remote accessOne managed gateway, time-limited access, session logs
Licence and software versionsSolidNetWork licence server, installers, service packsLicence recovery steps, stored installers for the versions you run
Engineering documentation for restartDrawings, BOMs, inspection plans, simulation reportsDated, trusted copies stored outside the main network
Know which version of a design is the real one.

BORIS for SOLIDWORKS registers your CAD files with a blockchain timestamp and a certificate of ownership from inside SOLIDWORKS, so after an incident you can show which version existed, and when, without relying on a server that may have been compromised.

👉 Get BORIS for SOLIDWORKS

What happened at Equinor this week?

Equinor's case shows the other side of the report: an attack on IT that did not stop production. In its news item first published on 17 November 2026 and updated daily, Equinor said it had detected an ongoing attack against certain IT systems, that operations and production were not affected and that authorities were being informed. On 18 November it said this was not a virus attack and that there was no risk of it spreading. On 19 November it said the attack was still ongoing, that it had been reported to the police, and added: "The attack does not appear to be specifically targeting Equinor."
On 20 November, Equinor said the attack had been stopped, that production was running as normal and that there was no indication that data had been stolen or altered. The company has not said who was behind it or how the attackers got in.
Note the phrase "stolen or altered": after an incident, every engineering team must ask whether it can still trust its files. And an attack that does not target you specifically can still reach you, often through VPN flaws, remote management tools or trusted service providers.

What do you need to restart safely?

The report makes a point that is easy to miss: recovery planning must cover more than everyday business data. It lists "configuration files, controller logic, engineering documentation, software versions and access to specialist suppliers" as things that may all be needed to restore a physical process safely, and says their value depends on whether they are protected.
For a SOLIDWORKS team, that means:

What should SOLIDWORKS teams do now?

  1. Map what production needs from engineering. List the drawings, models, programs, servers and licences the shop floor uses every day, and who owns each one.
  2. Find the single points of failure. One CAM workstation, one licence server or one host for PDM, SQL and file storage is exactly what the report warns about.
  3. Control remote and supplier access. One managed route, MFA, access only for the time needed, and logs. See our guide to managing CAD access for external collaborators.
  4. Keep trusted offline copies. Released drawings, CNC programs, post-processors, installers and the PDM database, stored where ransomware cannot reach them.
  5. Decide who can stop and restart. Agree in advance who may isolate PDM or file servers, who approves restarting, and what must be checked first.
  6. Test a restore. Rebuild the vault and licence server from backup at least once a year and time it.
  7. Talk to your broker. Ask how your cyber, property and business interruption policies treat a precautionary shutdown with no physical damage.
  8. Keep dated proof of your designs. Record which versions your team created, and when, so you can tell genuine files from altered ones after an incident.

How does this fit the bigger picture for engineering data?

Across our network this week, the same theme comes up: attackers go after the people, tools and data around the core systems, not only the systems themselves.

Conclusion

AXA XL's report puts into words what manufacturers learned the hard way this year: production can stop because the systems, accounts, suppliers and data behind it are lost or no longer trusted, even when every machine works. The costs can spread across several insurance policies, and a shutdown you choose as a precaution may not be treated like physical damage.
For SOLIDWORKS teams, the response is concrete. Know which engineering systems production depends on, remove single points of failure, control who can get in remotely, keep trusted offline copies of drawings and programs, agree who can stop and restart, and keep dated proof of your designs so you can tell what is genuine when it matters.
Keep proof of your designs that no attack can rewrite.

BORIS for SOLIDWORKS adds blockchain timestamps and certificates of ownership to your CAD files from inside SOLIDWORKS, giving you dated evidence of each design version that does not depend on your servers, your vault or your partners.

👉 Get BORIS for SOLIDWORKS

FAQ: AXA XL's OT resilience report and SOLIDWORKS teams

What did AXA XL publish on 19 November 2026?

A report called "Operational Resilience: Managing cyber risk when digital systems meet physical processes", produced with expert input from Deloitte and DeNexus. It explains how cyber incidents can stop physical operations and how businesses can map dependencies, control access and prepare for safe recovery.

Can a cyberattack stop production without attacking machines?

Yes. The report says the loss, compromise or suspected compromise of connected IT systems can be enough to halt production. Its two case studies describe companies that paused or restricted operations although machinery and control systems were not directly compromised.

Which insurance covers a production stop after a cyberattack?

It depends on the policy terms and the facts. The report says costs may touch cyber, property, business interruption, equipment breakdown, environmental, casualty or liability policies, and that a precautionary shutdown may raise different questions from physical damage. Ask your broker before an incident.

What happened at Equinor?

Equinor said on 17 November 2026 that it had detected an ongoing cyberattack against certain IT systems, and on 20 November that the attack had been stopped. It said production was not affected and that there was no indication data had been stolen or altered. The attacker and entry route were not disclosed.

Why are SOLIDWORKS systems part of OT risk?

Production often depends on released drawings, CAM and CNC programs, PDM servers, licence servers and remote access for suppliers. If those are locked or cannot be trusted, the shop floor may stop even with healthy machines.

How does BORIS for SOLIDWORKS help?

BORIS does not stop attacks or replace backups. It registers your SOLIDWORKS files with blockchain timestamps and certificates of ownership, so you can prove which design version existed, and when, independently of the systems that were attacked.