TLS Cipher String Cheat Sheet - Revision history

Dominique RIGHETTO: Point to the official site

2019-07-15T14:47:55Z

Point to the official site

Thunder-Son: Migration to GitHub

2019-02-14T14:41:54Z

Migration to GitHub

Show changes

Peter Mosmans: Fix multiple typos

2018-09-30T11:09:48Z

Fix multiple typos

Jmanico at 17:24, 29 September 2018

2018-09-29T17:24:51Z

Dominique RIGHETTO: Add the CS to the official list of CS

2018-09-29T09:21:02Z

Add the CS to the official list of CS

T.Gigler: Removed 'At a glance: Hardening...', added 'How to use this Cipher Strings?'

2017-11-01T22:14:55Z

Removed 'At a glance: Hardening...', added 'How to use this Cipher Strings?'

T.Gigler: Cipherstring 'A+', 'A', 'B': Added oldest known clients that are compatible

2017-09-29T14:50:52Z

Cipherstring 'A+', 'A', 'B': Added oldest known clients that are compatible

T.Gigler: editorial change

2017-09-28T22:42:37Z

editorial change

T.Gigler: editorial changes: Typo

2017-09-28T22:40:32Z

editorial changes: Typo

T.Gigler: editorial changes: Typos

2017-09-28T22:29:03Z

editorial changes: Typos

← Older revision		Revision as of 14:47, 15 July 2019
Line 4:		Line 4:
	The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!		The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!

