Industrial control systems connect digital infrastructure to physical processes. A programmable controller or SCADA application can influence pumps, valves and other equipment, so a cybersecurity issue may affect more than data or network availability. A hybrid cyber range offers a way to examine these interactions in an isolated environment by combining virtual infrastructure with selected physical devices.
A water-distribution emulator provides a useful example of this approach. Its test environment models stages such as water collection, treatment, storage and consumption, while using physical sensors, actuators and controllers to represent parts of an operational system. For automation engineers and plant leaders, the central lesson is that realistic testing depends on more than reproducing network connections: the relationship between control logic, field signals and physical behavior matters too.
Why industrial systems need dedicated test environments
ICS and SCADA environments can be difficult to assess using conventional software testing alone. Their behavior depends on interactions among controllers, networks, operating procedures, people and the process being controlled. Timing, unexpected inputs or changes in one part of a system can affect other components. A test performed on isolated devices may therefore miss system-level effects.
Testing directly on production equipment also carries operational risk. An incorrect command or disruptive security test could interrupt a process or create physical consequences. A cyber range provides a controlled setting for investigating vulnerabilities, validating configurations and rehearsing response activities without intentionally exposing the live process to those tests.
Isolation is particularly important when a scenario includes faults, malicious traffic or system crashes. The test environment can be reset and reused, allowing teams to repeat scenarios and compare outcomes. This also creates a setting for training, where operators and security personnel can practice without affecting production assets.
Choosing a physical, virtual or hybrid cyber range
Cyber ranges generally use physical, virtual or hybrid components. A physical testbed can closely reproduce selected equipment and network characteristics, but may require more hardware and offer less flexibility. A virtual range can make it easier to create and change scenarios, though its performance may differ from that of physical equipment.
A hybrid cyber range combines these approaches. Virtual machines can represent servers and workstations, while physical devices reproduce components that are difficult to emulate convincingly, such as field sensors, actuators or control hardware. This makes it possible to explore both information-system behavior and selected physical responses within one test setup.
The right balance depends on the test objective. If a team needs to examine how a control sequence responds to changing sensor values, physical process interfaces may be important. If the focus is on network topology or application configuration, virtual components may be sufficient. Where traffic load or hardware performance is under examination, virtualization can also introduce limitations: shared processing resources and network bandwidth may influence results. Those effects should be considered when interpreting test outcomes.
Modeling a water-distribution process
In the described emulator, five vessels represent parts of a water system: an environmental source, a lake or collection stage, a purification stage, clean-water storage and a consumer. Water moves through the central process in one direction, from collection through treatment to storage. Pumps support movement where needed, while valves regulate flow and can interrupt supply.
The model uses two broad categories of field measurement:
- Physical measurements, including tank level and water flow, help represent how much water is present and how it moves through the process.
- Chemical measurements, such as pH, conductivity, dissolved oxygen and ion readings, represent water-quality parameters in the model.
Raspberry Pi boards interface with the sensors and actuators. They read field values and operate connected hardware, while a JACE 8000 controller acts as the supervisory controller in the design. The controller applies the system-level control logic rather than delegating process decisions to each field board. This separation provides a testable example of how field interfaces and supervisory control can be arranged.
Networking, SCADA and control logic
The emulator connects its controller and field boards over a local network and uses Modbus over TCP/IP for communication. In this arrangement, the controller collects values from the field devices and determines whether pumps or valves should be operated according to the configured logic. A dedicated network supports communication within the model; when designing any testbed, the network boundaries and connections to other environments should be deliberate.
Niagara Framework is used to build the SCADA functions, including monitoring, histories, alarms and remote access through a web interface. Its normalized data points provide a common way to represent values and states. Control components can be combined to implement logic, while histories can record values at configured intervals or when a point changes. These records can then be reviewed in graphical or tabular views.
Role-based permissions also separate user responsibilities in the example. A programmer can modify control logic, a manager can supervise and operate the system, an administrator can configure test scenarios, and a guest can view information without changing settings or issuing commands. This structure helps make the range useful for different activities while limiting access according to role.
Testing scenarios and interpreting results
A useful testbed represents not only the normal process but also the inputs and outputs that can change its behavior. In the water model, scenarios can vary the source conditions, simulate operator commands, represent consumer demand or introduce losses. Administrators can use such scenarios to assess how the control logic responds, including whether alarms are generated when an unexpected condition occurs.
Before drawing conclusions from a test, teams should check that the model represents the aspects relevant to the question. That includes documenting the system architecture, controller configuration, network layout and assumptions about the physical process. A simplified emulator can support focused testing, but it should not be treated as an exact replica of every operational condition.
Practical implications for industrial teams
A hybrid cyber range gives automation and security teams a controlled way to examine how cyber events and process behavior intersect. Its value depends on matching the testbed to the question: use physical components where their behavior is important, virtualize where flexibility is useful, and account for resource constraints that may affect results.
For plant managers, system integrators and operations leaders, the practical takeaway is to treat testbed design as part of the security work itself. A documented, isolated and repeatable environment can support vulnerability assessment, control-logic validation and staff training without placing production processes at the center of every experiment. It also creates a foundation for refining scenarios as the modeled system changes.
Access Official Technical PDF