A production line can be running normally at 08:00 and be at a standstill by 08:15. A ransomware incident, failed network switch, unauthorised remote connection or corrupted controller configuration can all have the same immediate result: equipment cannot do its job. Manufacturing operational technology risks are therefore not just an IT concern. They affect output, quality, safety, delivery commitments and cash flow.
For many manufacturers, operational technology has grown over years rather than being designed as one connected environment. Programmable logic controllers, human-machine interfaces, sensors, industrial PCs, building systems and production databases may sit alongside newer cloud reporting tools and Microsoft 365. That mix supports efficient production, but it also creates dependencies that need to be understood and managed.
Why manufacturing operational technology risks are different
Operational technology, usually shortened to OT, is the technology that monitors or controls physical processes. In a factory, that may include machinery controls, packaging lines, supervisory control systems, environmental monitoring, robotics and access systems. IT generally handles business information, communication and administration. OT keeps the process moving.
The distinction matters because the consequences are different. A disruption to an office application is frustrating. A disruption to a production line may halt work in progress, create scrap, delay lorry collections or leave equipment in an unsafe state. Restoring systems quickly matters, but restoring them incorrectly can make matters worse.
OT also has a different operating life. A controller or machine interface may remain in service for 10, 15 or 20 years, often because replacing it would require capital expenditure and planned downtime. It may use older operating systems, proprietary software or protocols that were never designed for internet-connected environments. Applying a standard IT security control without considering the production process can introduce risk rather than remove it.
That does not mean OT should be isolated from cyber security practice. It means controls must be chosen and implemented with engineering, operations and safety teams involved.
The risks that cause the greatest disruption
Limited visibility of connected assets
You cannot protect equipment effectively if no one has a complete view of what is connected. Manufacturers commonly know their major production assets, but may have less certainty around industrial PCs, engineering laptops, unmanaged switches, wireless access points, remote support devices and supplier-installed gateways.
This uncertainty makes incident response slower. If a vulnerability is identified, the business may not know whether affected equipment is present, connected or essential to a particular line. An accurate asset register should record the device, its location, owner, function, network connection, software or firmware version, and the consequences of taking it offline.
Flat networks and uncontrolled connections
A flat network allows devices to communicate more freely than they need to. It is convenient during setup, but it gives a compromised office computer a potential route towards production systems. Equally, an infected industrial device may be able to reach shared files or business applications.
Network segmentation reduces this exposure by separating business IT, OT environments, guest access and critical services into controlled zones. The goal is not to make communication impossible. It is to permit only the traffic that is needed, between known systems, through monitored routes.
Remote access deserves the same care. Equipment suppliers may need to diagnose faults at short notice, particularly where specialist machinery is involved. That access can be commercially valuable, but permanent, shared or poorly monitored connections create a clear weakness. Use named accounts, multi-factor authentication, time-limited approval and logging. Where practical, provide remote access through a managed route rather than allowing direct connections into the plant network.
Legacy systems and difficult patching
Older systems are not automatically insecure, but they need compensating controls when supported updates are unavailable or patches cannot be applied without disrupting production. The wrong approach is to apply updates blindly. A patch that conflicts with a machine application, driver or controller can lead to unplanned downtime.
A better approach is risk-based patch management. Identify which systems are supported, which can be tested before deployment, and which need alternative protection. Alternatives may include network isolation, restricted user permissions, application allow-listing, endpoint protection where compatible, tighter monitoring and a documented replacement plan.
The key question is not simply, “Is this system patched?” It is, “What would happen if this system were compromised or failed, and what control most safely reduces that risk?”
Ransomware moving from IT into OT
Most ransomware incidents start with ordinary business routes: phishing, stolen credentials, unpatched internet-facing systems or insecure remote access. Once inside, attackers look for valuable data, administrator accounts and accessible backups. If IT and OT are connected without effective boundaries, disruption can spread to production.
The impact is not limited to encrypted files. Operators may lose visibility of a process, engineering teams may be unable to retrieve configurations, and production planning may have no reliable record of material, batch or quality status. Even where machinery remains physically capable of running, it may not be safe or commercially sensible to continue without the systems around it.
Backups are essential, but they must be usable. Manufacturers should hold protected copies of critical server data, machine configurations, controller programs and engineering documentation. Recovery should be tested against realistic downtime objectives. A backup that takes days to locate, validate and restore does not meet the needs of a line that must restart within hours.
Supplier and human risk
Factories depend on people who understand how equipment works. That knowledge is valuable, but it can be concentrated in a few experienced engineers, a specialist supplier or an individual with long-standing access. Shared accounts, undocumented changes and informal workarounds make recovery and accountability harder.
Clear access rules should not prevent engineers from doing urgent work. They should make it possible to see who changed what, when and why. Maintain current diagrams, configuration records and operating procedures. When a supplier relationship changes, review access immediately rather than assuming old accounts will no longer work.
How to reduce operational technology risk without disrupting production
A practical programme starts with the production process, not a generic cyber security checklist. Identify the systems that are essential to safety, quality and output. Establish the maximum acceptable downtime for each area, the people who can make decisions during an incident, and the dependencies that must be restored first.
From there, prioritise a small number of controls that materially improve resilience. For most small and mid-sized manufacturers, the following areas provide the strongest foundation:
- Maintain a verified inventory of OT-connected assets, software, configurations and owners.
- Separate IT and OT networks, with documented and restricted connections between them.
- Control remote access using named accounts, multi-factor authentication, approval and audit logs.
- Protect and test backups for business systems and production-critical configurations.
- Build an incident response plan that includes operations, engineering, IT, senior management and key suppliers.
These controls need to fit the site. A highly automated plant, a food production environment and a small fabrication workshop will have different risks, budgets and tolerance for change. The right solution is proportionate: strong enough to reduce the most serious exposure, but designed around uptime and safe working.
Build incident response around the factory floor
A conventional IT incident plan often focuses on laptops, email and data. A manufacturing plan must answer operational questions too. Who can authorise a controlled shutdown? Can the line be operated safely in a degraded mode? Which supplier needs to be contacted first? Where are the latest controller backups held? How will staff communicate if email or Teams is unavailable?
Run through these questions before an incident. A short tabletop exercise with production, engineering, IT and management can expose unclear responsibilities quickly. It also helps avoid the damaging assumption that someone else has the information or authority needed to act.
Monitoring supports this work. It should provide useful evidence of unusual connections, failed authentication attempts, changes to critical configurations and network faults, without overwhelming teams with alerts that no one can investigate. For smaller organisations, managed monitoring and external expertise can provide a practical route to better coverage, provided the service understands the importance of production continuity.
Treat OT resilience as an operational investment
Security improvements can appear difficult to justify when machinery needs attention, orders are demanding and production time is limited. Yet the cost of an uncontrolled outage is rarely limited to the initial repair. It can include lost production, overtime, missed delivery dates, wasted materials, reputational damage and difficult conversations with customers.
The most effective manufacturers treat OT resilience as part of operational reliability. They make sensible changes during planned maintenance, test recovery before it is needed and keep the information required to make decisions under pressure. With a clear view of the environment and a proportionate plan, technology can support the factory rather than become another source of uncertainty.

