Blog

Zero Trust for IoT and OT: answers from our webinar with Illumio

Written by IXT | 17. nov. 2026, 09:15:01

Your IoT and OT devices do not run security software, do not patch on demand and do not tell you when something is wrong. Those three facts drive most of the questions we hear about securing them.

 

On 8 October, Henning Solberg, CTO at IXT, and Trevor Dearing, who runs the Industry Solutions team at Illumio, took on many of them in our webinar. Our write-up, 8 lessons from IXT and Illumio, covers the main themes. These are the questions it leaves open, starting with the two the audience asked live.

 

 

Questions from the live audience

What data does anomaly detection use, and how many false positives should I expect?

Trevor explained that Illumio baselines connection behaviour: who talks to whom, which protocols, how much data. It flags changes from that baseline. Because it models the whole network, he expects few false positives. A legitimate change in how people work still gets flagged, but it is easy to identify. The customer sets the thresholds, and the data feeds into the customer's SIEM for the bigger picture.

 

 

Should I enforce rules top-down or bottom-up?

Neither, in Trevor's view. Best practice is risk-led. Label every system from your CMDB or an asset discovery tool, then add vulnerability and threat data. First, surround high-risk, high-exposure systems. Second, separate IT from OT and IoT. Third, apply explicit allow rules between your most important systems. Default deny is the end state, not day one.

 

 

Networks and connectivity

Is cellular more secure than Ethernet or Wi-Fi for IoT?

Cellular gives you a better starting point. Henning's point is that it is point-to-point by design, so devices do not share a broadcast domain and do not see each other by default. A router with several devices behind it on Ethernet rebuilds a shared segment, so that setup still needs segmentation. Read why cellular is a stronger starting point for OT and IoT security.

 

Isn't a private APN enough?

No. A private APN keeps traffic off the public internet. It does not show you what your devices talk to, and it does not stop one compromised device reaching the rest of the fleet. Henning acknowledged that operators, IXT included, used to assume the private APN was safe. That assumption no longer holds.

 

Are VLANs a security control?

Trevor's caveat: only when dynamic VLAN protocols are switched off. With them on, a misconfigured or malicious device negotiates its way onto other VLANs.

 

Is my device IoT or OT, and does it matter?

It matters, because the two fail in different ways. IoT devices report independently to a cloud or head-end system. OT devices sit inside a control hierarchy. Read IoT vs OT security for how to tell them apart.

 

 

Risk and patching

What is the difference between vulnerability and exposure?

In Trevor's framing, exposure combines a system's vulnerability score with how many things it connects to. A high-scoring system with one controlled connection is low exposure. A low-scoring workstation connected to ten systems is high exposure. Rank your work by exposure, not by score alone.

 

What do I do about devices I cannot patch?

Restrict what they talk to until a patch window opens. Trevor calls this virtual patching. It matters because exploitation is speeding up. The Verizon 2024 Data Breach Investigations Report found exploitation of vulnerabilities as a way into networks rose by about 180% in a year, while organisations took 55 days on average to fix half of their most severe vulnerabilities.

 

Where should I look first?

Trevor's first practical step: search your OT estate for RDP and remove it wherever you find it.

 

 

Regulation

Which regulations apply to connected devices?

NIS2 applies to operators in sectors such as energy, transport and water. The Cyber Resilience Act applies to products with digital elements. The Radio Equipment Directive sets cybersecurity requirements for radio and cellular equipment. Henning's point: if you operate or build remote connected devices, at least one applies to you, whatever your sector.

 

What does the Cyber Resilience Act require of my vendors?

It requires products to ship secure, but it does not define what secure means. Trevor's advice is to push vendors to show you how they meet it.

 

Does IXT Zero Trust make me NIS2 compliant?

No single product does. IXT Zero Trust addresses NIS2 Article 21(2) technical controls: access control, network segmentation, incident detection, supply chain access and audit trail. Risk documentation, incident response plans, staff training and supplier governance remain your responsibility.

 

 

See it in practice

For how these answers apply to real deployments, read our guides to EV charging networks and water and wastewater sites, or watch the full session.

 

 

Why trust this guide

This guidance is based on real IoT and OT deployments in regulated industries including energy, utilities, and industrial environments.

IXT designs and operates secure connectivity architectures where:

  • devices are deployed across multiple countries and networks
  • SIM-level identity is enforced at the network edge
  • third-party access is controlled without VPNs
  • audit trails are required for regulatory compliance (including NIS2)

The patterns described here reflect how these environments are secured in practice, not theoretical models.

 

About the author

This article was written by the IXT Connectivity and Security team.

IXT operates a full MVNO core network and delivers secure IoT connectivity across 190+ countries and 600+ mobile networks. The team works directly with industrial, utilities, and infrastructure operators to design and secure large-scale IoT and OT deployments.

Their focus is on network-level Zero Trust architecture, SIM-based identity, and secure device communication without relying on VPNs or endpoint agents.