Secure by default: Use cases and security context 

PLCnext Technology is supporting different security use cases. There are PLCnext Control devices that are equipped with Security Profile and devices that are secure by default. Check which device you are using in the PLCnext Control topic.

1. A secure by default PLCnext Technology device is an IEC 62443-4-1/4-2 certified component:
   • Security context described in this PLCnext Technology ‑ Security Info Center must fit the required automation system use cases.
   • IEC 62443-3-3 and IEC 62443-2-4 system design and installation/maintenance processes are supported. 
   • Centralized security functions like Device and Update Management (DaUM), logging, backup and restore or PKI. Depending on the system security concept, these centralized security functions might be located in the Network Security/Service Management zone (IT) or in the System Integrity/Manufactoring zone (OT).
2. Security is an overall system design requirement, and is ensued by the system design:
   • Check your individual security automation system use cases.
   • Perform a risk and threat analysis and design sufficient security measures.
   • Based on the risk and threat analysis of your automation system, you can activate or deactivate additional security features. E.g.: User Management, Certificate Authority, Firewall, Syslog, etc.
   • Make sure that the device continues to meet the necessary security requirements even after your own configurations.
3. Consider the general security instructions as described in the Industrial Security application note (AH EN INDUSTRIAL SECURITY).

PLCnext Technology secure-by-design features

PLCnext Technology is developed according to the secure-by-design procedures. It is certified according to IEC 62443-4-1 and IEC 62443-4-2. 
To build an automation solution with PLCnext Technology based on the IEC 62443-4-1/4-2 certification, the definitions described in this PLCnext Technology ‑ Security Info Center must be fulfilled.

The following features are building the base of the PLCnext Technology Security.

Hardware measures

• Secure boot with recovery system (depending in part on the controller model) 
• TPM-protected Phoenix Contact device certificate 
• Network segmentation by independent interfaces
• Use of an external SD card with encryption

Firmware measures

• Basing on Yocto Linux with secure-released components and automatic vulnerability supervision
• Secure communication via TLS 1.2, TLS 1.3, HTTPS, OPC UA®, SFTP, SSH, VPN
• User Manager supporting roles, permissions, credentials, and LDAP connection
• Certificate store for manufacturers, system integrators, and asset owners (locally or via Device and Update Management)
• Firewall with management of different interfaces, levels for chains and rules
• Syslog-ng for secure message management and central storage
• Time synchronization via NTP
• Backup and restore locally or via Device and Update Management (DaUM)
• Firmware update locally or via Device and Update Management (DaUM)