−	Please visit [https://~~github~~.~~com/OWASP/CheatSheetSeries/blob/master~~/cheatsheets/TLS_Cipher_String_Cheat_Sheet.md TLS Cipher String Cheat Sheet] to see the latest version of the cheat sheet.	+	Please visit [https://cheatsheetseries.owasp.org/cheatsheets/TLS_Cipher_String_Cheat_Sheet.html TLS Cipher String Cheat Sheet] to see the latest version of the cheat sheet.

@@ Line 11: / Line 11: @@
 =Recommendations for a cipher string=
 ==Scenarios==
-The cipher strings are based on the recommendation to setup your policy to get a whitelist for yours ciphers as described in the <u>[[Transport_Layer_Protection_Cheat_Sheet#Rule_-_Only_Support_Strong_Cryptographic_Ciphers|Transport Layer Protection Cheat Sheet (Rule - Only Support Strong Cryptographic Ciphers)]]</u>. 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 senario.<br>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.<br>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 <u>[https://www.ssllabs.com/ssltest/clients.html ssllabs's list of user agent capabilities]</u> and tests on our own. We have checked this thoroughly, but please accept that all data is provided without any warranty of any kind (Please contact the authors if you find any errors or if you can provide additional data).
+The cipher strings are based on the recommendation to setup your policy to get a whitelist for your ciphers as described in the <u>[[Transport_Layer_Protection_Cheat_Sheet#Rule_-_Only_Support_Strong_Cryptographic_Ciphers|Transport Layer Protection Cheat Sheet (Rule - Only Support Strong Cryptographic Ciphers)]]</u>. 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.<br>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.<br>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 <u>[https://www.ssllabs.com/ssltest/clients.html ssllabs's list of user agent capabilities]</u> and tests on our own. We have checked this thoroughly, but please accept that all data is provided without any warranty of any kind (Please contact the authors if you find any errors or if you can provide additional data).
-The recommened cipher strings are based on different scenarios:
+The recommended cipher strings are based on different scenarios:
 * <b>OWASP Cipher String 'A+'</b> (Advanced+, limited compatibility, e.g. to more recent browser versions)
 :* Recommended if you control the server and the clients (e.g. by approvement) and if you check the compatibility before using it

@@ Line 3: / Line 3: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 = Introduction  =
@@ Line 153: / Line 148: @@
 <b>CAUTION</b>: You need a newer version of OpenSSL to use this cipher string!<br/>
-<br/><br/>
+<br/>
 =Related Articles=
@@ Line 161: / Line 156: @@
 * <u>[https://wiki.mozilla.org/Security/Server_Side_TLS  Mozilla: Security/Server Side TLS]</u>
-<br/><br/>
+<br/>
 = Authors and Primary Editors  =
@@ Line 167: / Line 162: @@
 {{Template:Contact | name = Achim Hoffmann | email =achim@owasp.org | username = Achim}}<br/>
 == Other Cheatsheets ==

← Older revision		Revision as of 09:21, 29 September 2018
Line 172:		Line 172:
	{{Cheatsheet_Navigation_Body}}		{{Cheatsheet_Navigation_Body}}

−	~~<!-----~~[[Category:Cheatsheets]]	+	[[Category:Cheatsheets]]
−	~~[[Category:OWASP Best Practices]] ----->~~

@@ Line 119: / Line 119: @@
 | style="font-size: 119%;"| <b>Legacy (C-)</b>              || 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:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA
 |}
-= At a glance: Hardening of other parts of the configuration of TLS/SSL for web servers =
+= 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. <u>[https://bettercrypto.org BetterCrypto.org: Applied Crypto Hardening (DRAFT)]</u>, <u>[https://wiki.mozilla.org/Security/Server_Side_TLS  Mozilla: Security/Server Side TLS]</u>. We recommend to use one of the cipher strings described above.

@@ Line 16: / Line 16: @@
 =Recommendations for a cipher string=
 ==Scenarios==
-The cipher strings are based on the recommendation to setup your policy to get a whitelist for yours ciphers as described in the <u>[[Transport_Layer_Protection_Cheat_Sheet#Rule_-_Only_Support_Strong_Cryptographic_Ciphers|Transport Layer Protection Cheat Sheet (Rule - Only Support Strong Cryptographic Ciphers)]]</u>. The latest and strongest ciphers are solely available with TLSv1.2, older protocols don't support them.<br>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.
+The cipher strings are based on the recommendation to setup your policy to get a whitelist for yours ciphers as described in the <u>[[Transport_Layer_Protection_Cheat_Sheet#Rule_-_Only_Support_Strong_Cryptographic_Ciphers|Transport Layer Protection Cheat Sheet (Rule - Only Support Strong Cryptographic Ciphers)]]</u>. 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 senario.<br>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.<br>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 <u>[https://www.ssllabs.com/ssltest/clients.html ssllabs's list of user agent capabilities]</u> and tests on our own. We have checked this thoroughly, but please accept that all data is provided without any warranty of any kind (Please contact the authors if you find any errors or if you can provide additional data).
 The recommened cipher strings are based on different scenarios:
@@ Line 22: / Line 22: @@
 :* Recommended if you control the server and the clients (e.g. by approvement) and if you check the compatibility before using it
 :* Includes solely the strongest perfect forward secrecy (PFS) ciphers
 :* Protocols: TLSv1.2 (and newer or better)
 * <b>OWASP Cipher String 'A'</b> (Advanced, wider compatibility, e.g. to most newer browser versions)
 :* Recommended if you control the server and the clients (e.g. by approvement) if the 'A+' string does not work, make sure to check the compatibility before using it
 :* includes solely the strongest and stronger PFS ciphers
 :* Protocols: TLSv1.2 (and newer or better)
 * <b>OWASP Cipher String 'B'</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
@@ Line 33: / Line 35: @@
 :* 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)
 * <b>OWASP Cipher String 'C'</b> (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

@@ Line 120: / Line 120: @@
 * Disable compression on TLS/SSL level
 * Check the configuration for all virtual hosts
-* If you use 'Server Name Indication' (SNI), configure one virtual server is your default server (often this is the first virtual serever). Ancient browsers, OSs or runtime environments without SNI support connect solely to this server
+* If you use 'Server Name Indication' (SNI) configure one virtual server as your default server (often this is the first virtual server). Ancient browsers, OSs or runtime environments without SNI support connect solely to this server
 * Use only the TLS/SSL extensions that you really need, e.g. deactivate heart beat (see <u>[http://heartbleed.com Heartbleed]</u>), do not activate insecure or untested drafts for extensions e.g. additional random, opaque PRF input (see. <u>[http://dualec.org/DualECTLS.pdf DualECTLS]</u>)
 * Set reasonable HTML headers, e.g. <u>[[HTTP Strict Transport Security|HTTP Strict Transport Security (HSTS)]]</u>