Knowledge

ICS cybersecurity: where to start

Controllers, machine tools, pumps and sensors stay in service for decades and are often never updated. They were built for closed networks, but today they are connected to the office and the internet. Here is a plan to start with, without stopping production.

Updated 20 October 2026 · CUBRA security team

Why industrial networks are vulnerable

  • Equipment cannot simply be updated: that means stopping the line and testing it all over again.
  • Equipment protocols were designed without checking who sends a command.
  • The office network and the shop floor are often connected directly, so an infected email in the accounts department can reach the machines.
  • Contractors connect remotely, and forgotten open access lives on for years.

Step 1. Know what you have

You cannot protect what you do not know about. Make an inventory of the devices on the shop floor: what each one is, which firmware it runs and what it talks to. Part of the work is automatic – the security gateway finds devices on the network and compares their firmware against known vulnerabilities.

Step 2. Separate the shop floor from the office

Between the office network and production there should be a gateway that lets through only what is needed. From outside there should be no path to the equipment at all: it cannot be seen from the internet, whatever vulnerabilities it may have.

Step 3. Divide production into segments

Inside production, the network should also be divided: lines, warehouse, power, building systems. Segments cannot see each other, and a compromised device in one of them will not become a way into the others.

Step 4. Contractors only through a secure channel

Service companies should come in through a separate secure channel. Access is opened for the duration of the work, closes by itself, and every sign-in is logged.

Step 5. Control commands

The greatest danger is not data theft but a foreign command to the equipment: a new program for all machines at night, disabling emergency protection, changing dosing. A gateway that understands equipment protocols lets routine commands through and holds dangerous ones, raising an alarm for the person responsible.

Step 6. Communication for incidents

When something happens, dispatchers and the security team need communication that does not depend on the network under attack. A secure messenger on a separate node or communication without the internet lets them coordinate even when the office network is down.

Common mistakes at the start

  • Starting with expensive detection systems without knowing which devices are on the shop floor.
  • Leaving a direct path from the office to the equipment “for convenience”.
  • Giving contractors permanent remote access.
  • Writing rules without the process engineers – and blocking a needed command in the middle of a shift.

A step-by-step plan gives the best result: first the inventory and separation, then segments and contractor access, then command control.

How CUBRA helps

CUBRA Node sits between the office and the shop floor without stopping the lines: it hides equipment from the internet, divides the network into segments, lets contractors in only through a secure channel, inspects equipment commands and holds dangerous ones. CUBRA Shield modules add intrusion prevention, and CUBRA Messenger provides team communication during an incident (equipment command filter — after release).

FAQ

Can ICS be protected without stopping production?

Yes. The gateway is installed between the office and the shop floor during a planned maintenance window or without a break, and the equipment itself is not changed. Command rules are agreed with the process engineers in advance.

Is it enough to disconnect the shop floor from the internet?

That is not enough: malware also gets in via USB sticks, contractors’ laptops and the office network. You need segments, control over contractor access and command checks.

Who should be responsible for cybersecurity in production?

Ideally the IT department together with the chief process engineer or chief power engineer. IT knows the networks; the engineers know which equipment commands are normal and which are dangerous.