This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "HTTP Strict Transport Security Cheat Sheet"
(Created page with "<br> == Description == HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response he...") |
|||
Line 1: | Line 1: | ||
− | < | + | __NOTOC__ |
+ | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div> | ||
+ | |||
+ | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
+ | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
+ | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
+ | = Introduction = | ||
+ | __TOC__{{TOC hidden}} | ||
+ | |||
== Description == | == Description == | ||
Line 75: | Line 83: | ||
* [http://www.thoughtcrime.org/software/sslstrip/ Moxie Marlinspike's Black Hat 2009 talk on sslstrip, that demonstrates why you need HSTS] | * [http://www.thoughtcrime.org/software/sslstrip/ Moxie Marlinspike's Black Hat 2009 talk on sslstrip, that demonstrates why you need HSTS] | ||
+ | = Authors and Primary Editors = | ||
+ | |||
+ | Til Maas<br/> | ||
+ | Jim Manico<br/> | ||
+ | Pawel Krawczyk<br/> | ||
+ | Daniel Black</br> | ||
+ | Michael Coates | ||
+ | |||
+ | == Other Cheatsheets == | ||
+ | |||
+ | {{Cheatsheet_Navigation_Body}} | ||
+ | |||
+ | |} | ||
+ | |||
+ | [[Category:Cheatsheets]] | ||
+ | [[Category:OWASP Best Practices]] | ||
[[Category:Control|Control]] | [[Category:Control|Control]] |
Revision as of 07:03, 8 July 2016
Last revision (mm/dd/yy): 07/8/2016 IntroductionDescriptionHTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. Once a supported browser receives this header that browser will prevent any communications from being sent over HTTP to the specified domain and will instead send all communications over HTTPS. It also prevents HTTPS click through prompts on browsers. The specification has been released and published end of 2012 as RFC 6797 (HTTP Strict Transport Security (HSTS)) by the IETF. (Reference see in the links at the bottom.) ThreatsHSTS addresses the following threats:
ExamplesSimple example, using a long (1 year) max-age: Strict-Transport-Security: max-age=31536000 If all present and future subdomains will be HTTPS: Strict-Transport-Security: max-age=31536000; includeSubDomains Recommended: If the site owner would like their domain to be included in the HSTS preload list maintained by Chrome (and used by Firefox and Safari), then use: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload The `preload` flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list. ProblemsSite owners can use HSTS to identify users without cookies. This can lead to a significant privacy leak[1]. Cookies can be manipulated from sub-domains, so omitting the include "includeSubDomains" option permits a broad range of cookie-related attacks that HSTS would otherwise prevent by requiring a valid certificate for a subdomain. Ensuring the "Secure Flag" is set on all cookies will also prevent, some, but not all, of the same attacks. Browser Support
Links
Authors and Primary EditorsTil Maas Other Cheatsheets |