loader image

OT Secu­rity

OT Secu­rity OT security, or OT cybersecurity, is the protection of operational technology, the hardware and software that monitors and controls physical processes such as PLCs, SCADA systems and industrial control systems, against cyber threats, with availability and safety as the top priorities.

Context

OT secu­rity, also called oper­a­tional tech­nology secu­rity or OT cyber secu­rity, protects the systems that keep a factory, a power plant or a water utility running. Oper­a­tional tech­nology (OT) includes program­mable logic controllers, distrib­uted control systems, super­vi­sory control and data acqui­si­tion (SCADA), HMIs, robots, drives and safety systems. When these systems are attacked, the damage is not limited to data: produc­tion stops, prod­ucts are scrapped, equip­ment breaks and people can be hurt.

Essen­tials
  • Protects: indus­trial control systems, PLCs, SCADA, DCS, sensors and actu­a­tors
  • Top prior­i­ties: avail­ability and safety, then integrity and confi­den­tiality
  • Key stan­dard: IEC 62443 for the secu­rity of indus­trial automa­tion and control systems
  • Regu­la­tion: NIS2 for oper­a­tors, Cyber Resilience Act for product manu­fac­turers

What is OT in cyber­se­cu­rity?

In cyber­se­cu­rity, OT stands for oper­a­tional tech­nology, the coun­ter­part to infor­ma­tion tech­nology (IT). IT systems process infor­ma­tion: email, ERP, office appli­ca­tions. OT systems interact with the phys­ical world: they read sensors, move motors, open valves and control processes. OT secu­rity covers the people, processes and tech­nolo­gies that protect each OT system, the OT devices and the OT network they run on, including remote terminal units in distrib­uted infra­struc­ture.

For decades, OT envi­ron­ments were isolated, used propri­etary proto­cols and were consid­ered safe by obscu­rity. Industry 4.0 changed that. Machines now connect to MES, ERP, cloud plat­forms and remote service, which brings effi­ciency, but also exposes OT assets to the same cyber threats as IT.

What is the differ­ence between IT and OT cyber­se­cu­rity?

IT secu­rityOT secu­rity
Main priorityConfi­den­tiality of dataAvail­ability and safety of the process
System life­time3 to 5 yearsOften 15 to 30 years
PatchingRegular, often auto­maticOnly in main­te­nance windows, after testing
Proto­colsStan­dard IT proto­cols with secu­rityMany legacy indus­trial proto­cols without authen­ti­ca­tion
Impact of an inci­dentData loss, down­timeProduc­tion stop, damage, safety risks

These differ­ences mean that tradi­tional IT secu­rity tools cannot simply be copied into an OT envi­ron­ment, and an effec­tive OT secu­rity program needs its own secu­rity strate­gies. An aggres­sive network scan that is harm­less in IT can crash an old controller. Secu­rity measures have to respect real-time require­ments and long life­cy­cles.

Why is OT cyber­se­cu­rity impor­tant?

Attacks on indus­trial control systems are docu­mented since Stuxnet in 2010, followed by the attacks on the Ukrainian power grid in 2015 and 2016 and the Triton malware that targeted safety systems in 2017. Today the most common threat is ransomware that spreads from the IT network into produc­tion, forcing compa­nies to shut down plants as a precau­tion. Each of these high-profile OT cyber­at­tacks shows that OT secu­rity is a busi­ness conti­nuity topic, not only a tech­nical one. The conver­gence of IT and OT increases the risk of cyber inci­dents disrupting produc­tion, which is why agen­cies such as the US Cyber­se­cu­rity and Infra­struc­ture Secu­rity Agency (CISA) and the German BSI publish specific guid­ance for indus­trial secu­rity.

