Test HTTP Strict Transport Security (OTG-CONFIG-007)

Revision as of 08:24, 28 July 2013 by Andrew Muller (talk | contribs) (Andrew Muller moved page Testing for Missing HSTS header to Test HTTP Strict Transport Security (OTG-CONFIG-009): Align with common number and cross-product correlation initiative)

Jump to: navigation, search
This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents Back to the OWASP Testing Guide Project: https://www.owasp.org/index.php/OWASP_Testing_Project

Brief Summary

HSTS header is a mechanism that web sites have to communicate to the web browsers that all traffic exchanged with a given domain must always be sent over https, this will help protect the information from being passed over unencrypted requests.
Considering the importance of this security measure is important to verify that the web site using this HTTP header, in order to ensure that all the data travels encrypted from the web browser to the server.

Description of the Issue

...here: Short Description of the Issue: Topic and Explanation

Black Box testing and example

Testing for the presence of HSTS header:

   $ curl -s -D- https://paypal.com/ | grep Strict

Result Expected:

   Strict-Transport-Security: max-age=14400


OWASP Appsec Tutorial Series - Episode 4: Strict Transport Security