Siemens RX1500 User Manual page 39

RUGGEDCOM ROX II
User Guide
• SSL and SSH keys are accessible to users who connect to the device via the serial console. Make sure to take
appropriate precautions when shipping the device beyond the boundaries of the trusted environment:
▪ Replace the SSH and SSL keys with throwaway keys prior to shipping.
▪ Take the existing SSH and SSL keys out of service. When the device returns, create and program new keys
for the device.
• Restrict physical access to the device to only trusted personnel. A person with malicious intent in possession
of the flash card could extract critical information, such as certificates, keys, etc. (user passwords are protected
by hash codes), or reprogram the card.
• Control access to the serial console to the same degree as any physical access to the device. Access to
the serial console allows for potential access to BIST mode, which includes tools that may be used to gain
complete access to the device.
• Only enable the services that will be used on the device, including physical ports. Unused physical ports could
potentially be used to gain access to the network behind the device.
• If SNMP is enabled, limit the number of IP addresses that can connect to the device and change the
community names. Also configure SNMP to raise a trap upon authentication failures. For more information,
refer to Section 5.11, "Managing
• Limit the number of simultaneous Web Server, CLI, SFTP and NETCONF sessions allowed.
• If a firewall is required, configure and start the firewall before connecting the device to a public network. Make
sure the firewall is configured to accept connections from a specific domain. For more information, refer to
Section 5.17, "Managing Firewalls"
• Configure remote system logging to forward all logs to a central location. For more information, refer to
Section 3.9, "Managing
• Configuration files are provided in either NETCONF or CLI format for ease of use. Make sure configuration files
are properly protected when they exist outside of the device. For instance, encrypt the files, store them in a
secure place, and do not transfer them via insecure communication channels.
• It is highly recommended that critical applications be limited to private networks, or at least be accessible only
through secure services, such as IPsec. Connecting a ROX II device to the Internet is possible. However,
the utmost care should be taken to protect the device and the network behind it using secure means such as
firewall and IPsec. For more information about configuring firewalls and IPsec, refer to
Firewalls" and Section 5.28, "Managing IPsec
• Management of the certificates and keys is the responsibility of the device owner. Before returning the device
to Siemens Canada Ltd. for repair, replace the current certificates and keys with temporary throwaway
certificates and keys that can be destroyed upon the device's return.
• Be aware of any non-secure protocols enabled on the device. While some protocols, such as HTTPS, SSH
and 802.1x, are secure, others, such as Telnet and RSTP, were not designed for this purpose. Appropriate
safeguards against non-secure protocols should be taken to prevent unauthorized access to the device/
network.
• Prevent access to external, untrusted Web pages while accessing the device via a Web browser. This can
assist in preventing potential security threats, such as session hijacking.
• Use the latest Web browser version compatible with ROX II to make sure the most secure Transport Layer
Security (TLS) versions and ciphers available are employed.
• Make sure the device is fully decommissioned before taking the device out of service. For more information,
refer to Section 3.7, "Decommissioning the
• Configure port security features on access ports to prevent a third-party from launching various attacks that can
harm the network or device. For more information, refer to
Security Recommendations
SNMP".
Logs".
Tunnels".
Device".
Section 3.18.3, "Configuring Port
Chapter 1
Introduction
Section 5.17, "Managing
Security".
7