We're here to help.

F5 Big-IP TLS Termination Guide for Butterfly Cloud Connector

Introduction

SSL/TLS termination (offloading) relieves an Application or Web server of the processing burden of encrypting and/or decrypting traffic sent via TLS or SSL. Note that the SSL standard has been replaced by TLS as the encryption mechanism for most web based communications. Any use of “SSL” in this guide is strictly for convenience and is, in fact, referring to TLS.

When a DICOM server system is not capable of receiving TLS-encrypted DICOM data, the TLS termination capability of a F5 Big-IP can be used to decrypt/encrypt the data. Once the connection is terminated at the Big-IP, the unencrypted DICOM data is forwarded to the designated DICOM server.

The F5 Big-IP provides 2 ways in which SSL/TLS is processed. These are:

  • Client SSL – F5 decrypts the encrypted traffic inbound from the client.

  • Server SSL – Traffic is re-encrypted by the F5 then routed onto the backend servers.

This guide will focus on Client SSL exclusively.

Figure 1. DICOM-TLS Termination Using F5 Big-IP

DICOM-TLS Termination Using F5 Big-IP

 

Prerequisites

In most environments, the F5 Big-IP is located in the DMZ portion of the network. In order for the device to be able to process the DICOM-TLS traffic; the Internet-facing firewall must be configured to permit traffic on the port(s) that the ADC has been configured to listen on.

  1. Ensure that you have access to Butterfly Cloud (cloud.butterflynetwork.com) as an Administrator, so that you can configure the PACS connection. The PACS configuration screen will provide you with the digital certificate-key pair that will be used with the virtual servers on the F5 Big-IP.

    • A public certificate is not required for the DICOM-TLS encryption.  We are only using the certificate for encryption/decryption, not for end-point trust and validation.

  2. Note the external (Internet-facing) IP address of the firewall or F5 Big-IP.

  3. For the purposes of this document, we will be creating a TLS termination Virtual Server on the F5 Big-IP.

    • A DICOM Store virtual server will be configured to use port 2761.

    • (Optional) A DICOM Worklist virtual server will be configured to use port 2762.

  4. Ensure that the external firewall permits TCP traffic from the Internet to the above ports used by the Virtual Servers. The source IP address of Butterfly Cloud is 34.203.166.92.

  5. Login access to the F5 Big-IP GUI.

 

Set Up Connection from Butterfly Cloud and Download Digital Certificate

  1. Log in to Butterfly Cloud using your Browser - ensure that your user role in Butterfly Cloud is that of Administrator.

  2. Navigate to the DICOM Configuration menu. Click your username in the upper right of the window and select Organization Settings.

    Org_Settings_2.png
  3. Select the Connectivity tab and click the ‘+ Add’ option next to Connections to create a new TLS end-point that will be used with your DICOM integration.

    New_Connectivity_Menu.png
  4. Proceed to enter all of the necessary DICOM connection parameters.

    Connection_Parameters.png
    1. Name = Friendly name for the Connection.

    2. In the 'Security' section - set TLS to 'Active' and select the 'Generate' option.

    3. Select the PEM download format, and click 'Download'. Ensure that you receive 2 files: Butterfly_SCP_Cert.pem and Butterfly_SCP_key.pem

      1_-_Cert_Download.png
      1. The 2 files will be used in a later step; during the configuration of your TLS termination.

    4. In the 'SCP' section - Enter the Host information, DNS name or IP of your TLS end-point.

      1. Please note that the IP address must be a public IP that can be accessible from Butterfly Cloud to your network. This will typically be the IP address of your network firewall, router, or TLS termination device. Non-routable/private IP addresses are not valid.

  5. Click Save, then click on the Connectivity tab to create the DICOM Integration.

 

Configure the DICOM Integration and Associate the TLS Connection

  1. After clicking on the Connectivity tab, click the ‘+ Add’ option next to Integrations and select PACS/VNA.

    Add_PACS_VNA.png
  2. Give your PACS/VNA a friendly Name, and select to associate it with the TLS Connection created in Setup Connection from Butterfly Cloud and Download Digital Certificate.

    NAME_PACS.png
  3. Proceed to enter all of the necessary DICOM integration parameters.

    DICOM_Parameter_Fields.png
    1. SCU - Calling AET = The source AE Title of Butterfly Cloud (typically ‘BUTTERFLY’).

    2. SCP - AET = the AE Title of your DICOM destination.

    3. Enter a Port that you will need to forward from your firewall or router to the computer hosting the F5 Big-IP software.

      1. Port 2761/TCP is typically used for DICOM-TLS.

      2. Port 2762/TCP may be used in addition if DICOM Modality Worklist will be used.

    4. Please note that the port that is entered here is the public-facing port that is exposed by your TLS termination point.

  4. Set the Compression level of the DICOM Images and Cine Loop as required or preferred. The settings above are typical. Select ‘Save Configuration’ to complete the setup.

 

F5 Big-IP TLS Termination Setup

