Industrial Cybersecurity

Protecting production starts with knowing who controls it
Industrial cybersecurity protects operational technology (OT) assets that monitor and control physical processes against cyber risks. The scope includes PLCs, operator panels, SCADA, engineering workstations, motor drives and their networks. Industrial control systems (ICS) form an important part of the broader OT environment.
The objective extends beyond preventing file theft. Unauthorised program changes, incorrect setpoints, lost operator visibility or interrupted industrial communication can cause production losses, quality problems and physical hazards. In energy, water, chemical and manufacturing facilities, protection must consider people, processes, equipment and information together.
How does OT security differ from protecting office computers?
A restart that is acceptable in an office can stop an operating furnace or filling line. In OT, availability, integrity and confidentiality requirements must be assessed alongside process safety and continuity. Their priority is not identical at every facility; the effects of security controls on latency, communication and control cycles require evaluation.
Long equipment lifetimes, legacy operating systems and limited device resources require measures suited to the plant. Cybersecurity does not replace safety functions such as safety relays or emergency stopping. The programs, access paths and change privileges associated with these functions also belong in the cyber risk assessment.
Start with an inventory and the actual risks
An asset inventory should record firmware versions, network addresses, physical locations, responsible personnel, backups and maintenance connections, as well as makes and models. Identify communication relationships from sensors to gateways and higher-level systems. Using Ethernet or assigning a private IP address does not establish that a device is secure.
Ask what would happen if a device were compromised. Incorrect pump operation, a changed temperature setpoint and a suppressed alarm can have different consequences. Risk is not determined by a vulnerability score alone: consider exposure, physical consequences, existing controls and recovery options. Continuously connected IoT devices and forgotten service modems must also appear in the inventory.
Segment networks and restrict communication paths
Prevent uncontrolled access between IT and OT networks. Separate production cells, engineering workstations, servers and external access points according to their requirements. In the IEC 62443 approach, zones group assets with common security requirements, while conduits represent controlled communication connections between zones.
In a suitable architecture, an office reporting system can receive production data through an industrial DMZ rather than connecting directly to the control network. Firewall rules should restrict sources, destinations, protocols, directions and required services. Creating VLANs alone does not provide adequate protection without access enforcement. Restricted data flow requires closing unnecessary connections and documenting the communication that is needed.
How should remote maintenance and privileges be managed?
Design controlled remote access instead of exposing PLC or HMI interfaces directly to the internet. Suitable solutions use a maintained access gateway, a VPN, multi-factor authentication (MFA) and a jump server. Establishing a VPN connection does not justify granting unrestricted access to the entire production network.
Use individual accounts, least privilege, time-limited service access and session records. Where an older PLC cannot support MFA directly, enforce it at the access gateway. Disable unnecessary access after the work and review contractor accounts. PLC system security also requires management of cabinet access, programming computers, USB devices and access to backup files.
A communication protocol does not automatically provide security
Classic implementations of the Modbus family, particularly traditional Modbus/TCP connections, should not be assumed to provide built-in encryption or strong authentication. Modbus Security is a separate approach that adds TLS and certificate-based authentication; both endpoints require compatible support. Assess the functional capabilities of protocols such as EtherNet/IP and Modbus TCP separately from their cybersecurity capabilities.
The OPC UA security model provides mechanisms for application identity, user permissions, message signing and encryption. Appropriate security policies, certificate trust lists and user permissions still require configuration. The presence of OPC UA does not prove that secure settings are enabled. Certificate expiry, private-key protection and change records must be managed throughout operation.
Plan patches and changes around production requirements
Apply firmware, operating-system and security-software updates using vendor compatibility checks, testing, maintenance windows and a rollback plan. OT patch management requires more than either installing every update without control or neglecting a legacy system indefinitely. Where immediate patching is impractical, document compensating controls such as restricted access and network isolation, together with their justification.
Active vulnerability scanning, restarts or intensive monitoring can disrupt some older devices. Passive network monitoring and existing logs often provide a suitable starting point; plan active testing around vendor guidance and operating conditions. Maintain approved change management for PLC programs, drive parameters and network rules.
Being able to restore matters as much as making backups
Protect PLC source projects, HMI applications, recipes, drive parameters, network-device configurations and required licence information. Keep some backups offline or immutable, beyond an attacker's ability to alter them using the same compromised privileges. Having a backup file does not establish that the system can be rebuilt. Test restoration using compatible software, hardware and authorised access.
RTO describes the target recovery time; RPO describes the acceptable data-loss window. Define these targets around process needs as part of resource availability planning. For timely incident response, establish responsibilities, communication channels, safe isolation conditions and return-to-service criteria in advance. Disconnecting a running plant without assessing the consequences can also create process risks; coordinate intervention with operations and safety personnel.
What does the IEC 62443 approach cover?
The IEC 62443 standards family addresses industrial automation and control system security throughout the lifecycle. 62443-3-2 covers security risk assessment and system design, while 62443-3-3 addresses system security requirements. IEC 62443-4-1 concerns secure product development, and IEC 62443-4-2 addresses technical security requirements for components.
Define the responsibilities of asset owners, integrators, maintenance providers and product manufacturers together. Certification of one component does not secure an entire incorrectly configured plant. A cybersecurity level is a different concept from SIL or PL. Practical protection depends on suitable products, a sound architecture, competent personnel and sustained operating discipline.
Editor's note: “This machine is not connected to the internet” is insufficient on its own. A maintenance laptop, USB drive, second network adapter or subsequently installed modem can create another access path. Verify the actual separation using the connection diagram and real working practices. Begin by identifying assets and access paths, reducing privileges and preparing backups that can actually be restored.
Related cybersecurity topics
Secure product development lifecycle
Technical security of industrial components
FR 6: timely response to events
Related topics in other categories
Industrial communication systems
Motor drives and control parameters
Sensors and field measurements
References
NIST SP 800-82 Rev. 3: Guide to Operational Technology Security (2023, final)
IEC 62443-3-2: Security risk assessment for system design
ISA: ISA/IEC 62443 Series of Standards
ASD / ACSC: Industrial control systems — Remote access protocol
OPC Foundation: OPC UA Part 2 — Security Model
Modbus Organization: Modbus Security protocol
Source status, 17 October 2026: NIST Rev. 3 is a final publication; the Rev. 4 initial public draft is not yet a final publication.