Introduction

This article is focused on providing clear and simple examples for the cipher string. They are based on different scenarios where you use the Transport Layer Security (TLS) protocol.

Recommendations for a cipher string

Scenarios

The cipher strings are based on the recommendation to setup your policy to get a whitelist for your ciphers as described in the Transport Layer Protection Cheat Sheet (Rule - Only Support Strong Cryptographic Ciphers). The latest and strongest ciphers are solely available with TLSv1.2, older protocols don't support them. Please find enclosed all supported protocols by the scenario.

We have not included any ChaCha20-Poly1305 ciphers, yet. One reason is that we haven't found various assessments yet, the other is that implementations of new ciphers may be more buggy.

Finally we have compiled the oldest versions of different client agents that are still compatible with a cipher string. We provide this information according to the ciphers and protocols supported by browsers, libraries, bots on the basis of ssllabs's list of user agent capabilities and tests on our own.

We have checked this thoroughly, but please accept that all data is provided without any warranty of any kind. The list of the oldest supported clients assumes that the server supports all ciphers by the scenario (Please contact the authors if you find any errors or if you can provide additional data).

The recommended cipher strings are based on different scenarios:

OWASP Cipher String 'A' (Advanced, wide browser compatibility, e.g. to most newer browser versions):

• Recommended if you control the server and the clients (e.g. by approvement), make sure to check the compatibility before using it.
• Includes solely the strongest Perfect Forward Secrecy (PFS) ciphers.
• Protocols: TLSv1.2 (and newer or better).
• Oldest known clients that are compatible: Android 4.4.2, BingPreview Jan 2015, Chrome 32/Win 7, Chrome 34/OS X, Edge 12/Win 10, Firefox 27/Win 8, Googlebot Feb 2015, IE11/Win 7 + MS14-066, Java8b132, OpenSSL 1.0.1e, Safari 9/iOS 9, Yahoo Slurp Jun 2014, YandexBot Sep 2014.

OWASP Cipher String 'B' (Broad compatibility to browsers, check the compatibility to other protocols before using it, e.g. IMAPS):

• Recommended if you solely control the server, the clients use their browsers and if you check the compatibility before using it for other protocols than https.
• Includes solely the strongest and stronger PFS ciphers.
• Protocols: TLSv1.2 (and newer or better).
• Oldest known clients that are compatible: Android 4.4.2, BingPreview Jan 2015, Chrome 30/Win 7, Chrome 34/OS X, Edge 12/Win 10, Firefox 27/Win 8, Googlebot Feb 2015, IE11/Win 7, IE 11/WinPhone 8.1, Java8b132, OpenSSL 1.0.1e, Opera 17/Win 7, Safari 5/iOS 5.1.1, Safari 7/OS X 10.9, Yahoo Slurp Jun 2014, YandexBot Sep 2014

OWASP Cipher String 'C' (Widest Compatibility, compatibility to most legacy browsers, legacy libraries (still patched) and other application protocols besides https, e.g. IMAPS):

• You may use this if you solely control the server, your clients use elder browsers and other elder libraries or if you use other protocols than https.
• Includes solely PFS ciphers.
• Be aware of additional risks and of new vulnerabilities that may appear are more likely than above.
• Plan to phase out SHA-1 and TLSv1, TLSv1.1 for https in middle-term.
• Protocols: TLSv1.2, TLSv1.1, TLSv1 (and newer or better).
• Oldest known clients that are compatible: Android 2.3.7/4.0.4, Baidu Jan 2015, BingPreview Dec 2013, Chrome 27/Win 7, Chrome 34/OS X, Edge 12/Win 10, Firefox 10.0.12 ESR/Win 7, Firefox 21/Win 7+Fedora 19, Googlebot Oct 2013, IE 7/Vista, IE 10/WinPhone 8.0, Java 7u25, OpenSSL 0.9.8y, Opera 12.15/Win 7, Safari 5/iOS 5.1.1, Safari 5.1.9/OS X 10.6.8, Yahoo Slurp Oct 2013, YandexBot May 2014

OWASP Cipher String 'D' (Legacy, widest compatibility to real old browsers and legacy libraries and other application protocols like SMTP):

