The transition of industrial systems from passive monitoring to active control via IIoT has created a new vulnerability vector: the potential for control signal spoofing. While attackers previously could only read data, they can now send commands to stop a conveyor or alter the operating mode of critical equipment. For a critical infrastructure engineer, this means that every incoming signal must not only be delivered but also verified for source legitimacy.
Why IT security methods fail for critical OT equipment
Standard IT security methods, such as resource-intensive encryption protocols, are often inapplicable in an OT environment. According to NIST SP 800-82, system availability in operational technologies takes precedence over confidentiality. If a controller spends excessive time processing a secure packet, it may lead to a disruption of the technological process. Most legacy controllers lack the resources to handle modern cryptographic protocols, creating vulnerabilities for unauthorized control actions.
Architectural model for command verification: from sensor to actuator
The reliability of IIoT solutions is established during the architectural design phase of interactions between devices, edge nodes, and the cloud, as described in the AWS Well-Architected IoT Lens. Rather than attempting to secure every individual sensor, it is more effective to build a trusted perimeter at the edge gateway level. The edge node acts as a filter that verifies command integrity before transmitting it to the PLC, offloading the field controllers.
Control loop segmentation per ISA/IEC 62443 standards
The ISA/IEC 62443 series of standards is a fundamental basis for ensuring the security of industrial automation systems across more than 20 industries. A key method is network segmentation into zones and conduits, which allows for the isolation of control loops from the corporate network. Even in the event of an IT segment compromise, a physical barrier in the form of a conduit with strict filtering rules prevents unauthorized influence on actuators.
Ensuring message integrity
Instead of full channel encryption, which introduces critical latency, it is architecturally advisable to implement Message Integrity Checks (MIC). For storing signature keys on edge gateways, it is recommended to use Hardware Security Modules (HSM) or TPM, which eliminates the possibility of key replacement even if the gateway software is compromised.
Modernizing legacy systems
Specialists from the Intecracy Group technology alliance can assist with technology stack audits and the development of modernization roadmaps. This includes analyzing vulnerable components and integrating secure gateways for cyber-physical systems (AZIOT), allowing for the gradual transition of legacy equipment to modern security standards without halting production processes.
Architectural checklist for control command verification
- Is network segmentation implemented according to ISA/IEC 62443 zones and conduits?
- Is hardware isolation (TPM/HSM) used for signature keys?
- Are RBAC policies configured to limit control rights for specific actuators (e.g., via OPC UA)?
- Is Message Integrity Check (MIC) performed for critical commands?
- Have network latencies been considered when selecting cryptographic signature methods?
FAQ
How to implement command verification in IIoT without increasing network latency?
Use lightweight Message Integrity Check (MIC) mechanisms at the edge gateway level instead of full encryption for every packet.
Is network segmentation sufficient to protect against unauthorized PLC control?
Segmentation per ISA/IEC 62443 is a baseline, but it must be supplemented with command integrity checks and strict Role-Based Access Control (RBAC) for control interfaces.
How to ensure ISA/IEC 62443 compliance when working with legacy industrial equipment?
Use architectural isolation via modern security gateways that verify commands before sending them to legacy controllers.