ADC

Architecture overview

September 14, 2021

Contributed by:

The three entities that are part of a Citrix ADC-Entrust deployment are an Entrust nShield Connect module, a remote file server (RFS), and a Citrix ADC.

The Entrust nShield Connect is a network-attached hardware security module. The RFS is used to configure the HSM and to store the encrypted key files.

Hardserver, a proprietary daemon provided by Entrust, is used for communication between the client (ADC), the Entrust HSM, and the RFS. It uses the IMPATH secure communication protocol. A gateway daemon, called the Hardserver Gateway, is used to communicate between the Citrix ADC packet engine and the Hardserver.

Note: The terms Entrust nShield Connect, Entrust HSM, and HSM are used interchangeably in this documentation.

The following figure illustrates the interaction between the different components.

Entrust architecture overview

In a typical deployment, the RFS is used to securely store keys generated by the HSM. After the keys are generated, you can securely transfer them to the ADC and then use the GUI or command line to load the keys to the HSM. A virtual server on the ADC uses Entrust to decrypt the client key exchange to complete the SSL handshake. Thereafter, all the SSL operations are performed on the ADC.

Note: The terms keys and application key tokens are used interchangeably in this documentation.

The following figure illustrates the packet flow in the SSL handshake with the Entrust HSM.

Figure 1. SSL Handshake Packets Flow Diagram with Citrix ADC Using Entrust HSM

SSL handshake with Entrust

Note: The communication between the ADC and the HSM uses an Entrust proprietary communication protocol, called IMPATH.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Architecture overview

September 14, 2021

Contributed by:

September 14, 2021

Contributed by:

Architecture overview

In this article