
The traditional model of industrial cybersecurity is becoming harder to sustain. For manufacturing and other industries that depend on uninterrupted power, increasingly interconnected systems introduce cybersecurity risks that can have consequences well beyond the utility itself.
Industrial cybersecurity has historically relied heavily on network segmentation. Operational technology (OT) environments could be separated from other networks, with relatively few connections into and out of those environments. Cybersecurity teams could focus on controlling those connection points without necessarily needing a detailed understanding of every asset, communication path and operational dependency within the OT environment.
Today, however, utilities are connecting more devices and systems across existing grid infrastructure and creating more connections between operational and business environments. They're expanding digital communications to improve grid intelligence, automate processes, reduce manual workflows and make previously isolated information useful across the organization. This includes transitioning legacy serial communications to digital networks.
As a result, cybersecurity can no longer rely primarily on where the boundary is. It increasingly needs to understand what is operating behind and across those boundaries, why it needs to communicate, what it should communicate with, precisely what those communication patterns should look like, what depends on those communications and what could happen if that expected behavior changes.
This is where security architecture and cyber asset context become increasingly important. Security architecture defines how systems and networks should connect, where boundaries and trust relationships should exist, and how communication should be controlled. Cyber asset context provides the operational understanding needed to explain why those connections exist, what purpose the assets serve, how they are expected to behave and what consequences could follow if that behavior changes.
Together, architecture and asset context provide the foundation for effective monitoring and detection. An alert that a device communicated with another system has limited meaning by itself. Determining whether that communication is expected, suspicious or potentially operationally significant requires an understanding of what the device is, why the communication exists and what could be affected.
Why Operational Context Matters
Preventing unauthorized connections is only part of the challenge. Utilities must also ensure that legitimate existing and new connections alike are understood, appropriately designed and incorporated into the security architecture. This requires coordination among the teams responsible for network operations, cybersecurity and the equipment itself.
Knowing that a device exists is only the starting point. Cybersecurity also needs to understand why it is connected, what operational function it supports, which systems it should communicate with and what dependencies that connectivity creates. If the device has LTE or 5G connectivity, it could introduce communication paths outside the traditional OT network architecture, creating potential security risks.
In one case Black & Veatch observed, a utility installed a server that repeatedly attempted to communicate with an external system to perform time checks. Without sufficient context, cybersecurity teams had to determine whether that communication was expected and legitimate.
Consider a hypothetical example: an engineer wants to install a new recloser on a distribution feeder to protect a critical customer. The installation serves a legitimate operational need, but it also introduces new connections that must be understood and secured. The new unit also includes communication capabilities that introduce additional connectivity into the existing environment.
The cybersecurity team should know the device's tag number, location and IP address, but in reality, that information isn't enough. The cybersecurity team also needs to know which control system the device should communicate with, what information it should report, who can send it commands and what its normal communication patterns look like.
Without that context, an unexpected connection or command may be harder to recognize and investigate. The same missing information can make it difficult to design appropriate network access as more devices come online.
Managing Connectivity from the Start
When a device such as a recloser is added to a network, three things should happen:
- Understand the operational need. Why is the device being connected, what function does it serve, and what operations depend on it?
- Define how it should connect and operate. What systems does it need to communicate with, what commands and data exchanges are expected, and how should those connections be controlled?
- Determine how the device should be secured and monitored. Bring the appropriate teams together to determine the necessary segmentation, access controls, monitoring and ongoing ownership.
The information needed to manage a new connection often spans organizational boundaries. Engineering, operations, networking, maintenance, vendors and cybersecurity may each hold part of the picture. Bringing those perspectives together creates the shared understanding needed to design, secure and monitor the connection appropriately.
Today’s connectivity and digitization tools can deliver incredible efficiency when implemented effectively, but in many cases, that’s easier said than done.
A Better Methodology
The same connectivity that enables greater visibility, automation and access to information also changes the cybersecurity environment utilities must manage. The objective is not to prevent that connectivity, but to make sure it is intentional, understood and appropriately protected.
That starts with the operational need. What function is the connection enabling? Which assets and applications support it? What communications are required? What depends on them, and what could happen if those communications change or fail? Those requirements should inform the architecture, segmentation, access controls and monitoring.
Cybersecurity therefore needs to be part of the connectivity decision rather than something applied after the technical design is complete. Bringing operational requirements, architecture, asset context and cybersecurity together allows utilities to support modernization while making informed decisions about the risks that come with greater connectivity.
With this approach, shared understanding transforms device inventory into a practical foundation for managing cybersecurity. By making connectivity intentional, understood and appropriately protected, utilities can realize the benefits of modernization while managing the risks to reliable power delivery.






















