be.OT Secure Industrial Platform

Critical infrastructure under attack

Critical infrastructure, from power grids to water supply and industrial plants, is no longer a theoretical target. In late December 2025, Poland foiled an attack against cogeneration plants and management systems for wind and solar farms, which its government linked to Russian services. In July 2026, attackers exploited internet-connected PLCs across more than 30 water systems in Minnesota (U.S.), locking some operators out and forcing equipment to be operated manually. In October 2026, a wave of attacks raised refrigerator temperatures at hundreds of supermarkets in France and, in early November, in Belgium and other European countries, with product losses valued in the millions of euros.

On top of this comes growing regulatory pressure. The NIS2 Directive requires essential entities, among them those in the energy sector, to manage their cybersecurity risks, and the Cyber Resilience Act (CRA) requires security by design from manufacturers, with vulnerability reporting in force since September 2026 and full application in December 2027.

At the same time, the shutdown of 2G and 3G networks, primarily in Europe but also in other parts of the world, forces the replacement of many devices deployed in the field. This is the opportunity to build in security from day one, rather than adding it afterward as a separate layer.

What are the important points related to be.OT

Designed specifically for OT environments

Inspection and control purpose-built for industrial environments, with more than 1,000 OT protocol signatures, such as IEC 60870-5-104, IEC 61850, DNP3, and Modbus, and easy customization of the customer’s proprietary protocols.

Operation at scale

Zero-touch provisioning to deploy and maintain large fleets of devices across thousands of dispersed locations, with a consistent security policy, no configuration drift, and no unnecessary site visits.

OT cybersecurity: protecting without disrupting

Several factors make this environment unique. Assets are distributed across plants, remote stations, or isolated equipment, with variable connectivity. Equipment and platforms from different manufacturers coexist, many designed to last for decades. Remote access by suppliers and engineers is necessary, but must be done with control and traceability. And communications use numerous industrial protocols, such as Modbus, DNP3, IEC 60870-5-104, IEC 61850, and OPC UA, which require specific inspection that conventional IT firewalls do not understand.

On top of this is a visibility problem: you cannot protect what you cannot see. Unknown or unauthorized devices are a threat, and telling normal behavior from anomalous behavior in machine-to-machine flows requires an approach centered on OT protocols, with specific detection, passive inventory, and progressive response.

That is why OT cybersecurity rests on three ideas:

• Protection at the edge: inspecting and controlling traffic where it originates, even when the link to the control center fails.
• Zero-trust access with industrial protocol awareness: each user or supplier reaches only the asset they need, and every session is inspected, not just authenticated.
• Unified visibility: seeing the inventory, flows, and alarms across the entire network, from the plant floor to the corporate network, in a single console.

be.OT – Use Cases

Traffic lights, streetlights, water, video, and municipal services protected end to end and managed from a single control center.

Substations and power grids

Secure connectivity between substations, RTUs, PLCs, and smart meters, and the control center, with cybersecurity built into the equipment itself.

Challenge

In addition, many of its devices still rely on 2G and 3G networks that operators are shutting down, and there is rarely an up-to-date inventory of what is actually connected at each substation. Any security measure must reinforce operational continuity, not degrade it, and the equipment must run for a decade or more with minimal maintenance.

Solution

With the Custos family of Industrial Edge devices, inspection of protocols such as IEC 60870-5-104 and the inventory run locally at the edge and keep working even if the link goes down.

Connectivity is flexible: 5G, LTE, 450 MHz, satellite networks, PRIME PLC, and BPL. Everything is managed from a single console, with zero-touch provisioning to deploy and maintain fleets of thousands of devices.

Why Teldat?

Industrial M2M communications

Protection of sensors, robots, RTUs, and connected machines at remote locations, with secure tunnels to the corporate data center.

Challenge

Many of these devices are left exposed or with weak credentials, and real incidents prove it. In 2026, internet-exposed PLCs were exploited across more than 30 water systems in the United States, and in 2025 a weak password made it possible to manipulate a valve for four hours.

Companies need controlled remote access for their suppliers, to know which devices are at each site, and to do so without adding complexity or jeopardizing operational continuity. Small teams cannot afford a different security tool for every site.

Solution

Third-party remote access follows the zero-trust model: each engineer reaches only the asset they need, and the session is inspected at the industrial protocol level. Signatures and security updates arrive automatically from the cloud. The result is a consistent policy across all sites and a single console.

Why Teldat?

Smart cities

Traffic lights, streetlights, water, video, and municipal services protected end to end and managed from a single control center.

Challenge

In 2023, a cyberattack on the traffic management system of Olsztyn (Poland) disrupted the traffic lights at nearly 100 intersections for several weeks, unauthorized radio commands brought about 20 trains to a standstill, and that same year a group compromised pressure-monitoring equipment at a municipal water utility in Pennsylvania.

City councils, with small technical teams, must protect infrastructure scattered across blocks or districts, know what is connected, and comply with NIS2 without multiplying cost or operational complexity. In addition, each service usually depends on a different supplier, which makes a single view harder to achieve.

Solution

In a centralized architecture, inspection runs on shared security instances. In a distributed architecture, each device applies the policy locally, with segmentation and zero trust between devices, and keeps protecting even if the link goes down. SD-WAN controllers maintain a single policy, and the two modes can be combined within the same city.

Why Teldat?