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

Jump to: navigation, search
(Other Contributors: Add to contributors)
Line 101: Line 101:
* Test for auto-binding
* Test for auto-binding
== Denial of Service ==
== Denial of Service ==
* Test for anti-automation
* Test for anti-automation
* Test for account lockout
* Test for account lockout
Line 123: Line 122:
* Test whether card number are stored
* Test whether card number are stored
== HTML 5==
* Test Web Messaging
* Test for Web Storage SQL injection
= Authors and primary contributors =
= Authors and primary contributors =
[[User:Simon Bennetts|Simon Bennetts]]
[[User:Simon Bennetts|Simon Bennetts]]<br/>
[[User:Raesene|Rory McCune]] <br/>
Colin Watson<br/>
All the authors of theTesting Guide v3
= Other Contributors =
= Other Contributors =
[[User:Raesene|Rory McCune]] <br/>
Colin Watson<br/>
= Related articles =
= Related articles =

Revision as of 03:17, 31 July 2012



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.

It is currently at a very early stage, but any feedback or offers of help will be appreciated.

The Checklist

Information Gathering

  • Manually explore the site
  • Spider/crawl for missed or hidden content
  • Check for files that expose content, such as robots.txt, sitemap.xml, .DS_Store
  • Check the caches of major search engines for publicly accessible sites
  • Perform Web Application Fingerprinting
  • Identify technologies used
  • Identify user roles
  • Identify application entry points
  • Identify client-side code
  • Identify multiple versions/channels (e.g. web, mobile web, mobile app, web services)
  • Identify co-hosted and related applications
  • Identify all hostnames and ports
  • Identify third-party hosted content

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 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

Secure Transmission

  • Check SSL Version, Algorithms, Key length, Digital Cert. Validity
  • Check credentials only delivered over HTTPS
  • Check session tokens only delivered over HTTPS
  • Check if HTTP Strict Transport Security (HSTS) in use


  • Test for user enumeration
  • Test for authentication bypass
  • Test for bruteforce protection
  • Test password quality rules
  • Test remember me functionality
  • Test password reset
  • Test CAPTCHA
  • Test multi factor authentication
  • Test logout and cache management
  • Test for default logins
  • Test for user-accessible authentication history
  • Test for out-of channel notification of account lockouts and successful password changes
  • Test for consistent authentication across applications with shared authentication schema / SSO

Session Management

  • Establish how session management is handled in the application (eg, tokens in cookies, token in URL)
  • Check session tokens for cookie flags (httpOnly and secure)
  • Check session cookie scope
  • Check session timeout duration
  • Test to see if users can have multiple simultaneous sessions
  • Test session cookies for randomness
  • Confirm that new session tokens are issued on login, role change and logout
  • Test for consistent session management across applications with shared session management
  • Test for session puzzling
  • Test for CSRF and clickjacking


  • Test for path traversal
  • Test for bypassing authorization schema
  • Test for Privilege Escalation
  • Test for horizontal Access control problems (between two users at the same privilege level)
  • Test for missing authorization

Data Validation

  • Test for Reflected Cross Site Scripting
  • Test for Stored Cross Site Scripting
  • Test for DOM based Cross Site Scripting
  • Test for Cross Site Flashing
  • Test for SQL Injection
  • Test for LDAP Injection
  • Test for ORM Injection
  • Test for XML Injection
  • Test for XXE Injection
  • Test for SSI Injection
  • Test for XPath Injection
  • Test for IMAP/SMTP Injection
  • Test for Code Injection
  • Test for Command Injection
  • Test for Buffer overflow
  • Test for incubated vulnerabilities
  • Test for HTTP Splitting/Smuggling
  • Test for Open Redirection
  • Test for Local File Inclusion
  • Test for Remote File Inclusion
  • Compare client-side and server-side validation rules
  • Test for NoSQL injection
  • Test for HTTP parameter pollution
  • Test for auto-binding

Denial of Service

  • Test for anti-automation
  • Test for account lockout
  • Test for HTTP protocol DoS

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

Risky Functionality - File Uploads

  • Test that acceptable file types are whitelisted
  • Test that file size limits, upload frequency and total file counts are defined and are enforced
  • Test that file contents match the defined file type
  • Test that all file uploads have Anti-Virus scanning in-place.
  • Test that unsafe filenames are sanitised
  • Test that uploaded files are not directly accessible within the web root
  • Test that uploaded files are not served on the same hostname/port
  • Test that files and other media are integrated with the authentication and authorisation schemas

Risky Functionality - Card Payment

  • Test whether card number are stored
  • TBC


  • Test Web Messaging
  • Test for Web Storage SQL injection

Authors and primary contributors

Simon Bennetts
Rory McCune
Colin Watson
All the authors of theTesting Guide v3

Other Contributors

Related articles

OWASP Testing Guide

Mozilla Web Security Verification

OWASP Cheat Sheets Project Homepage