GUIDE · MANUFACTURING OT

OT and ICS security: a guide to protecting production plants

After this guide you will know what OT and ICS are, why a production plant requires different rules from the office, which are the most common risks and in what order to tackle the topics for further study. The aim is to decide where to start without stopping production.

Updated october 2026
10 min read
Altovar Technical Editorial Team

1. What we mean by OT and ICS

OT, operational technology, refers to the equipment and programs that control physical processes: production lines, robots, furnaces, pumps, conveyor belts and the ventilation systems of production areas. At the centre are programmable logic controllers, called PLCs, which read sensors and drive actuators in very short cycles. ICS, industrial control systems, is the term used for these industrial control systems as a whole, including operator panels and supervisory systems known as SCADA.

The difference from IT lies in the consequences. A configuration error in the office blocks email or exposes data. In a plant it can stop a line for a long time, spoil a batch or, in the worst cases, put at risk people working near the machines. For this reason OT security is not only about keeping information confidential, but about the correct functioning of the process and the physical safety of people, which in an industrial setting is called safety.

2. Why OT security is not IT security

Many companies apply the same rules to the plant as they do to the office: antivirus, automatic updates, periodic password changes. On many machines these rules do not work as they stand. An update may require stopping the line, and controller software is often approved by the manufacturer only in one specific version. An approach adapted to the lifecycle of plants, which can last many years, is therefore needed.

The table summarises the main differences. It is not a ranking: it shows where priorities change and, consequently, where the measures you choose must change too. Read it as a basis for discussion with your supplier and the production manager, because every plant has exceptions that the table cannot cover, such as a new line next to an old one or a device that no longer receives updates.

AspectOffice (IT)Plant (OT)
Main priorityConfidentiality of dataAvailability and the safety of people
UpdatesFrequent and often automaticScheduled, tested and coordinated with the manufacturer
System lifespanReplaced every few yearsCan last many years, with dated software
RestartAccepted at any timeCostly or risky, to be scheduled
Security scansRoutinely permittedTo be assessed carefully, as they can lock up controllers

3. How a plant is organised

A plant is usually organised in layers. At the base are sensors and actuators, which measure and act on the process. Above them are the PLC controllers, which run the machine's logic. Then there are the SCADA supervisory systems and operator panels, called HMIs, through which staff see and control the line. Higher up are the production management systems, often called MES, and finally the corporate network with the business management systems, known as ERP.

Problems often arise at the points where these layers meet. A management system that reads data from the factory, a technician who connects a laptop to the line, a supplier who logs in remotely: each connection is a door. The most common way to reduce risk is to separate zones and control what passes between them. The reference model known as Purdue, used by many designers, helps to name these layers and to decide where to place the boundaries.

4. The most frequent risks

Many plant problems have simple causes. A sophisticated attack is not needed to stop a line: often a flat network with no boundaries, permanently active remote access or a USB stick passed from one maintenance computer to another is enough. The risk depends not only on the technology but on the habits with which people work on the equipment, and on the exceptions that accumulate over time, when a temporary connection becomes permanent without anyone deciding so.

These are the points worth checking first, because they come up often during site visits. The list is not complete, but it is a good starting point for understanding where you are exposed and which controls are really missing. For each one ask who manages it, how long it has existed and whether anyone has ever verified it in writing. If the answer is silence, the point should be added to those to be clarified as a priority.

  • Flat networks, where the office computer and the line controller can see each other without filters
  • Supplier remote access that is always on, with shared credentials or credentials never changed
  • Devices still using factory default passwords and unnecessary network services left switched on
  • Maintenance computers and removable media used across several plants without controls
  • No backup copies of PLC programs, HMI configurations or machine parameters

5. Updates and continuity: the conflict to manage

The conflict is simple to describe. Security requires vulnerabilities to be fixed quickly; production requires machines to stay stopped as little as possible. The solution lies in maintenance windows scheduled with the manufacturer, testing on a copy of the system or on a spare machine, and a rollback procedure already written down. Where an update is not possible, the risk does not disappear: it must be reduced by other measures.

The most common compensating measures are isolating the device in a separate zone, limiting who can connect to it, controlling the network flows that reach it and keeping verified copies of programs and configurations ready. Each reduces exposure without touching the machine's software. Record in the risk document which devices cannot be updated, with the reason and the person accountable for them.

6. Standards and reference frameworks

There is no single rule that says what to do in every plant. More than one framework may apply at the same time, and the choice depends on the sector, the size and the customers you serve. If your business falls within the scope of the NIS2 directive, transposed in Italy by Legislative Decree 138/2024, you must manage cyber risk in a documented way and report significant incidents, with a first communication within 24 hours and a more detailed notification within 72 hours.