Main threats to OT systems

  • ransomware and malware entering from the IT network
  • inse­cure remote access for main­te­nance and service
  • legacy systems with known secu­rity vulner­a­bil­i­ties that cannot be patched quickly, often a whole indus­trial control system running on outdated soft­ware
  • flat networks without segmen­ta­tion between IT, OT and safety systems
  • supply chain risks from compo­nents, soft­ware and inte­gra­tors
  • missing asset inven­tory, so nobody knows what is connected

IEC 62443 and the Purdue model

IEC 62443 is the inter­na­tional cyber­se­cu­rity frame­work for the secu­rity of indus­trial automa­tion and control systems. It defines roles (asset owner, system inte­grator, product supplier), require­ments for each role and secu­rity levels from 1 to 4. A central concept is zones and conduits: the network is divided into zones with similar secu­rity needs, and commu­ni­ca­tion between them runs through controlled conduits. The Purdue model, which divides an indus­trial network into levels from field devices to enter­prise IT, is often used to plan this segmen­ta­tion and the OT network archi­tec­ture. In the US, NIST SP 800–82 provides compa­rable guid­ance.

Best prac­tices for protecting OT systems

No single secu­rity solu­tion covers every­thing. These secu­rity best prac­tices form the core of OT cyber­se­cu­rity:

  1. Know your OT assets: asset manage­ment is the first best prac­tice. Build and main­tain an inven­tory of devices, firmware and connec­tions, so you can manage OT risks you actu­ally know about.
  2. Segment the network: sepa­rate IT and OT, and create zones within OT.
  3. Secure remote access: central, authen­ti­cated, logged access instead of indi­vidual modems or VPNs.
  4. Manage vulner­a­bil­i­ties: track vulner­a­bil­i­ties in all compo­nents, for example with SBOMs, and patch in planned windows.
  5. Monitor the OT network: OT secu­rity moni­toring and OT threat detec­tion analyze network traffic and detect anom­alies with OT-aware tools.
  6. Apply secu­rity controls: access control, multi-factor authen­ti­ca­tion for remote users and hard­ened config­u­ra­tions reduce the attack surface.
  7. Prepare for inci­dents: backups of controller programs, recovery plans and exer­cises.
  8. Demand secu­rity from suppliers: secure-by-design prod­ucts, update commit­ments and secu­rity docu­men­ta­tion.

OT secu­rity, regu­la­tion and open stan­dards

Two EU laws make OT cyber­se­cu­rity manda­tory. The NIS2 Direc­tive requires oper­a­tors in crit­ical sectors, including many manu­fac­turers, to manage cyber­se­cu­rity risks in their OT envi­ron­ment. The Cyber Resilience Act requires manu­fac­turers of controllers, sensors, machines and indus­trial soft­ware to deliver secure prod­ucts with secu­rity updates.

Open stan­dards help here. OPC UA brings authen­ti­ca­tion and encryp­tion to indus­trial commu­ni­ca­tion. The OI4 Indus­trial Cyber Secu­rity work­group defines secu­rity require­ments for every layer of the OI4 archi­tec­tural guardrails, and its white papers on vulner­a­bility manage­ment with SBOMs, post-quantum cryp­tog­raphy and Asset Admin­is­tra­tion Shell secu­rity are avail­able in the OI4 down­loads.

Frequently asked ques­tions

What does OT stand for in OT secu­rity?

OT stands for oper­a­tional tech­nology: the hard­ware and soft­ware that moni­tors and controls phys­ical devices and processes in industry, such as PLCs, SCADA systems and indus­trial robots.

What is the differ­ence between OT secu­rity and ICS secu­rity?

The terms are often used inter­change­ably. ICS secu­rity focuses on indus­trial control systems, while OT secu­rity is slightly broader and covers all oper­a­tional tech­nology, including building automa­tion and other cyber-phys­ical systems.

Where should a company start with OT cyber­se­cu­rity?

With visi­bility. An inven­tory of OT assets and their connec­tions is the basis for every further step, from segmen­ta­tion to vulner­a­bility manage­ment.