Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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.
Sort the estate by what is actually patchable and by what a compromise would cost the process:
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.