Skip to content
SOC for OT

Comparisons

IT SOC vs OT SOC: 10 differences that matter in industry

By 2 min read

Key takeaways

  • The priority order flips from confidentiality-first to safety- and availability-first.
  • OT telemetry comes mainly from passive network sensors, not EDR agents.
  • Automated containment is rare in OT; response is negotiated with operations.
  • An IT SOC can cover OT only with OT telemetry, protocol knowledge and agreed escalation paths.

What is the core difference between an IT SOC and an OT SOC?

The core difference is what is being protected. An IT SOC protects information: data, identities and the systems that process them. An OT SOC protects a physical process — a production line, a water treatment plant, a substation — and the people and equipment around it. Everything else follows from that.

IT SOC vs OT SOC: 10 differences
DimensionIT SOCOT SOC
1. PriorityConfidentiality → integrity → availabilitySafety → availability → integrity → confidentiality
2. AssetsLaptops, servers, cloud workloads, identitiesPLCs, RTUs, HMIs, engineering workstations, historians, SIS
3. TelemetryEDR agents, identity, e-mail and cloud logsPassive network sensors (SPAN/TAP), OT host logs, firewalls, remote access
4. ProtocolsHTTP(S), DNS, SMB, Kerberos, LDAPModbus, S7comm, PROFINET, EtherNet/IP, DNP3, IEC 104, IEC 61850, OPC UA
5. Asset lifetime3–5 years15–30 years, often unsupported operating systems
6. PatchingMonthly cycles, automatedOnly in maintenance windows; compensating controls instead
7. Detection focusMalware, phishing, credential abuse, data theftUnauthorised changes to logic and setpoints, unusual engineering access, ICS malware
8. ContainmentAutomated isolation within minutesPre-agreed, manual, coordinated with the control room
9. SkillsWindows, cloud, identity, malware analysisPlus industrial protocols, control engineering and process safety
10. KPIsMTTD, MTTR, % endpoints coveredPlus % of critical conduits monitored, asset inventory accuracy, safe-response rate

Why does the priority order flip in OT?

In IT, a few hours of downtime is costly but rarely dangerous. In OT, an unplanned stop can damage equipment, spoil a batch or, in the worst case, endanger people. That is why OT frameworks such as NIST SP 800-82 and IEC 62443 put safety and availability first. For the SOC this means that an alert is never handled in isolation: analysts need to know which process a device controls and what a response would do to it.

Why is OT monitoring mostly passive?

Many controllers and embedded devices were never designed to receive unexpected traffic. Active scanning or heavy polling can make them freeze or reboot. Most OT SOCs therefore mirror traffic from switches (SPAN) or install network TAPs and analyse it out-of-band, decoding industrial protocols to see who programs which controller, which commands are sent and which values change.

Can an IT SOC monitor OT?

Yes, under three conditions:

  1. OT telemetry — passive sensors at the main conduits and logs from OT hosts and remote-access paths.
  2. OT knowledge — analysts (in-house or via a partner) who understand industrial protocols and the MITRE ATT&CK for ICS techniques.
  3. Agreed escalation — a contact in operations for every site and pre-agreed response options per zone.

Research by SINTEF and NTNU describes several workable models, from a fully integrated IT/OT SOC to a dedicated OT SOC and vendor-operated monitoring. See What is a SOC for OT? for an overview.

Frequently asked questions

Should IT and OT security monitoring be in one SOC?

Many organisations choose a converged SOC because attacks on OT usually start in IT. It works when the SOC receives OT telemetry, has analysts or a partner with industrial protocol knowledge, and has agreed playbooks with operations. A dedicated OT SOC makes sense for large, safety-critical or highly regulated operators.

Why can't an OT SOC just isolate an infected host?

Because an OT host may be part of a running process. Isolating an HMI, historian or engineering workstation can blind operators or stop production, and touching a safety system can create a hazardous situation. Containment options are therefore pre-agreed per zone and executed together with the control room.

Sources

  1. NIST SP 800-82 Rev. 3: Guide to Operational Technology (OT) Security — National Institute of Standards and Technology
  2. MITRE ATT&CK for ICS matrix — MITRE
  3. A Comparative Study of SOC Models for Operational Technology — SINTEF / NTNU