Getting operational data into the enterprise is where the value of an industrial estate is meant to be released. It is also where a cyber attack reaches the plant and where accountability quietly disappears, because the join belongs fully to neither side.
The short answer
- Operational technology runs the plant and prizes availability and safety. Corporate IT runs the business and moves faster. They have different clocks, different risks and different cultures.
- Convergence is worth doing because operational data drives maintenance, efficiency and resilience decisions the business cannot make blind.
- The danger is that connecting the two extends the corporate attack surface into systems that control physical processes.
- Most failures are governance failures: the boundary between the two estates has no named owner, so decisions about it are made by default.
- Govern the join deliberately, with a defined data flow, controlled crossing points and ownership on both sides.
Two estates that were never the same
Operational technology is the control systems, sensors and actuators that run a physical process: a substation, a treatment works, a production line. It is judged on availability and safety, changes slowly and deliberately, and often runs equipment older than the engineers maintaining it. Corporate IT is the servers, applications and networks that run the business. It is judged on function and cost, patches frequently, and refreshes every few years. These are not two versions of one thing. They evolved separately, for different purposes, with different definitions of a good day.
Convergence brings them together so operational data can inform enterprise decisions, and there are real gains in doing so: condition-based maintenance, energy optimisation, and a resilient operating picture during an incident. The gains are the reason the projects are funded. The risks are the reason they need governing rather than simply connecting.
Connecting the estates moves the risk both ways
The headline risk runs from IT to OT. A corporate network compromise that once meant lost email now has a path toward systems that open breakers and control flow. Attacks on industrial operators repeatedly reach the plant through the enterprise side, because that is where the exposure and the people are. Connecting the estates without controlling the crossing extends every corporate weakness into a place where the consequence is physical.
Risk runs the other way too. Operational data pulled into corporate analytics inherits the corporate estate's exposure, and a model that starts to depend on an operational feed makes that feed's integrity a business-critical matter. This is the same expansion of scope examined in how AI lands inside the NIS duties: once operational data and enterprise systems are joined, the regulated perimeter grows to match.
The join fails on ownership, not on technology
The technical patterns for a safe boundary are well established: segmented networks, a controlled zone between the estates, one-way data flows where the process allows, strict control of what crosses and in which direction. The reason convergence still goes wrong is that the boundary itself has no owner. OT engineering assumes IT security is handling the connection. IT security assumes the OT team owns anything touching the plant. The gap between those assumptions is exactly the crossing point an attacker uses and an assessor flags.
Governing the join means making that boundary a named responsibility. Someone owns the crossing points, the rules for what data moves and in which direction, and the joint decisions when a change on one side affects the other. That owner sits across both estates rather than inside one, because a boundary governed from only one side is governed for that side's priorities and blind to the other's.
What good governance of the boundary looks like
| Element | What it means in practice |
|---|---|
| A defined data flow | You can state exactly what data crosses the boundary, in which direction, and why. Anything undocumented is closed. |
| Controlled crossing points | Traffic passes through a small number of governed points, segmented and monitored, rather than through ad hoc connections. |
| Ownership on both sides | Named owners for the OT estate, the IT estate and the boundary between them, with a joint route for decisions that affect both. |
| Change control across the line | A change on one side that affects the other is assessed jointly before it happens, not discovered afterwards. |
| Monitoring at the join | The crossing points are watched for anomalies, because they are where a compromise on one side becomes a compromise on the other. |
The constraint
The binding limit in OT/IT convergence is ownership of the boundary itself, rather than the sophistication of the security technology deployed on either side. Investing in segmentation and monitoring while no single owner is accountable for the crossing leaves the decisions about it made by default from one side, because the deciding question is who is answerable for the join across both estates, and that is an organisational appointment rather than a product.
Where to start
Begin by drawing the boundary and asking who owns it today. In most operators the honest answer is that nobody does, and that answer explains more about the state of the convergence programme than any architecture diagram. Name the owner, document what crosses the line, close what should not, and put a joint change process across the two estates. The technology to secure the boundary is available and understood. The accountability to govern it is what is usually missing, and it is what decides whether convergence releases value safely or opens a path to the plant.
Sources
- National Cyber Security Centre, Cyber Assessment Framework, on segmentation, access and monitoring outcomes for operational systems.
- The Network and Information Systems Regulations 2018, on the security duties that follow operational systems into scope.
- NCSC guidance on operational technology and secure system design.