Secure communication drivers
- Last UpdatedNov 11, 2025
- 1 minute read
In an ICS context, the control system might not have direct control over remote devices, PLCs, or RTUs. Communication drivers, however, can be controlled and secured as part of the ICS software.
Individual communication drivers require specific security configuration action items. Refer to Security configuration for communication drivers for detailed guidance. Text and detailed linked references from the communication drivers documentation follow.
Secure communication drivers
The table below lists the security areas that you need to configure for Communication Drivers and the details of the section(s) in this guide that provide the corresponding instructions.
|
Security area(s) |
Security topic(s) |
Summary |
|---|---|---|
|
Encrypting SuiteLink communication for secure connection. |
You can encrypt SuiteLink communication between a SuiteLink server and a SuiteLink client. |
|
|
Enabling security in the communication. |
Configure the System Management Server |
Incorporates security measures, including support for the TLS 1.2 protocol for secure encrypted communications between nodes, single sign on (SSO), and certificate management. |
|
Establishing secure connection with MQTT Broker |
Incorporates security measures, including support for the TLS 1.3 protocol for secure encrypted communications between MQTT Broker and MQTT Communication Driver. |
|
|
Authenticating the Connection using SNMP V3. |
Allows you to configure the security settings for every station. |
|
|
Setting the OPC UA connection security parameters: |
Allows you to update Security Policy, Security Message Mode, and User Credentials. |