The Thales nShield Connect is an external HSM that is available for use with BIG-IP® systems. Because it is network-based, you can use the Thales nShield Connect solution with all BIG-IP platforms, including VIPRION® Series chassis and BIG-IP Virtual Edition (VE).
The Thales nShield Connect architecture includes a component called the Remote File System (RFS) that stores and manages the encrypted key files. The RFS can be installed on the BIG-IP system or on another server on your network.
The BIG-IP system is a client of the RFS, and all BIG-IP systems that are enrolled with the RFS can access the encrypted keys from this central location. The RFS helps automate the key distribution process, but you are not required to use RFS with this solution.
Only RSA-based cipher suites use the network HSM.
After you install the Thales nShield Connect client on the BIG-IP system, the keys stored in the Thales HSM and the corresponding certificates are available for use with Access Policy Manager® and Application Security Manager™.
For additional information about using Thales nShield Connect, refer to the Thales website:
Before you can use Thales nShield Connect with the BIG-IP® system, you must make sure that these requirements are in place:
Additionally, before you begin the installation process, make sure that you can locate these items on the installation DVD that ships with the Thales hardware unit:
The implementation process involves preparation of the Thales nShield Connect device.
Before you can set up the Thales nShield Connect components on a BIG-IP® system, you must obtain the Thales 64-bit Linux ISO CD and copy files from the CD to specific locations on the BIG-IP system using secure copy (SCP). F5 Networks has tested these integration steps with Thales security World Software for Linux 64bit v11.40. We expect later versions to be compatible. For questions about Thales components, consult your Thales representative.
|File to copy from the CD||Location to place file on BIG-IP|
nethsm-thales-rfs-install.sh --hsm_ip_addr=192.168.13.59 --rfs_interface=eth0
To use the Thales nShield Connect device with the BIG-IP system, you must first set up the Thales client on the BIG-IP system. For the enrollment to work properly, the IP address of the BIG-IP system must be a client of the networked HSM. You set up the IP address using the front panel of the nShield Connect device, or by pushing the client configuration. For details about how to add, edit, and view clients, refer to the Thales documentation.
If you are setting up the Thales client on a VIPRION® system, you run the configuration script only on the primary blade, and then the system propagates the configuration to the additional active blades.
nethsm-thales-install.sh --hsm_ip_addr=<nShield_Connect_device_IP_address> --rfs_ip_addr=<remote_RFS_server_IP_address> --rfs_username=<remote_RFS_server_username_for_SSH_login> --interface=<Interface_name_of_Thales_client_on_BIG-IP>
The following example sets up the client where the Thales nShield Connect device has an IP address of 192.168.13.59, the remote RFS has an IP address of 192.168.13.58, the user name for an SSH login to the RFS is root, and the Thales client interface is the management (eth0) interface:
nethsm-thales-install.sh --hsm_ip_addr=192.168.13.59 --rfs_ip_addr=192.168.12.58 --rfs_username=root --interface=eth0
nethsm-thales-install.sh --hsm_ip_addr=<nShield_Connect_device_IP_address> --rfs_interface=<local_RFS_server_interface>
The following example sets up the client where the Thales nShield Connect device has an IP address of 188.8.131.52 and the RFS is installed on the BIG-IP system using the eth0 interface:
nethsm-thales-install.sh --hsm_ip_addr=184.108.40.206 --rfs_interface=eth0
chmod 755 -R /opt/nfast/bin chown -R nfast:nfast /opt/nfast/kmdata/ chmod 700 -R /opt/nfast/kmdata/tmp/nfpriv_root chown -R root:root /opt/nfast/kmdata/tmp/nfpriv_root
Server: : serial number CB9E-745E-F901 A1D0-2DBE-AD98 5286-D07F-7601 mode operational