If you manufacture machines or components with software to sell in the European Union, the Cyber Resilience Act may impose requirements on the product. If you are a supplier in the automotive supply chain, TISAX verification is often required by customers. An ISO/IEC 27001 certification may also cover the OT perimeter, provided it is included in the scope. Check with a consultant which combination applies to you.

7. A four-phase path

The work is best tackled in a precise order. If you start with things you do not know, such as supplier access, you risk closing doors without knowing which lines depend on those connections. The following path begins with the inventory, which makes the equipment visible, and goes on to the verification of restores, which shows that the measures really work. Even a small change to the network can have effects on a line that does not seem connected.

Each phase produces a simple document that remains useful afterwards: a list, a network diagram, a list of accesses, a recovery procedure. You do not need a long project to start, but each phase needs an identified owner and a date by which it must be completed. The owner should be chosen from people who really know the subject, not simply from those who have time available.

  1. Inventory the OT equipment: lines, machines, controllers, panels and the suppliers who access them.
  2. Separate the networks and decide which data flows are really needed between the layers.
  3. Regulate maintenance access and remove any that are no longer used.
  4. Save programs and configurations, and test the restore of at least one machine.

8. Topics to explore, in the right order

This guide is an overview of a group of deeper topics. You do not need to read them all at once. It is best to start with the inventory and the separation of networks, because all other choices depend on them. The following topics answer more specific questions on a single theme: read them in the order that matches the phase you are in. Not all topics deserve the same effort: a business with many remote accesses will start with maintenance access, another with many old machines will start with updates. If you already have a supplier that manages your equipment, give it this page and ask which topics it already knows.

  • Layered model and segmentation between the office network and the factory network
  • OT asset inventory and discovery methods in environments that cannot stop
  • Rules for remote access by maintenance staff to machines
  • Updating PLCs and supervisory systems within maintenance windows
  • Backup of PLCs, operator panels and machine configurations
  • Specific technical standard for the security of industrial automation systems
  • Cyber security requirements for machine manufacturers
  • TISAX path for suppliers in the automotive supply chain
  • Cyber security checklist for a production plant

9. How to start

The first action this week is to build a rough list. Take a sheet and mark every line, every controller, every operator panel and every connection to the outside, including modems and support access. It does not need to be complete on the first attempt. What matters is that the production manager and the maintenance manager look at it together, because they are the ones who recognise machines that do not appear in any documents.

Straight after, ask the supplier that manages your machines who accesses them, with which tools and with which credentials. The answers will tell you which parts of your plant are managed and which remain without a clear owner. The IT manager should then confirm that the list matches the real network, without relying on documentation alone. That list of gaps is the point from which to continue with the rest of the path.

Frequently Asked Questions

Are OT and IT the same thing?

No. IT manages information and digital services, OT controls physical processes. The skills overlap, but the priorities differ: in a plant, availability and the safety of people often come before confidentiality. For this reason rules designed for the office must be adapted before they are applied in a factory. Anyone responsible for security in a business should understand both worlds.

Do I need a dedicated OT security team?

It depends on the size and complexity of the plant. In many organisations the work is shared between the IT manager, the production manager and the maintenance supplier, with a single coordinating contact. What matters is being clear about who decides, who carries out the work and who answers for a stoppage. A dedicated role becomes useful when there are many plants or they are highly interconnected.

Can I update a PLC like a computer?

Not in general. The controller is approved by the manufacturer for specific software versions, and an unapproved update can change how the machine behaves. Before any intervention, ask the manufacturer whether the version is supported, read the release notes and test the change on a copy or a test bench. Only then schedule the application window with production.

Is an antivirus on the machines enough?

No. An antivirus can help on support computers, but it is not always compatible with the machine's software and does not replace network separation or access control. On many devices it cannot be installed. The most effective measures limit who can connect and what passes between zones, together with security copies and tested recovery procedures.

Must the maintenance supplier follow these rules?

Yes, and the contract should say so. Ask that access be personal, logged and revoked at the end of each intervention, that the computers used are controlled and that the supplier reports any incidents. Check with a legal adviser how these clauses fit with the supply agreement, because the issue varies with the type of contract and the responsibilities agreed.

Does the NIS2 directive apply to my factory?

It depends on size, sector and activity. Some manufacturing activities fall within the scope, others do not, and the assessment must be made case by case. If you fall within it, a documented management of risks and the reporting of significant incidents are required, with a first communication within 24 hours and a more detailed notification within 72 hours. Consult a consultant before deciding.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →