Blog

Securing remote water and wastewater sites over cellular

Written by IXT | 16. nov. 2026, 11:54:09

A pump station on the edge of town has no staff, no server room and no security team. It has a controller, a cellular link and a job that cannot stop. Add every reservoir, treatment plant and sewage pump a utility runs, and you have a long list of unattended sites connected back to one control system.

 

Attackers have noticed. Nozomi Networks' OT and IoT security report for the first half of 2025 ranked energy, utilities and waste among the five most targeted sectors in its customer base.

 

Water and wastewater was the third use case Henning Solberg, CTO at IXT, and Trevor Dearing of Illumio discussed in our webinar, Securing IoT Devices.

 

 

Why water is harder to secure

The sites are remote and unattended. Pump stations, reservoirs and treatment plants run with nobody on site. Nobody notices a strange connection at 2am.

 

The owners differ from place to place. In many cases municipalities run these systems. Henning pointed out that IT security policy varies from one municipality to the next, so every connection project starts from a different baseline.

 

The money goes elsewhere. Trevor was direct about it. Water gets less attention than electricity and wind turbines. Households pay less for water than for power, budgets are tighter, and the money goes on fixing leaks and stopping sewage reaching rivers. Cyber security comes last.

 

The devices cannot protect themselves. Patch windows are rare, and site controllers have no room for security software. The network has to carry the protection.

 

 

Connecting the control system without exposing it

For water customers, IXT builds a private APN for the sites and a network-node interface into the utility's control system. That interface is the sensitive point. The control system sits in a wider environment IXT does not manage, so it has to be isolated from the endpoints in the field.

 

The aim is simple to state. A pump station talks to the control system it reports to, over the protocols it needs, and to nothing else. Nothing in the field reaches the wider network behind the control system.

 

IXT builds that boundary in the network. The IXT SIM identifies each site controller. SecureNet keeps the traffic on the private APN, off the public internet. Zscaler ZTNA in IXT's core network checks every session before a connection opens. Illumio applies policy-based segmentation between the sites and the control system.

 

A compromised pump station reaches its own controller, not the network behind it.

 

 

Seeing what every site talks to

Trevor's rule applies to every remote site: "You can't protect what you can't see." Zero Trust Visualisation, powered by Illumio, shows each connection from each IXT-connected site in real time. It flags changes in behaviour, such as a site that starts talking to a new destination or sending more data than usual.

 

It also changes how you rank risk. Exposure is a system's vulnerability score combined with how many things it connects to. In Trevor's example, a high-scoring system with one controlled connection is low exposure, while a low-scoring workstation connected to ten systems is high exposure.

 

That matters because patching is slow everywhere, not only in water. The Verizon 2024 Data Breach Investigations Report found organisations take 55 days on average to fix half of their most severe vulnerabilities once a patch exists. Until a patch window opens, restrict what the vulnerable system talks to. Trevor calls this virtual patching.

 

 

Contractor access without a VPN

Integrators and equipment vendors need to reach site controllers to maintain them. A VPN into the APN gives them far more than one site. Privileged remote access through Zscaler replaces it with a browser session to the specific controller, time-limited and recorded, with no software to install.

 

 

Regulation

Drinking water and wastewater are both sectors under NIS2. Operators carry obligations on access control, segmentation, incident detection and supplier access. IXT Zero Trust addresses NIS2 Article 21(2) technical controls. Your risk documentation, incident response plans and supplier governance remain your responsibility.

 

 

Where to start

Begin with a map. Find every site, every connection and every remote access route. Then surround the systems with the highest risk and exposure, separate IT from OT, and write explicit allow rules for the connections that keep water flowing. That is the order Trevor recommends, and it suits a sector where the budget has to go where the risk is highest.

 

 

Watch the water and wastewater segment

Henning and Trevor discuss water and sewage from 47:39 in the recording.

 

 

 

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.