Open Web Application Security Project

From The Secure Arc Wiki

Jump to: navigation, search

The following summary is taken from the OWASP website (reproduced in accordance with the Creative Commons 2.5 License):

OWASP (Open Web Application Security Project), is a worldwide free and open community focused on improving the security of application software. Their mission is to make application security "visible," so that people and organisations can make informed decisions about application security risks. Everyone is free to participate in OWASP and all of their materials are available under an open source license. The OWASP Foundation is a 501c3 not-for-profit charitable organization that ensures the ongoing availability and support for their work.

The following information gives a brief account of relevant OWASP testing guidelines. Each area of testing can be mapped back to the Security Principles that drive them.


Standards Outline

The structure of the testing guidelines includes the following;

  • Introduction and Objectives
  • Information Gathering
    • Testing Web Application Fingerprint
    • Application Discovery
    • Spidering and Googling
    • Analysis of Error Codes
    • Infrastructure Configuration Management Testing
      • SSL/TLS Testing
      • DB Listener Testing
    • Application Configuration Management Testing
    • Testing for File Extensions Handling
    • Old, backup and unreferenced files
  • Business Logic Testing
  • Authentication Testing
    • Testing for Guessable (Dictionary) User Account
    • Brute Force Testing
    • Testing for bypassing authentication schema
    • Testing for directory traversal/file include
    • Testing for vulnerable remember password and pwd reset
    • Testing for Logout and Browser Cache Management Testing
  • Session Management Testing
    • Testing for Session Management Schema
    • Testing for Cookie and Session Token Manipulation
    • Testing for Exposed Session Variables
    • Testing for CSRF
    • Testing for HTTP Exploit
  • Data Validation Testing
    • Testing for Cross Site Scripting
      • Testing for HTTP Methods and XST
    • Testing for SQL Injection
      • Oracle Testing
      • MySQL Testing
      • SQL Server Testing
    • Testing for LDAP Injection
    • Testing for ORM Injection
    • Testing for XML Injection
    • Testing for SSI Injection
    • Testing for XPath Injection
    • IMAP/SMTP Injection
    • Testing for Code Injection
    • Testing for Command Injection
    • Testing for Buffer overflow
      • Testing for Heap overflow
      • Testing for Stack overflow
      • Testing for Format string
    • Testing for incubated vulnerabilities
  • Testing for Denial of Service
    • Testing for DoS Locking Customer Accounts
    • Testing for DoS Buffer Overflows
    • Testing for DoS User Specified Object Allocation
    • Testing for User Input as a Loop Counter
    • Testing for Writing User Provided Data to Disk
    • Testing for DoS Failure to Release Resources
    • Testing for Storing too Much Data in Session
  • Web Services Testing
    • XML Structural Testing
    • XML Content-level Testing
    • HTTP GET parameters/REST Testing
    • Testing for Naughty SOAP attachments
    • WS Replay Testing
  • AJAX Testing
    • AJAX Vulnerabilities
    • How to test AJAX

Standard Practice

The OWASP guidelines suggest an approach to securing information assets and web applications throughout the SDLC. These practices will map directly into the Security Principles. There are many other projects developed by the OWASP community. A list can be found at the following [link].

Licensing and Documentation

OWASP content is available under the Creative Commons 2.5 License. Information and guides can be downloaded for personal or business use directly from the OWASP Testing website.


Personal tools