• Take care, use this cipher string only if you are forced to support non PFS for real old clients with very old libraries or for other protocols besides https.
• Be aware of the existing risks (e.g. ciphers without PFS, ciphers with 3DES) and of new vulnerabilities that may appear the most likely.
• No not use WEAK ciphers based on 3DES e.g. (TLS_RSA_WITH_3DES_EDE_CBC_SHA, DES-CBC3-SHA)
• Never use even more INSECURE or elder ciphers based on RC2, RC4, DES, MD4, MD5, EXP, EXP1024, AH, ADH, aNULL, eNULL, SEED nor IDEA.
• PFS ciphers are preferred, except all DHE ciphers that use SHA-1 (to prevent possible incompatibility issues caused by the length of the DHparameter).
• Plan to move to 'A' for https or at least 'B' otherwise in middle-term.
• Protocols: TLSv1.2, TLSv1.1, TLSv1 (and newer or better).

Table of the ciphers (and their priority from high (1) to low (e.g. 18))

IANA, OpenSSL and other crypto libraries use slightly different names for the same ciphers.

This table lists the names used by IANA and by openssl in brackets []. Additional you can find the unambiguously hex values defined by IANA. Mozilla offers a larger cipher names correspondence table.

Remarks:

Elder versions of Internet-Explorer and Java do NOT support Diffie-Hellman parameters superior to 1024 bit. So the ciphers TLS_DHE_RSA_WITH_AES_256_CBC_SHA and TLS_DHE_RSA_WITH_AES_128_CBC_SHA were moved to the end to prevent possible incompatibility issues.

Other option: Delete this two ciphers from your list.

Examples for cipher strings

OpenSSL

How to use this Cipher Strings?

Inform yourself how to securely configure the settings for the services or hardware that you do use, e.g. BetterCrypto.org: Applied Crypto Hardening (DRAFT), Mozilla: Security/Server Side TLS.

We recommend to use one of the cipher strings described above.

Example configs

Apache

Cipher String 'B':

SSLProtocol +TLSv1.2                  # for Cipher-String 'A', 'B'
#SSLProtocol +TLSv1.2 +TLSv1.1 +TLSv1 # for Cipher-String 'C', 'D'
SSLCompression off
SSLHonorCipherOrder on
SSLCipherSuite 'DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256'
#add optionally ':!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:!ADH:!IDEA:!3DES'

Remarks:

• The cipher string is compiled as a whitelist of individual ciphers to get a better compatibility even with old versions of OpenSSL.
• Monitor the performance of your server, e.g. the TLS handshake with DHE hinders the CPU about 2.4 times more than ECDHE, cf. Vincent Bernat, 2011, nmav's Blog, 2011.
• Verify your cipher string using your crypto library, e.g. openssl using cipher string 'B':

openssl ciphers -V "DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256"
#add optionally ':!aNULL:!eNULL:!LOW:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:!ADH:!IDEA' to protect 
#older Versions of OpenSSL
#use openssl ciphers -v "..." for openssl < 1.0.1:

0x00,0x9F - DHE-RSA-AES256-GCM-SHA384   TLSv1.2 Kx=DH     Au=RSA  Enc=AESGCM(256) Mac=AEAD
0x00,0x9E - DHE-RSA-AES128-GCM-SHA256   TLSv1.2 Kx=DH     Au=RSA  Enc=AESGCM(128) Mac=AEAD
0xC0,0x30 - ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH   Au=RSA  Enc=AESGCM(256) Mac=AEAD
0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH   Au=RSA  Enc=AESGCM(128) Mac=AEAD
0x00,0x6B - DHE-RSA-AES256-SHA256       TLSv1.2 Kx=DH     Au=RSA  Enc=AES(256)    Mac=SHA256
0x00,0x67 - DHE-RSA-AES128-SHA256       TLSv1.2 Kx=DH     Au=RSA  Enc=AES(128)    Mac=SHA256
0xC0,0x28 - ECDHE-RSA-AES256-SHA384     TLSv1.2 Kx=ECDH   Au=RSA  Enc=AES(256)    Mac=SHA384
0xC0,0x27 - ECDHE-RSA-AES128-SHA256     TLSv1.2 Kx=ECDH   Au=RSA  Enc=AES(128)    Mac=SHA256

CAUTION: You must not use legacy versions of OpenSSL if you use this cipher string! We strongly recommend to verify if it works!

Related Articles

• OWASP: Transport Layer Protection Cheat Sheet.
• BetterCrypto.org: Applied Crypto Hardening (DRAFT).
• Mozilla: Security/Server Side TLS.

Authors and Primary Editors

Torsten Gigler - torsten.gigler@owasp.org

Achim Hoffmann - achim@owasp.org