Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

Why Is Patch Management Difficult in OT?

Patching industrial systems is constrained by vendor validation, safety recertification, rare outage windows, and devices that have no update mechanism at all, so compensating controls do much of the work.

Illustration for the cybersecurity term OT Patch Management
Home / Blog / Cybersecurity Terms / Why Is Patch Management Difficult in OT?
17 November 2026

Why Is Patch Management Difficult in OT?

Why Is Patch Management Difficult in OT?

The honest answer is that most industrial sites patch a minority of their devices, and the ones they skip are frequently the ones running the process. This is not negligence. Patch management in operational technology collides with constraints that simply do not exist in a corporate estate, and a programme that ignores them produces a compliance document rather than a safer plant.

The Five Real Constraints

  1. Vendor validation. Control system suppliers test operating system updates against their own software and publish compatibility lists, often weeks or months behind release. Applying an untested update can void support, and in some contracts it voids warranty cover on the equipment itself.
  2. Outage windows are rare and expensive. A continuous process plant may have one planned turnaround every two to five years. Between them, stopping a controller to update firmware means stopping production, and the cost of an hour is measured in tonnes or megawatt hours.
  3. Safety recertification. Changing software in a safety-instrumented system triggers the management-of-change requirements of IEC 61511, which can mean re-proving the safety function and updating the safety case before the plant restarts.
  4. Devices with no update path. Field instruments, older protection relays, drives, and many sensors have firmware that was never designed to be changed, or that can only be changed by physical replacement of a module.
  5. Unsupported platforms. Engineering workstations running Windows 7 or Windows CE are still common, because the vendor toolchain that programs a fifteen-year-old controller will not run on anything newer.

Vulnerability Scores Mislead Here

A CVSS base score is calculated for a generic internet-facing deployment. Applied to a controller sitting in a segmented cell with no routed path to anything, it overstates risk; applied to a remotely accessible historian, it can understate the consequence, because the metric has no vocabulary for a release of hazardous material. Read the vendor advisory rather than the score. Siemens publishes security advisories on a monthly cycle, Rockwell Automation and Schneider Electric maintain their own notification channels, and CISA republishes industrial advisories with affected model and firmware detail that maps directly onto an OT asset inventory.

Log4Shell, CVE-2021-44228, made the point in December 2021. The library turned up inside historians, manufacturing execution systems, and vendor management platforms far more often than inside controllers, and the organisations that could answer quickly were the ones holding an accurate software inventory rather than the ones with the fastest patching tooling.

Prioritising What You Can Reach

Sort the estate by what is actually patchable and by what a compromise would cost the process:

Compensating Controls Do the Heavy Lifting

Where a device cannot be patched, the risk is managed by making the vulnerability unreachable. In practice that means tight zones and conduits so the vulnerable service is not exposed outside its cell; application allow-listing on engineering workstations; removable media controls; brokered remote access with session recording; and protocol-aware monitoring that will raise an alarm if the vulnerable function is ever exercised. Record each decision as an accepted risk with a named owner and a review date, so the gap is visible to management rather than buried in a scanner report.

What the Regulator Asks

The NCSC’s Cyber Assessment Framework, used to assess operators of essential services under the NIS Regulations 2018, does not demand that every system be patched. Principle B4 asks that vulnerabilities be understood and managed, and an auditor will accept documented compensating controls, a maintained inventory, and evidence of a disciplined decision process more readily than a patch percentage that nobody can substantiate.

At Privia Security, our Cyber Risk Analysis Services help industrial operators build a defensible vulnerability position around the equipment they cannot simply update.

FAQ – Frequently Asked Questions

How Often Should Industrial Systems Be Patched?

Set the cadence per layer rather than per site. Demilitarised zone servers follow a monthly cycle, HMIs and engineering workstations typically quarterly against the vendor compatibility list, and controllers and safety systems only during planned turnarounds. Emergency out-of-cycle patching should be reserved for vulnerabilities that are remotely reachable and actively exploited.

Is It Safe to Patch a PLC at All?

It is routine during a planned outage with the vendor procedure, a verified backup of the application, and a tested rollback. It is not safe to do opportunistically on a running process: a failed firmware update can leave the controller unbootable, and recovering it may require physical access and a replacement module.

What If the Vendor No Longer Supports the Product?

Treat it as an asset lifecycle decision, not a patching problem. Record the end-of-support date, apply compensating controls to make the device unreachable from anywhere an attacker could stand, and put replacement into the capital plan. Regulators are generally tolerant of legacy equipment and intolerant of legacy equipment nobody has a plan for.

Can Virtual Patching Help in OT?

It can, within limits. A protocol-aware firewall or intrusion prevention rule that blocks the specific request pattern used against a known vulnerability buys time until a turnaround. It does not fix the flaw, it depends on the traffic crossing the enforcement point, and it should be documented as a temporary control with a review date.

Related Terms

You May Be Interested In These

What Is a DCSync Attack?

Cybersecurity Terms

17 November 2026

What Is a DCSync Attack?

Read More
What Is SIEM Use Case Management?

Cybersecurity Terms

17 November 2026

What Is SIEM Use Case Management?

Read More
What Is a Trusted Platform Module?

Cybersecurity Terms

17 November 2026

What Is a Trusted Platform Module?

Read More