Q-Cyber Magazine
IT/OT convergence: One estate, two disciplines
As industrial networks connect to enterprise IT, operators need a shared model that respects ISA/IEC 62443 for control systems, rejects implicit trust on either side of the link, and still meets CERT-In reporting duties.

The connection between a plant network and a corporate network is now ordinary. The security model that treats one as "safe inside" and the other as "the office" is not. Convergence is a fact of architecture; implicit trust across the join should not be.
Two disciplines, one incident
Information-technology teams are used to confidentiality, patching cycles and user identity. Operational-technology teams are used to safety, availability and long equipment lives. ISA's description of 62443 is useful here: the series is intended to bridge those worlds, not to declare one of them the winner. A patch regime that assumes a weekly reboot will fail on a turbine controller. A plant network that assumes a corporate credential is harmless will fail in the other direction.
NIST's zero-trust language helps at the join. A connection from the enterprise to the plant should be authorised as a request to a resource, not trusted because it came from "inside the company." Remote vendor access, shared historians, and data-lakes that copy process data into business analytics are typical places where that implicit trust still sits.
Ransomware makes the point sharper. If a business e-mail compromise can reach an engineering workstation, and if backups of process configurations sit on the same reachable storage, the incident is no longer only an office problem. The CISA guide's insistence on offline, tested backups and on narrowing initial access paths is therefore an OT control as well as an IT one.
Exhibit 1
What should be common, and what should stay distinct, at the IT/OT join
Source: Qualitative framework derived from ISA's description of the 62443 series; NIST SP 800-207 (August 2020); CISA #StopRansomware Guide; CERT-In Directions, 28 April 2022. No incident counts are claimed.
Implications
- Draw the join explicitly, with a resource-level access policy for every path between business IT and the plant.
- Use 62443 roles and security levels for the OT side, rather than copying the office policy.
- Place engineering backups offline, and test restore without assuming an IT-style reboot.
- Run one incident clock, so a plant event is not delayed while teams argue about ownership.
What this means for critical infrastructure and energy
Convergence will continue because data and remote support have operational value. The operators who will absorb that value safely are those who can show, for each path into the plant, who is allowed to use it, how it is logged, and how the plant can be restored if it is abused.