Configuring SSL termination consists of 4 steps:

  1. Import the Butterfly SSL Certificate and Key

  2. Configure the client SSL-client profile

  3. Configure the Server Pool

  4. Configure the Virtual Server

 

Import the SSL Certificate and Key

  1. Go to ‘System ›› Certificate Management: Traffic Certificate Management: 'SSL Certificate List'.

  2. Select Import.

    Import.png
  3. Select 'Certificate' Import Type.

  4. Enter the Certificate Name (e.g. Butterfly_SCP_Cert.pem).

  5. Upload the certificate within the Certificate Source section. The certificate file was previously generated on Butterfly Cloud.

  6. Click Import.

  7. Repeat the process (above) to import the Key.

  8. Select ‘Key’ Import Type.

  9. Enter the Key Name (e.g. Butterfly_SCP_Key.pem ).

  10. Security Type should be defaulted to ‘Normal’.

  11. Upload the key within the Key Source section. The key file was previously generated on Butterfly Cloud.

  12. Click Import.

  13. SSL Certificate List should appear similar to below, when complete.

    Traffic_Cert_Management.png
 

Configure the SSL Profile

Next, we will need to configure the SSL Client profile.

  1. Go to ‘Local Traffic ›› Profiles: SSL: 'Client’

  2. Select Create.

    Create.png
  3. Within the General Properties enter the Name (e.g. Butterfly-TLS) and select the Parent Profile as clientssl and check mark Custom.

  4. Within the Configuration section select the Certificate and Key.

  5. Click Finished.

 

Configure the Server Pool

This step defines the server(s) to which the Big-IP Virtual Server (Step 4) will send traffic after it has terminated TLS.  In situations where you have one (1) DICOM destination (most customer sites) then you will have a Pool with 1 member server only.

Note

Setting the Health Monitor to ‘tcp_half_open’ will enable a half-open TCP monitor. It is recommended to use this setting due to observed problems with certain vendor’s DICOM services when monitored using a full-open TCP connection.

  1. Go to ‘Local Traffic ›› Pools: 'Pool List’.

  2. Select Create.

    Server_Pool.png
  3. Within the Configuration enter the Name (e.g. DICOM-Store-Server-Pool) and select the Health Monitors (tcp_half_open).

  4. In Resources - Add member servers to the Pool as required.

  5. Click Finished.

    Configured_Server_Pool.png
 

Configure the Virtual Server

  1. Go to ‘Local Traffic ›› Virtual Servers: Virtual Server List’.

  2. Select Create.

    Create_2.png
  3. Within the General Properties enter the Name (e.g. Butterfly-TLS-DICOM-Store) and Destination Address and Service Port.

    1. This is the (virtual) IP address and port that you are defining for this Virtual Server. Your firewall will need to permit traffic to this IP/port.

      TCP.png
  4. Within the Configuration section >> SSL Profile (Client), select the previously created profile (Butterfly-TLS).

    Butterfly-TLS.png
  5. SSL Profile (Server) should be blank.

  6. In a one-armed Big-IP configuration (single interface), ensure that Source Address Translation is set to Auto Map.

  7. Under Resources >> Default Pool, select the previously created Server Pool (DICOM-STore-Server-Pool).

  8. Click Finished.

    Virtual_Servers.png
 

Setup Complete

Repeat Configure the Server Pool and Configure the Virtual Server if you need to set up another TLS Termination - Virtual Server for your DICOM Modality Worklist.

Note

  • If your PACS/VNA is not operating in promiscuous mode, then you will need to add the Butterfly Cloud AE title as an approved DICOM source.

  • Please be aware that the PACS will see the Internal IP of the F5 Big-IP as the source of DICOM data from Butterfly Cloud.

 

Verify the Connection from Butterfly Cloud

  1. Switch back to Butterfly Cloud in the Browser.

  2. Navigate to the integrations menu. Click your username in the upper right of the window and select Organization Settings.

    Org_Settings.png
  3. Select the Connectivity tab and click the ‘...’ next to the newly created DICOM integration. Select the Echo option to perform a DICOM C-ECHO from Butterfly Cloud.

    Echo.png
  4. Click Echo, then Click on ‘Echo’ again in the upper right of the pop-up menu. This triggers a new  DICOM C-ECHO; please verify the output is similar to below.

    Echo_Settings.png
  5. Congratulations - you have setup an encrypted DICOM-TLS connection to your DICOM destination.

 

(Optional) - Automatic Forwarding to DICOM Storage

  1. To automatically send any studies saved to a Butterfly Cloud folder to your DICOM end-point, you can associate it with an Archive.

  2. Select the Archive folder that you would like to associate with the DICOM connection.  Select Archive Settings.

    Archive_Settings.png
  3. Choose the DICOM Storage location to associate with the Archive folder.

    PACS_Assignment.png
  4. Now any study saved to this folder (using the Butterfly iQ App) will automatically forward to the chosen DICOM destination.

 
 
Was this article helpful?
0 out of 0 found this helpful
Thank you for your feedback

We’re sorry this didn’t answer your question. We’re here to help. Contact us