This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Web Application Security Testing Cheat Sheet"

Jump to: navigation, search
(Data Validation)
(Information Gathering)
Line 27: Line 27:
* [[Fingerprint_Web_Server_(OTG-INFO-002)|Perform Web Application Fingerprinting]]
* [[Fingerprint_Web_Server_(OTG-INFO-002)|Perform Web Application Fingerprinting]]
* Identify technologies used
* Identify technologies used
* Identify user roles
* [[Test_Role_Definitions_(OTG-IDENT-001)|Identify user roles]]
* [[Identify_application_entry_points_(OTG-INFO-006) | Identify application entry points]]
* [[Identify_application_entry_points_(OTG-INFO-006) | Identify application entry points]]
* Identify client-side code
* Identify client-side code

Revision as of 17:52, 3 September 2015



This cheat sheet provides a checklist of tasks to be performed when performing a blackbox security test of a web application.


This checklist is intended to be used as an aide memoire for experienced pentesters and should be used in conjunction with the OWASP Testing Guide. It will be updated as the Testing Guide v4 is progressed.

The intention is that this guide will be available as an XML document, with scripts that convert it into formats such as pdf, Media Wiki markup, HTML etc.

This will allow it to be consumed within security tools as well as being available in a format suitable for printing.

All feedback or offers of help will be appreciated - and if you have specific chances you think should be made, just get stuck in.

The Checklist

Information Gathering

Configuration Management

  • Check for commonly used application and administrative URLs
  • Check for old, backup and unreferenced files
  • Check HTTP methods supported and Cross Site Tracing (XST)
  • Test file extensions handling
  • Test RIA cross domain policy
  • Test for security HTTP headers (e.g. CSP, X-Frame-Options, HSTS)
  • Test for policies (e.g. Flash, Silverlight, robots)
  • Test for non-production data in live environment, and vice-versa
  • Check for sensitive data in client-side code (e.g. API keys, credentials)

Secure Transmission

  • Check SSL Version, Algorithms, Key length
  • Check for Digital Certificate Validity (Duration, Signature and CN)
  • Check credentials only delivered over HTTPS
  • Check that the login form is delivered over HTTPS
  • Check session tokens only delivered over HTTPS
  • Check if HTTP Strict Transport Security (HSTS) in use


Session Management


Data Validation

Denial of Service

Business Logic

  • Test for feature misuse
  • Test for lack of non-repudiation
  • Test for trust relationships
  • Test for integrity of data
  • Test segregation of duties
  • Test for Process Timing
  • Test Number of Times a Function Can be Used Limits
  • Test for the Circumvention of Work Flows
  • Test Defenses Against Application Mis-use
  • Test Upload of Unexpected File Types


Risky Functionality - File Uploads

Risky Functionality - Card Payment


Error Handling

Other Formats

  • DradisPro template format on github
  • Asana template on Templana (thanks to Bastien Siebman)

Authors and primary contributors

Simon Bennetts
Rory McCune
Colin Watson
Simone Onofri
Amro AlOlaqi

All the authors of the Testing Guide v3

Other Contributors

Ryan Dewhurst

Related articles

OWASP Testing Guide

Mozilla Web Security Verification

OWASP Cheat Sheets Project Homepage