Most engineers think…
Most people assume you can point the same security tools at the plant floor that you use for the office — scan everything, drop an agent on each box, match known signatures. In OT that mental model is not just wrong, it is dangerous.
OT and ICS run fragile devices — PLCs, RTUs and HMIs — that can be disrupted by active probing, run for years without patching, and speak industrial protocols IT tools don't understand. Darktrace / OT instead watches traffic passively, learns the normal pattern of life of every asset and protocol with Self-Learning AI, and flags anomalies with no signatures and no agents. Crucially, because it correlates IT and OT on one platform, it can follow an attacker who lands on IT and pivots into OT — the most common attack path and the exact thing siloed tools miss.
① Why OT and ICS are not just 'IT on the plant floor'
The single most important idea: you cannot treat OT like IT. Operational technology runs the physical process — and the devices that do it (PLCs, RTUs and HMIs) are fragile, often run for years without patching, and can be knocked over by something as simple as an active scan.
That changes the rules. You generally cannot install agents on OT devices, you must not actively probe them, and the priorities are flipped: safety and uptime come before patching. On top of that, OT speaks its own languages — industrial protocols like Modbus, DNP3, Siemens S7, EtherNet/IP, OPC, IEC-104 and Profinet — that ordinary IT security tools simply do not understand.
So any OT security approach has to be passive, agentless and protocol-aware. Point a normal IT scanner at the plant floor and you risk causing the very outage you were trying to prevent.
Why must an OT security approach be passive rather than actively scanning devices?
② Darktrace / OT — passive Self-Learning AI on the plant floor
Darktrace / OT brings Darktrace's Self-Learning AI to OT and ICS. It works entirely from passive traffic — no active scanning, no agents on devices — so fragile gear is never disturbed. From that traffic it learns the normal pattern of life of each OT asset and each industrial protocol, then flags deviations as anomalies. Because it learns rather than matches, it needs no signatures and can catch novel or zero-day OT threats.
Protocol understanding and asset visibility
It genuinely understands OT protocols (Modbus, DNP3, S7, EtherNet/IP, OPC, IEC-104, Profinet), so it can tell a routine Modbus read from a suspicious Modbus write to a controller. Passively, it also builds an OT asset inventory and maps every device to the Purdue model levels — giving you a picture of what is talking to what, and where each asset sits, without ever sending a packet to a PLC.
Learns the normal pattern of life of each OT asset and protocol from passive traffic, then flags anomalies — no signatures needed.
Read-only observation of OT traffic with no agents and no probing, so fragile PLCs, RTUs and HMIs are never disturbed.
The line between office IT and plant-floor OT — the most common attack path, where an IT foothold pivots down into OT.
Automated investigation that stitches related IT and OT events into one incident, exposing the full cross-boundary chain.
In an interview, the first two words for any OT tool are passive and agentless — because the devices are fragile. Then add that Darktrace learns each protocol's pattern of life (Modbus, DNP3, S7) so it interprets commands, not just packet counts, and maps assets to the Purdue model.
How does Darktrace / OT decide that OT activity is a threat?
③ Catching the real attack path — IT to OT, and inside OT
Here is the part interviews care about: most OT attacks do not start in OT. They start with an IT foothold — a phishing email, a compromised laptop — and then pivot across the IT/OT boundary into the plant network. That boundary is the most common attack path, and the blind spot for tools that only see one side.
Because Darktrace correlates IT and OT on one platform, the Cyber AI Analyst can stitch related events into a single incident. An IT phishing compromise and a later anomalous command to a PLC are not two unrelated alerts — they read as one chain. It also catches anomalies within OT itself: an HMI issuing commands it never has, or a device talking to a controller it has never spoken to.
The interview line: the value is following the attacker across the boundary, not just watching one network. You see the foothold, the pivot, and the OT deviation as a connected story.
Priya at Sahyadri Steelworks near Pune faces this
The IT SOC's EDR cleaned a phishing-infected office laptop, but nobody can say whether anything reached the plant floor — the OT network is a black box to the IT tools.
The attacker used the IT foothold to pivot toward the OT segment; the IT-only tooling has zero visibility into OT protocols, so any plant-floor activity is invisible.
Open the Cyber AI Analyst incident in Darktrace / OT — it shows the laptop's connection crossing the IT/OT boundary and an anomalous Modbus write to a PLC the source had never talked to, flagged as a deviation from the OT pattern of life.
Darktrace / OT ▸ Cyber AI Analyst ▸ Incident ▸ Asset (PLC)Isolate the source on the IT side, confirm with the OT/engineering team that the PLC logic and setpoints are intact (alongside, not replacing, the safety system), and tighten the IT/OT segmentation to close that path.
Re-baseline shows the OT pattern of life back to normal, no further anomalous writes to the PLC, and the incident closed with the full IT-to-OT chain documented.
Most real OT attacks start on IT and pivot across the IT/OT boundary — a so-called air gap rarely holds. A tool that only watches OT misses where the attack came from; a tool that only watches IT misses where it went. You need IT and OT correlated to see the whole chain.
▶ Watch an IT-to-OT attack get caught before the PLC is touched
How a phishing foothold turns into an OT command, and how Darktrace / OT sees it. Press Play for the caught path, then Break it to see the classic failure.
A compromised IT laptop sends a Modbus write to a PLC it has never communicated with. How does Darktrace / OT treat this?
④ One platform vs silos — and the pitfalls
Why one platform? Because correlating IT + OT together is what lets Darktrace follow an attacker from an IT foothold down into OT. An IT-only tool never sees the OT side; an OT-only tool never sees where the attack came from. Either silo misses the cross-boundary path. Darktrace / OT also adds risk and exposure context — which assets are most at risk — and is designed to work alongside safety systems, never to replace them.
The classic pitfalls
Three mistakes sink most OT-security efforts. Active scanning in OT — using IT-style probes that can crash fragile devices. Treating IT and OT as separate silos — which misses the cross-boundary attack entirely. And having no passive visibility into OT protocols — so anomalous Modbus or S7 traffic goes unseen. Darktrace / OT is built to avoid all three: passive, protocol-aware, and correlated with IT.
Never close an OT incident on a hunch. Use the Cyber AI Analyst incident to see the exact asset, protocol and command, then confirm with the OT/engineering team that the controller's logic and setpoints are intact — alongside the safety system, which Darktrace complements rather than replaces.
Which of these is a classic OT-security pitfall Darktrace / OT is designed to avoid?
🤖 Ask the AI Tutor
Tap any question — instant, scoped to this lesson. No login, no waiting.
Pre-curated from vendor docs + community Q&A, scoped to this lesson. For a live prod issue, paste your export into chat.techclick.in.
📝 Wrap-up assessment — six more
You've answered 4 inline. Six left. 70% (7 of 10) marks the lesson complete on your profile. Tap Submit all answers at the end.
🧠 In your own words
Type one line: why can Darktrace / OT catch an IT-to-OT attack that an IT-only tool cannot? Then compare with the expert version.
🗣 Teach a friend
Best way to lock it in — explain it in one line to a teammate. Tap to generate a paste-ready summary.
📖 Glossary
- OT (Operational Technology)
- The hardware and software that runs physical industrial processes — the plant floor, as opposed to office IT.
- ICS (Industrial Control System)
- The systems that monitor and control industrial processes — PLCs, RTUs, HMIs and SCADA.
- PLC / RTU / HMI
- Programmable Logic Controller, Remote Terminal Unit and Human-Machine Interface — fragile OT devices that run and display the process.
- Pattern of life
- The learned baseline of normal behaviour for an OT asset or protocol, against which Darktrace flags anomalies.
- Self-Learning AI
- Darktrace's anomaly-detection AI that builds its own baseline from passive traffic and needs no signatures.
- Industrial protocols
- OT languages such as Modbus, DNP3, Siemens S7, EtherNet/IP, OPC, IEC-104 and Profinet that Darktrace / OT interprets.
- IT/OT boundary
- The junction between the IT and OT networks — the most common path for an attacker to cross into OT.
- Purdue model
- A reference model that organises ICS/OT into hierarchical levels, used to give OT assets context.
- Cyber AI Analyst
- Darktrace's automated investigation that stitches related IT and OT events into one incident, exposing the cross-boundary chain.
📚 Sources
- Darktrace — Darktrace / OT: cyber security for critical infrastructure and industrial systems. darktrace.com/products/ot
- Darktrace — Self-Learning AI and the ActiveAI Security Platform. darktrace.com
- Darktrace — Cyber AI Analyst: automated investigation across IT and OT. darktrace.com
- Darktrace — OT asset visibility and Purdue model mapping (product overview). darktrace.com/products/ot
- Purdue Enterprise Reference Architecture / ISA-95 — ICS network segmentation model.
- CISA — Industrial Control Systems (ICS) security guidance and OT protocol references. cisa.gov
What's next?
Got the OT approach? Next, see the Threat Visualizer in action and how Darktrace is actually deployed — sensors, taps and what sits where on the network.