Industry

Cybersecurity for industrial companies and control systems

Machine tools, robots and lines receive programs over the network. CUBRA keeps the shop floor apart from the office and accepts programs only from your own people.

What can happen

Downtime costs millions

A plant pays the ransom because every hour of downtime costs more.

Ransomware

The shop floor stands still and orders are missed.

Program tampering

The machine produces defective parts or breaks down.

Drawing theft

Design documentation ends up with competitors.

Conveyor stopped

Robots and lines stop.

!
A real case – 2019

Ransomware hit a major aluminium producer – some of its plants switched to manual operation.

Where CUBRA Node goes

CUBRA Node Rack in the plant server room

The CUBRA Node security gateway divides the shop floor, warehouse, cameras and office. Machine tool programs go only through the gateway.

  • CUBRA Node Rack with redundancy
  • Manufacturer service access over our channel
  • Your equipment stays as it is
Internetno access to equipmentService companyonly via our channelCUBRA Nodeplant server roomShop floormachine tools, robotsCNC programsonly through the gatewayWarehousescannersCamerasrecorder onlyOfficestaff PCsSegments cannot see each other: a hacked PC cannot reach the shop floor
What the gateway does

Six levels of protection

Hides it from the internet

There is no way to reach your shop floor, machine tools and warehouse from outside: they cannot be seen from the internet, whatever vulnerabilities they may have.

Splits it into segments

Each group of devices works in its own segment (a separate part of the network): a hacked PC cannot reach the shop floor.

Lets service in only via our channel

The service company gets in through our secure channel. Every login is logged, and access opens for the duration of the work and closes by itself.

Understands the “language of equipment”

CUBRA Node examines the commands equipment receives over the network: each segment gets only the commands it needs, and the gateway holds back the rest (equipment command filter — after release).

Holds back dangerous commands (after release)

A new program for every machine tool at night will not get through silently – the person responsible gets an alarm at once.

Knows every device

CUBRA Node finds all devices, their firmware and known vulnerabilities by itself – and suggests what to do.

Who exactly it is for

Where we help

What is connected and how we handle it
Robots and conveyors

Each workshop is in a separate segment. Robots accept commands only from their own workshop’s control system; there is no path to them from the office or the internet.

Workshop control systems

The control system hands out programs and commands to the robots. We place it in a separate segment; only an engineer can change its settings, over our channel, and every change is recorded in the log.

Equipment manufacturers

Manufacturers service the robots remotely. They connect only over our channel and only for the duration of the work; every sign-in is recorded in the log, so there are no permanently open “doors” for them in the network.

Office

Staff computers sit in a separate segment. Malware most often arrives here by email, but there is no path from this segment to the equipment, so an infected PC will not stop the site from working.

What it protects against
  • Ransomware
  • Conveyor stopped
  • Program tampering
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer
What is connected and how we handle it
Furnaces and mills

Furnaces and mills receive commands from the process control system. We place them in a separate segment: CUBRA Node lets through only those commands, and holds back unusual ones and raises an alert.

Safety system

The emergency shutdown system stops the process when something goes wrong and must work under any conditions. We place it in a closed segment with no path at all from outside, so even an infected control system cannot reach it.

Office

Staff computers sit in a separate segment. Malware most often arrives here by email, but there is no path from this segment to the equipment, so an infected PC will not stop the site from working.

What it protects against
  • Accident
  • Ransomware
  • Production stoppage
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer

Workshops with CNC machines

A machine runs the program it receives over the network. A tampered program means rejects or a broken machine.

What we offer
What is connected and how we handle it
Machine tools

We place them in the “Workshop” segment. They accept programs only from the process engineer’s PC through CUBRA Node – not from the office or from a USB stick in another PC.

Process engineer’s PC

Programs go from the process engineer’s PC to the machines. We place it in a separate segment; every program sent to a machine is recorded in the log: who, when and which one.

Office

Staff computers sit in a separate segment. Malware most often arrives here by email, but there is no path from this segment to the equipment, so an infected PC will not stop the site from working.

What it protects against
  • Program tampering
  • Rejects
  • Machine breakdown
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer

Light industry, packaging, printing works

Production lines and printing presses are often connected to the same network as the accounts department.

What we offer
What is connected and how we handle it
Lines and machines

Lines and machines receive jobs over the network, and the manufacturer services them remotely. We place them in a separate segment: commands are accepted only from their own control system, and the manufacturer’s service connects only over our channel.

Office and accounts

Office and accounts computers sit in a separate segment, with no path to the lines. Ransomware from email will at most encrypt an office PC, and the line will keep running.

What it protects against
  • Ransomware
  • Downtime
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer
What is connected and how we handle it
Design department

This is where drawings and firmware are kept. We place the department in a separate segment that only its staff can access. Bulk copying of drawings at night triggers an alert.

Lines and test benches

Lines and test benches sit in their own segment. Firmware reaches them only from the engineer’s trusted PC; every upload is recorded in the log.

Partners

Partners need drawings and files. They receive them through CUBRA Messenger or via a CUBRA Share link, not by ordinary email, which can be intercepted.

What it protects against
  • Theft of documentation
  • Tampered firmware
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer
What is connected and how we handle it
Ventilation, drainage, hoisting

These systems are controlled from the control room. We place them in closed segments that accept only the dispatcher’s commands. CUBRA Node will hold back an attempt to switch off ventilation or drainage and raise an alert.

Control room

The control room runs the mine and stays in touch with the crews. We place it in a separate segment; communication with the crews goes through CUBRA Messenger, and where there is no internet, through CUBRA Offline Gateway (CUBRA Offline Gateway — after release).

Office

Staff computers sit in a separate segment. Malware most often arrives here by email, but there is no path from this segment to the equipment, so an infected PC will not stop the site from working.

What it protects against
  • Threat to life
  • Mine shutdown
How we connect it
  1. CUBRA Node finds machine tools, robots and lines by itself
  2. We split the shop floor, warehouse, cameras and office into segments
  3. We connect equipment manufacturers through our channel
  4. We switch on alerts for the chief engineer
Several sites

All sites in one dashboard

The chief engineer sees every workshop and every alarm.

  • The same rules for all sites in one go
  • Alarms sent to the duty officer’s phone
  • Log of service company logins
And people too

Secure communication for staff

Engineers, shift teams and management stay in touch in CUBRA Messenger.

  • Messages, calls, mail, files
  • Works on inexpensive phones

FAQ – Manufacturing

How do I protect industrial control systems if the equipment can’t be stopped?

CUBRA Node is placed between the office network and the shop floor without stopping the lines. The shop floor becomes a separate segment hidden from the internet, and commands to machines and controllers are checked.

Can old controllers with no updates be protected?

Yes. We don’t change the equipment itself: the gateway lets through only the necessary commands, and a new program for all machines at night won’t go unnoticed.

How do I work with contractors who service the equipment?

A contractor gets in only through a secure CUBRA channel. Access opens for the duration of the work and closes by itself, and every sign-in is recorded in the log.

Will CUBRA find every device on the shop floor?

Yes. CUBRA Node finds devices, their firmware and known vulnerabilities by itself and suggests what to update first.

See also: ICS cybersecurity: where to start.