ICSA-16-313-01

Connecting devices to a network via Ethernet always entails the risk of unauthorized access to the network. Phoenix Contact recommends that users implement an adequate defense–in-depth networking architecture (including the following) for control systems where these devices are operating: Devices should not be exposed to public networks without the use of virtual private networks (VPNs) for remote access. Firewalls should be used for network segmentation or controller isolation. Available communication channels or ports not needed in the application should be turned off. Administrators and users should check whether the application offers any option of deactivating active communication channels (e.g., SNMP, FTP, BootP, DCP), or setting passwords to prevent third parties from unauthorized accessing the controller and modifying the system. Access to the devices should be limited to the fewest possible authorized personnel. Change standard or default passwords when first installing every component. Passwords should be changed in regular interval in order to reduce risks of becoming public. Passwords should have a maximum strength by the use of small and capital letters as well as numbers and special characters with a length of at least 10 characters. Conduct regular thread analyses to discover whether current measures meet the safety requirements. Install and maintain security software in order to defend new or recurring risks

Connecting devices to a network via Ethernet always entails the risk of unauthorized access to the network. Phoenix Contact recommends that users implement an adequate defense–in-depth networking architecture (including the following) for control systems where these devices are operating: Devices should not be exposed to public networks without the use of virtual private networks (VPNs) for remote access. Firewalls should be used for network segmentation or controller isolation. Available communication channels or ports not needed in the application should be turned off. Administrators and users should check whether the application offers any option of deactivating active communication channels (e.g., SNMP, FTP, BootP, DCP), or setting passwords to prevent third parties from unauthorized accessing the controller and modifying the system. Access to the devices should be limited to the fewest possible authorized personnel. Change standard or default passwords when first installing every component. Passwords should be changed in regular interval in order to reduce risks of becoming public. Passwords should have a maximum strength by the use of small and capital letters as well as numbers and special characters with a length of at least 10 characters. Conduct regular thread analyses to discover whether current measures meet the safety requirements. Install and maintain security software in order to defend new or recurring risks