The Security section
contains the policy setting for configuring session encryption and encryption
of logon data.
minimum encryption level
specifies the minimum level at which to encrypt session data sent between the
server and a user device.
For the Virtual
Delivery Agent 7.x, this policy setting can be used only to enable the
encryption of the logon data with RC5 128-bit encryption. Other settings are
provided only for backwards compatibility with legacy versions of XenApp and
For the VDA 7.x, encryption of session data is set using the basic
settings of the VDA's Delivery group. If Enable Secure ICA is selected for the
Delivery group, session data is encrypted with RC5 (128 bit) encryption. If
Enable Secure ICA is not selected for the Delivery group, session data is
encrypted with Basic encryption.
When adding this
setting to a policy, select an option:
- Basic encrypts
the client connection using a non-RC5 algorithm. It protects the data stream
from being read directly, but it can be decrypted. By default, the server uses
Basic encryption for client-server traffic.
- RC5 (128 bit) logon
only encrypts the logon data with RC5 128-bit encryption and the
client connection using Basic encryption.
- RC5 (40 bit)
encrypts the client connection with RC5 40-bit encryption.
- RC5 (56 bit)
encrypts the client connection with RC5 56-bit encryption.
- RC5 (128 bit)
encrypts the client connection with RC5 128-bit encryption.
The settings you
specify for client-server encryption can interact with any other encryption
settings in your environment and your Windows operating system. If a higher
priority encryption level is set on either a server or user device, settings
you specify for published resources can be overridden.
You can raise
encryption levels to further secure communications and message integrity for
certain users. If a policy requires a higher encryption level, Receivers using
a lower encryption level are denied connection.
SecureICA does not
perform authentication or check data integrity. To provide end-to-end
encryption for your site, use SecureICA with SSL/TLS encryption.
SecureICA does not
use FIPS-compliant algorithms. If this is an issue, configure the server and
Receivers to avoid using SecureICA.
SecureICA uses the RC5 block cipher as described in RFC 2040 for confidentiality. The block size is 64 bits (a multiple of 32-bit word units). The key length is 128 bits. The number of rounds is 12.