Original Publication Date: 11/17/2011
Updated Date: 02/27/2013
This article applies to BIG-IP 11.x. For information about other versions, refer to the following article:
You should consider using this procedure under the following condition:
You must meet the following prerequisite to use this procedure:
BIG-IP SSL Stacks
The BIG-IP SSL profiles have the ability to use ciphers from two different SSL stacks; the NATIVE stack is built into TMM, and the COMPAT stack, is based on the OpenSSL library. The NATIVE stack is an optimized SSL stack which can be used by the BIG-IP system to leverage hardware acceleration. F5 recommends using the NATIVE stack as it is suitable for most SSL connections.
In BIG-IP version 11.x, the SSL profiles only use ciphers from the NATIVE SSL stack. To use SSL ciphers from the COMPAT stack, you must manually configure the cipher string for the profile to COMPAT.
Default cipher list for SSL profiles
When configuring an SSL profile on the BIG-IP system, you can manually specify the ciphers available for SSL connections, or you can use the default cipher string, DEFAULT. The default cipher string only uses SSL ciphers from the NATIVE SSL stack. The DEFAULT cipher string for the SSL profiles is as follows:
11.2.1 through 11.3.0
NATIVE:!MD5:!EXPORT:!DES:!DHE:!EDH:@SPEED
This cipher string is defined as follows:
| Parameter | Definition |
| NATIVE | Use the optimized SSL stack that leverages hardware acceleration |
| !MD5 | Do not use MD5 ciphers |
| !EXPORT | Do not use EXPORT grade (weak) ciphers |
| !DES | Do not use DES ciphers |
| !DHE | Do not use DHE ciphers |
| !EDH | Do not use EDH ciphers |
| @SPEED | Order the cipher preference by speed |
11.0.0 through 11.2.0
NATIVE:!MD5:!EXPORT:!DES:@SPEED
This cipher string is defined as follows:
| Parameter | Definition |
| NATIVE | Use the optimized SSL stack that leverages hardware acceleration |
| !MD5 | Do not use MD5 ciphers |
| !EXPORT | Do not use EXPORT grade (weak) ciphers |
| !DES | Do not use DES ciphers |
| @SPEED | Order the cipher preference by speed |
F5 recommends using the DEFAULT cipher string for client and server SSL profiles. However, you can configure an SSL profile to use a custom cipher suite. By applying different profiles to different virtual servers, you can make client SSL virtual servers more or less permissive than others. For example, you can use this approach to allow only strong ciphers, thereby enforcing the PCI requirement for strong cryptography and eliminating Weak Supported SSL Ciphers Suite violations.
Configuring the SSL profile to use only TLSv1.2 compatible ciphers
Configuring the SSL profile to block a specific SSL cipher
Configuring the SSL profile to order SSL ciphers by strength
Configuring the SSL profile to block a specific SSL version
Configuring the SSL profile to use specific ciphers from the COMPAT SSL stack
Configuring the SSL profile to use ciphers from the NATIVE and COMPAT SSL stacks
Configuring the SSL profile to use only TLSv1.2 compatible ciphers
To configure an SSL profile to use only TLSv1.2 compatible ciphers using the Configuration utility, perform the following procedure:
Impact of procedure: Configuring the profile to use only TLSv1.2 will cause connection failure for clients that do not support TLS1.2.
tmsh create /ltm profile client-ssl <profile_name> ciphers TLSv1_2
Configuring the SSL profile to block a specific SSL cipher
To configure an SSL profile to block a specific cipher using the Configuration utility, perform the following procedure:
Impact of procedure: Configuring the profile to block a specific SSL cipher may cause certain client connections to fail.
tmsh create /ltm profile client-ssl <profile_name> ciphers DEFAULT:!AES128-SHA
Configuring the SSL profile to order SSL ciphers by strength
To configure the SSL profile to order SSL ciphers by strength, perform the following procedure:
Impact of procedure: Ordering SSL ciphers by strength may cause the virtual server to process fewer SSL transactions per second (TPS).
tmsh create /ltm profile client-ssl <profile_name> ciphers DEFAULT:@STRENGTH
Configuring the SSL profile to block a specific SSL version
To configure the SSL profile to block a specific SSL version, perform the following procedure:
Impact of procedure: Configuring the profile to block a specific SSL version may cause certain client connections to fail.
DEFAULT:!SSLv3
Note: Alternatively, to create an SSL profile to block SSLv3 using the tmsh utility, use the following syntax:tmsh create /ltm profile client-ssl <profile_name> ciphers DEFAULT:!SSLv3
Configuring the SSL profile to use specific ciphers from the COMPAT SSL stack
To configure the SSL profile to use specific ciphers from the COMPAT stack, perform the following procedure:
Impact of procedure: Configuring the profile to use ciphers from the COMPAT SSL stack may result suboptimal SSL performance for the virtual server.
COMPAT+DHE
Note: Alternatively, to create an SSL profile that allows DHE ciphers using the tmsh utility, use the following syntax:tmsh create /ltm profile client-ssl <profile_name> ciphers COMPAT+DHE
Configuring the SSL profile to use ciphers from the NATIVE and COMPAT SSL stacks
To configure the SSL profile to use ciphers from the NATIVE and COMPAT SSL stacks, perform the following procedure:
Impact of procedure: Configuring the profile to use ciphers from the NATIVE and COMPAT SSL stacks may result in low-encryption SSL connections.
COMPAT:NATIVE
Note: Alternatively, to create an SSL profile that allows ciphers from the NATIVE and COMPAT SSL stacks using the tmsh utility, use the following syntax:tmsh create /ltm profile client-ssl <profile_name> ciphers COMPAT:NATIVE