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

From OWASP
Jump to: navigation, search
m (→‎Reporting)
 
(18 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
{{Template:OWASP Testing Guide v2}}
+
{{Template:OWASP Testing Guide v4}}
  
−
Performing the technical side of the assessment is only half of the overall assessment process; the final product is the production of a well-written, and informative, report.  
+
Performing the technical side of the assessment is only half of the overall assessment process. The final product is the production of a well written and informative report. A report should be easy to understand and should highlight all the risks found during the assessment phase. The report should appeal to both executive management and technical staff.  
−
A report should be easy to understand and highlight all the risks found during the assessment phase and appeal to both management and technical staff.  
 
  
−
The report needs to have three major sections and be created in a manner that allows each section to be split off and printed and given to the appropriate teams, such as the developers or system managers.
+
The report needs to have three major sections. It should be created in a manner that allows each separate section to be printed and given to the appropriate teams, such as the developers or system managers. The recommended sections are outlined below.
  
−
The sections generally recommended are:
 
 
   
 
   
−
'''I. Executive Summary'''  
+
'''1. Executive Summary'''
  
−
The executive summary sums up the overall findings of the assessment and gives managers, or system owners, an idea of the overall risk faced. The language used should be more suited to people who are not technically aware and should include graphs or other charts which show the risk level. It is recommended that a summary be included, which details when the testing commenced and when it was completed.
+
The executive summary sums up the overall findings of the assessment and gives business managers and system owners a high level view of the vulnerabilities discovered. The language used should be more suited to people who are not technically aware and should include graphs or other charts which show the risk level. Keep in mind that executives will likely only have time to read this summary and will want two questions answered in plain language: 1) ''What's wrong?'' 2) ''How do I fix it?'' You have one page to answer these questions.
  
−
Another section, which is often overlooked, is a paragraph on implications and actions. This allows the system owners to understand what is required to be done in order to ensure the system remains secure.  
+
The executive summary should plainly state that the vulnerabilities and their severity is an '''input''' to their organizational risk management process, not an outcome or remediation. It is safest to explain that tester does not understand the threats faced by the organization or business consequences if the vulnerabilities are exploited. This is the job of the risk professional who calculates risk levels based on this and other information. Risk management will typically be part of the organization's IT Security Governance, Risk and Compliance (GRC) regime and this report will simply provide an input to that process.
  
−
'''II. Technical Management Overview'''  
+
'''2. Test Parameters'''
  
−
The technical management overview section often appeals to technical managers who require more technical detail than found in the executive summary. This section should include details about the scope of the assessment, the targets included and any caveats, such as system availability etc.  
+
The Introduction should outline the parameters of the security testing, the findings and remediation. Some suggested section headings include:
−
This section also needs to include an introduction on the risk rating used throughout the report and then finally a technical summary of the findings.
 
  
−
'''III Assessment Findings'''
+
2.1  Project Objective:
 +
This section outlines the project objectives and the expected outcome of the assessment.
  
−
The last section of the report is the section, which includes detailed technical detail about the vulnerabilities found, and the approaches needed to ensure they are resolved. This section is aimed at a technical level and should include all the necessary information for the technical teams to understand the issue and be able to solve it.  
+
2.2 Project Scope:
 +
This section outlines the agreed scope.
  
−
The findings section should include:
+
2.3 Project Schedule:
 +
This section outlines when the testing commenced and when it was completed.
 +
 
 +
2.4 Targets:  
 +
This section lists the number of applications or targeted systems.
  
−
* A reference number for easy reference with screenshots
+
2.5 Limitations:
−
* The affected item
+
This section outlines every limitation which was faced throughout the assessment. For example, limitations of project-focused tests, limitation in the security testing methods, performance or technical issues that the tester come across during the course of assessment, etc.
−
* A technical description of the issue
 
−
* A section on resolving the issue
 
−
* The risk rating and impact value
 
  
−
Each finding should be clear and concise and give the reader of the report a full understanding of the issue at hand.
+
2.6 Findings Summary:
 +
This section outlines the vulnerabilities that were discovered during testing.
  
−
Here is the report:
+
2.7 Remediation Summary:
 +
This section outlines the action plan for fixing the vulnerabilities that were discovered during testing.
  
−
<center>[[Image:tablefin.PNG]]</center>
+
'''3. Findings'''
−
<center>[[Image:tablefin2.PNG]]</center>
 
−
<center>[[Image:tablefin3.PNG]]</center>
 
−
<center>[[Image:tablefin4.PNG]]</center>
 
  
−
'''IV Toolbox''' 
+
The last section of the report includes detailed technical information about the vulnerabilities found and the actions needed to resolve them. This section is aimed at a technical level and should include all the necessary information for the technical teams to understand the issue and resolve it. Each finding should be clear and concise and give the reader of the report a full understanding of the issue at hand.
  
−
This section is often used to describe the commercial and open-source tools that were used in conducting the assessment. When custom scripts/code are utilized during the assessment, it should be disclosed in this section or noted as attachment.
 
−
It is often appreciated by the customer when the methodology used by the consultants is included. It gives them an idea of the thoroughness of the assessment and also an idea what area's where included.
 
  
−
'''Report'''
+
The findings section should include:
  
−
{| border=1
+
* Screenshots and command lines to indicate what tasks were undertaken during the execution of the test case
−
|| '''Category''' || '''Ref Number''' || '''Name ''' || '''Finding ''' ||'''Affected Item'''|| '''Comment/Solution ''' || '''Risk Value '''
+
* The affected item
 +
* A technical description of the issue and the affected function or object
 +
* A section on resolving the issue
 +
* The severity rating [1], with vector notation if using CVSS
 +
 
 +
The following is the list of controls that were tested during the assessment:
 +
 
 +
{| class="wikitable"
 +
| align="center" style="background:#f0f0f0;"|'''Test ID'''
 +
| align="center" style="background:#f0f0f0;"|'''Test Description'''
 +
| align="center" style="background:#f0f0f0;"|'''Findings'''
 +
| align="center" style="background:#f0f0f0;"|'''Severity'''
 +
| align="center" style="background:#f0f0f0;"|'''Recommendations'''
 +
|-
 +
| ||||
 +
|-
 +
| colspan="5" | '''Information Gathering'''
 +
|-
 +
| OTG-INFO-001||Conduct Search Engine Discovery and Reconnaissance for Information Leakage || || ||
 +
|-
 +
| OTG-INFO-002||Fingerprint Web Server || || ||
 +
|-
 +
| OTG-INFO-003||Review Webserver Metafiles for Information Leakage || || ||
 +
|-
 +
| OTG-INFO-004||Enumerate Applications on Webserver || || ||
 +
|-
 +
| OTG-INFO-005||Review Webpage Comments and Metadata for Information Leakage || || ||
 +
|-
 +
| OTG-INFO-006||Identify application entry points || || ||
 +
|-
 +
| OTG-INFO-007||Map execution paths through application || || ||
 +
|-
 +
| OTG-INFO-009||Fingerprint Web Application Framework || || ||
 +
|-
 +
| OTG-INFO-009||Fingerprint Web Application || || ||
 +
|-
 +
| OTG-INFO-010||Map Application Architecture || || ||
 +
|-
 +
| || || || || ||
 +
|-
 +
| colspan="5" | '''Configuration and Deploy Management Testing'''
 +
|-
 +
| OTG-CONFIG-001||Test Network/Infrastructure Configuration || || ||
 +
|-
 +
| OTG-CONFIG-002 ||Test Application Platform Configuration || || ||
 +
|-
 +
| OTG-CONFIG-003||Test File Extensions Handling for Sensitive Information || || ||
 +
|-
 +
| OTG-CONFIG-004|| Backup and Unreferenced Files for Sensitive Information || || ||
 +
|-
 +
| OTG-CONFIG-005||Enumerate Infrastructure and Application Admin Interfaces || || ||
 +
|-
 +
| OTG-CONFIG-006||Test HTTP Methods || || ||
 +
|-
 +
| OTG-CONFIG-007||Test HTTP Strict Transport Security || || ||
 +
|-
 +
| OTG-CONFIG-008||Test RIA cross domain policy || || ||
 +
|-
 +
| |||| || || ||
 +
|-
 +
| colspan="5" | '''Identity Management Testing'''
 +
|-
 +
| OTG-IDENT-001||Test Role Definitions || || ||
 +
|-
 +
| OTG-IDENT-002||Test User Registration Process || || ||
 +
|-
 +
| OTG-IDENT-003||Test Account Provisioning Process || || ||
 +
|-
 +
| OTG-IDENT-004||Testing for Account Enumeration and Guessable User Account || || ||
 +
|-
 +
| OTG-IDENT-005||Testing for Weak or unenforced username policy || || ||
 +
|-
 +
| OTG-IDENT-006||Test Permissions of Guest/Training Accounts || || ||
 +
|-
 +
| OTG-IDENT-007||Test Account Suspension/Resumption Process || || ||
 +
|-
 +
| |||| || || ||
 +
|-
 +
| colspan="5" | '''Authentication Testing'''
 +
|-
 +
| OTG-AUTHN-001||Testing for Credentials Transported over an Encrypted Channel || || ||
 +
|-
 +
| OTG-AUTHN-002||Testing for default credentials || || ||
 +
|-
 +
| OTG-AUTHN-003||Testing for Weak lock out mechanism || || ||
 +
|-
 +
| OTG-AUTHN-004||Testing for bypassing authentication schema || || ||
 +
|-
 +
| OTG-AUTHN-005||Test remember password functionality || || ||
 +
|-
 +
| OTG-AUTHN-006||Testing for Browser cache weakness || || ||
 +
|-
 +
| OTG-AUTHN-007||Testing for Weak password policy || || ||
 +
|-
 +
| OTG-AUTHN-008||Testing for Weak security question/answer || || ||
 +
|-
 +
| OTG-AUTHN-009||Testing for weak password change or reset functionalities || || ||
 +
|-
 +
| OTG-AUTHN-010||Testing for Weaker authentication in alternative channel || || ||
 +
|-
 +
| |||| || || ||
 +
|-
 +
| colspan="5" | '''Authorization Testing'''
 +
|-
 +
| OTG-AUTHZ-001||Testing Directory traversal/file include || || ||
 +
|-
 +
| OTG-AUTHZ-002||Testing for bypassing authorization schema || || ||
 +
|-
 +
| OTG-AUTHZ-003||Testing for Privilege Escalation || || ||
 +
|-
 +
| OTG-AUTHZ-004||Testing for Insecure Direct Object References || || ||
 +
|-
 +
| |||| || || ||
 +
|-
 +
| colspan="5" | '''Session Management Testing'''
 +
|-
 +
| OTG-SESS-001 ||Testing for Bypassing Session Management Schema || || ||
 +
|-
 +
| OTG-SESS-002 ||Testing for Cookies attributes || || ||
 +
|-
 +
| OTG-SESS-003 ||Testing for Session Fixation || || ||
 +
|-
 +
| OTG-SESS-004 ||Testing for Exposed Session Variables || || ||
 +
|-
 +
| OTG-SESS-005 ||Testing for Cross Site Request Forgery || || ||
 +
|-
 +
| OTG-SESS-006 ||Testing for logout functionality || || ||
 +
|-
 +
| OTG-SESS-007 ||Test Session Timeout || || ||
 +
|-
 +
| OTG-SESS-008 ||Testing for Session puzzling || || ||
 +
|-
 +
| || || || || ||
 +
|-
 +
| colspan="5" | '''Input Validation Testing'''
 +
|-
 +
| OTG-INPVAL-001||Testing for Reflected Cross Site Scripting || || ||
 +
|-
 +
| OTG-INPVAL-002||Testing for Stored Cross Site Scripting || || ||
 +
|-
 +
| OTG-INPVAL-003 ||Testing for HTTP Verb Tampering || || ||
 +
|-
 +
| OTG-INPVAL-004||Testing for HTTP Parameter pollution || || ||
 +
|-
 +
| OTG-INPVAL-006||Testing for SQL Injection || || ||
 +
|-
 +
| ||Oracle Testing || || ||
 +
|-
 +
| ||MySQL Testing || || ||
 +
|-
 +
| ||SQL Server Testing || || ||
 +
|-
 +
| ||Testing PostgreSQL || || ||
 +
|-
 +
| ||MS Access Testing || || ||
 +
|-
 +
| ||Testing for NoSQL injection || || ||
 
|-
 
|-
−
|| Information Gathering || || Application Discovery ||  ||  ||  ||
+
| OTG-INPVAL-007||Testing for LDAP Injection || || ||
 
|-
 
|-
−
|| || || Spidering and googling ||  ||  ||  ||
+
| OTG-INPVAL-008||Testing for ORM Injection || || ||
 
|-
 
|-
−
|| || || Analisys of error code ||  ||  ||  ||
+
| OTG-INPVAL-009||Testing for XML Injection || || ||
 
|-
 
|-
−
|| ||  || SSL/TLS Testing || ||  || ||
+
| OTG-INPVAL-010||Testing for SSI Injection || || ||
 
|-
 
|-
−
|| ||  || DB Listener Testing || ||  || ||
+
| OTG-INPVAL-011||Testing for XPath Injection || || ||
 
|-
 
|-
−
|| || || File extensions handling ||  ||  ||  ||
+
| OTG-INPVAL-012||IMAP/SMTP Injection || || ||
 
|-
 
|-
−
|| ||   || Old, backup and unreferenced files ||  ||  ||  ||
+
| OTG-INPVAL-013||Testing for Code Injection || || ||
 
|-
 
|-
−
||Business logic testing  || || ||  ||  ||  ||
+
| ||Testing for Local File Inclusion || || ||
 
|-
 
|-
−
|| Authentication Testing || || Default or guessable account ||  ||  || ||
+
| ||Testing for Remote File Inclusion || || ||
 
|-
 
|-
−
|| || || Brute Force ||  ||  ||  ||
+
| OTG-INPVAL-014||Testing for Command Injection || || ||
 
|-
 
|-
−
|| || || Bypassing authentication schema ||  ||  ||  ||
+
| OTG-INPVAL-015||Testing for Buffer overflow || || ||
 
|-
 
|-
−
|| || || Directory traversal/file include ||  ||  ||  ||
+
| ||Testing for Heap overflow || || ||
 
|-
 
|-
−
|| || || Vulnerable remember password and pwd reset ||  ||  ||  ||
+
| ||Testing for Stack overflow || || ||
 
|-
 
|-
−
|| ||  || Logout and Browser Cache Management Testing || ||  || ||
+
| ||Testing for Format string || || ||
 
|-
 
|-
−
|| Session Management Testing || || Session Management Schema  ||  ||  || ||
+
| OTG-INPVAL-016||Testing for incubated vulnerabilities || || ||
 
|-
 
|-
−
|| || || Session Token Manipulation ||  ||  ||  ||
+
| OTG-INPVAL-017||Testing for HTTP Splitting/Smuggling || || ||
 
|-
 
|-
−
|| || || Exposed Session Variables || ||  ||  ||
+
| |||| || || ||
 
|-
 
|-
−
||  ||  || Session Riding ||  ||  ||  ||
+
| colspan="5" | '''Error Handling'''
 
|-
 
|-
−
|| || || HTTP Exploit ||  ||  ||  ||
+
| OTG-ERR-001||Analysis of Error Codes || || ||
 
|-
 
|-
−
|| Data Validation Testing || || Cross site scripting ||  ||  ||  ||
+
| OTG-ERR-002||Analysis of Stack Traces || || ||
 
|-
 
|-
−
|| || || HTTP Methods and XST || ||  ||  ||
+
| || || || || ||
 
|-
 
|-
−
||  ||  || SQL Injection ||  ||  ||  ||
+
| colspan="5" | '''Cryptography'''
 
|-
 
|-
−
||  ||  || Stored procedure injection ||  || || ||
+
| OTG-CRYPST-001||Testing for Weak SSL/TSL Ciphers, Insufficient Transport Layer Protection || || ||
 
|-
 
|-
−
|| || || ORM Injection ||  ||  ||  ||
+
| OTG-CRYPST-002||Testing for Padding Oracle || || ||
 
|-
 
|-
−
|| || || LDAP Injection ||  ||  ||  ||
+
| OTG-CRYPST-003||Testing for Sensitive information sent via unencrypted channels || || ||
 
|-
 
|-
−
|| || || XML Injection || ||  ||  ||
+
| |||| || || ||
 
|-
 
|-
−
||  ||  || SSI Injection ||  ||  ||  ||
+
| colspan="5" | '''Business Logic Testing'''
 
|-
 
|-
−
|| || || XPath Injection ||  ||  ||  ||
+
| OTG-BUSLOGIC-001||Test Business Logic Data Validation || || ||
 
|-
 
|-
−
|| || || IMAP/SMTP Injection ||  ||  ||  ||
+
| OTG-BUSLOGIC-002||Test Ability to Forge Requests || || ||
 
|-
 
|-
−
|| || || Code Injection ||  ||  ||  ||
+
| OTG-BUSLOGIC-003||Test Integrity Checks || || ||
 
|-
 
|-
−
|| || || OS Commanding ||  ||  ||  ||
+
| OTG-BUSLOGIC-004||Test for Process Timing || || ||
 
|-
 
|-
−
|| || || Buffer overflow ||  ||  ||  ||
+
| OTG-BUSLOGIC-005||Test Number of Times a Function Can be Used Limits || || ||
 
|-
 
|-
−
|| || || Incubated vulnerability ||  ||  ||  ||
+
| OTG-BUSLOGIC-006||Testing for the Circumvention of Work Flows || || ||
 
|-
 
|-
−
|| Denial of Service Testing || || Locking Customer Accounts ||  ||  ||  ||
+
| OTG-BUSLOGIC-007||Test Defenses Against Application Mis-use || || ||
 
|-
 
|-
−
|| || || User Specified Object Allocation ||  ||  ||  ||
+
| OTG-BUSLOGIC-008||Test Upload of Unexpected File Types || || ||
 
|-
 
|-
−
|| || || User Input as a Loop Counter ||  ||  ||  ||
+
| OTG-BUSLOGIC-009||Test Upload of Malicious Files || || ||
 
|-
 
|-
−
|| || || Writing User Provided Data to Disk || ||  ||  ||
+
| |||| || || ||
 
|-
 
|-
−
||  ||  || Failure to Release Resources ||  ||  ||  ||
+
| colspan="5" | '''Client Side Testing'''
 
|-
 
|-
−
|| || || Storing too Much Data in Session ||  ||  ||  ||
+
| OTG-CLIENT-001||Testing for DOM based Cross Site Scripting || || ||
 
|-
 
|-
−
|| Web Services Testing  ||  || XML Structural Testing || ||  || ||
+
| OTG-CLIENT-002||Testing for JavaScript Execution || || ||
 
|-
 
|-
−
||  ||  || XML content-level Testing || ||  || ||
+
| OTG-CLIENT-003||Testing for HTML Injection || || ||
 
|-
 
|-
−
|| ||  || HTTP GET parameters/REST Testing || ||  || ||
+
| OTG-CLIENT-004 ||Testing for Client Side URL Redirect || || ||
 
|-
 
|-
−
|| || || Naughty SOAP attachments ||  ||  ||  ||
+
| OTG-CLIENT-005||Testing for CSS Injection || || ||
 
|-
 
|-
−
|| ||  || Replay Testing ||  || || ||
+
| OTG-CLIENT-006||Testing for Client Side Resource Manipulation || || ||
 
|-
 
|-
−
|| AJAX Testing || || AJAX Vulnerabilities  ||  ||  ||  ||
+
| OTG-CLIENT-007||Test Cross Origin Resource Sharing || || ||
 
|-
 
|-
 +
| OTG-CLIENT-008||Testing for Cross Site Flashing || || ||
 +
|-
 +
| OTG-CLIENT-009||Testing for Clickjacking || || ||
 +
|-
 +
| OTG-CLIENT-010||Testing WebSockets || || ||
 +
|-
 +
| OTG-CLIENT-011||Test Web Messaging || || ||
 +
|-
 +
| OTG-CLIENT-012||Test Local Storage || || ||
 +
|-
 +
|
 
|}
 
|}
  
 +
'''Appendix''' 
  
 +
This section is often used to describe the commercial and open-source tools that were used in conducting the assessment. When custom scripts or code are utilized during the assessment, it should be disclosed in this section or noted as attachment. Customers appreciate when the methodology used by the consultants is included. It gives them an idea of the thoroughness of the assessment and what areas were included.
  
−
 
+
'''References'''
−
 
+
Industry standard vulnerability severity and risk rankings (CVSS) [1] – http://www.first.org/cvss
−
{{Category:OWASP Testing Project AoC}}
 

Latest revision as of 19:04, 1 December 2014

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


Performing the technical side of the assessment is only half of the overall assessment process. The final product is the production of a well written and informative report. A report should be easy to understand and should highlight all the risks found during the assessment phase. The report should appeal to both executive management and technical staff.

The report needs to have three major sections. It should be created in a manner that allows each separate section to be printed and given to the appropriate teams, such as the developers or system managers. The recommended sections are outlined below.


1. Executive Summary

The executive summary sums up the overall findings of the assessment and gives business managers and system owners a high level view of the vulnerabilities discovered. The language used should be more suited to people who are not technically aware and should include graphs or other charts which show the risk level. Keep in mind that executives will likely only have time to read this summary and will want two questions answered in plain language: 1) What's wrong? 2) How do I fix it? You have one page to answer these questions.

The executive summary should plainly state that the vulnerabilities and their severity is an input to their organizational risk management process, not an outcome or remediation. It is safest to explain that tester does not understand the threats faced by the organization or business consequences if the vulnerabilities are exploited. This is the job of the risk professional who calculates risk levels based on this and other information. Risk management will typically be part of the organization's IT Security Governance, Risk and Compliance (GRC) regime and this report will simply provide an input to that process.

2. Test Parameters

The Introduction should outline the parameters of the security testing, the findings and remediation. Some suggested section headings include:

2.1 Project Objective: This section outlines the project objectives and the expected outcome of the assessment.

2.2 Project Scope: This section outlines the agreed scope.

2.3 Project Schedule: This section outlines when the testing commenced and when it was completed.

2.4 Targets: This section lists the number of applications or targeted systems.

2.5 Limitations: This section outlines every limitation which was faced throughout the assessment. For example, limitations of project-focused tests, limitation in the security testing methods, performance or technical issues that the tester come across during the course of assessment, etc.

2.6 Findings Summary: This section outlines the vulnerabilities that were discovered during testing.

2.7 Remediation Summary: This section outlines the action plan for fixing the vulnerabilities that were discovered during testing.

3. Findings

The last section of the report includes detailed technical information about the vulnerabilities found and the actions needed to resolve them. This section is aimed at a technical level and should include all the necessary information for the technical teams to understand the issue and resolve it. Each finding should be clear and concise and give the reader of the report a full understanding of the issue at hand.


The findings section should include:

  • Screenshots and command lines to indicate what tasks were undertaken during the execution of the test case
  • The affected item
  • A technical description of the issue and the affected function or object
  • A section on resolving the issue
  • The severity rating [1], with vector notation if using CVSS

The following is the list of controls that were tested during the assessment:

Test ID Test Description Findings Severity Recommendations
Information Gathering
OTG-INFO-001 Conduct Search Engine Discovery and Reconnaissance for Information Leakage
OTG-INFO-002 Fingerprint Web Server
OTG-INFO-003 Review Webserver Metafiles for Information Leakage
OTG-INFO-004 Enumerate Applications on Webserver
OTG-INFO-005 Review Webpage Comments and Metadata for Information Leakage
OTG-INFO-006 Identify application entry points
OTG-INFO-007 Map execution paths through application
OTG-INFO-009 Fingerprint Web Application Framework
OTG-INFO-009 Fingerprint Web Application
OTG-INFO-010 Map Application Architecture
Configuration and Deploy Management Testing
OTG-CONFIG-001 Test Network/Infrastructure Configuration
OTG-CONFIG-002 Test Application Platform Configuration
OTG-CONFIG-003 Test File Extensions Handling for Sensitive Information
OTG-CONFIG-004 Backup and Unreferenced Files for Sensitive Information
OTG-CONFIG-005 Enumerate Infrastructure and Application Admin Interfaces
OTG-CONFIG-006 Test HTTP Methods
OTG-CONFIG-007 Test HTTP Strict Transport Security
OTG-CONFIG-008 Test RIA cross domain policy
Identity Management Testing
OTG-IDENT-001 Test Role Definitions
OTG-IDENT-002 Test User Registration Process
OTG-IDENT-003 Test Account Provisioning Process
OTG-IDENT-004 Testing for Account Enumeration and Guessable User Account
OTG-IDENT-005 Testing for Weak or unenforced username policy
OTG-IDENT-006 Test Permissions of Guest/Training Accounts
OTG-IDENT-007 Test Account Suspension/Resumption Process
Authentication Testing
OTG-AUTHN-001 Testing for Credentials Transported over an Encrypted Channel
OTG-AUTHN-002 Testing for default credentials
OTG-AUTHN-003 Testing for Weak lock out mechanism
OTG-AUTHN-004 Testing for bypassing authentication schema
OTG-AUTHN-005 Test remember password functionality
OTG-AUTHN-006 Testing for Browser cache weakness
OTG-AUTHN-007 Testing for Weak password policy
OTG-AUTHN-008 Testing for Weak security question/answer
OTG-AUTHN-009 Testing for weak password change or reset functionalities
OTG-AUTHN-010 Testing for Weaker authentication in alternative channel
Authorization Testing
OTG-AUTHZ-001 Testing Directory traversal/file include
OTG-AUTHZ-002 Testing for bypassing authorization schema
OTG-AUTHZ-003 Testing for Privilege Escalation
OTG-AUTHZ-004 Testing for Insecure Direct Object References
Session Management Testing
OTG-SESS-001 Testing for Bypassing Session Management Schema
OTG-SESS-002 Testing for Cookies attributes
OTG-SESS-003 Testing for Session Fixation
OTG-SESS-004 Testing for Exposed Session Variables
OTG-SESS-005 Testing for Cross Site Request Forgery
OTG-SESS-006 Testing for logout functionality
OTG-SESS-007 Test Session Timeout
OTG-SESS-008 Testing for Session puzzling
Input Validation Testing
OTG-INPVAL-001 Testing for Reflected Cross Site Scripting
OTG-INPVAL-002 Testing for Stored Cross Site Scripting
OTG-INPVAL-003 Testing for HTTP Verb Tampering
OTG-INPVAL-004 Testing for HTTP Parameter pollution
OTG-INPVAL-006 Testing for SQL Injection
Oracle Testing
MySQL Testing
SQL Server Testing
Testing PostgreSQL
MS Access Testing
Testing for NoSQL injection
OTG-INPVAL-007 Testing for LDAP Injection
OTG-INPVAL-008 Testing for ORM Injection
OTG-INPVAL-009 Testing for XML Injection
OTG-INPVAL-010 Testing for SSI Injection
OTG-INPVAL-011 Testing for XPath Injection
OTG-INPVAL-012 IMAP/SMTP Injection
OTG-INPVAL-013 Testing for Code Injection
Testing for Local File Inclusion
Testing for Remote File Inclusion
OTG-INPVAL-014 Testing for Command Injection
OTG-INPVAL-015 Testing for Buffer overflow
Testing for Heap overflow
Testing for Stack overflow
Testing for Format string
OTG-INPVAL-016 Testing for incubated vulnerabilities
OTG-INPVAL-017 Testing for HTTP Splitting/Smuggling
Error Handling
OTG-ERR-001 Analysis of Error Codes
OTG-ERR-002 Analysis of Stack Traces
Cryptography
OTG-CRYPST-001 Testing for Weak SSL/TSL Ciphers, Insufficient Transport Layer Protection
OTG-CRYPST-002 Testing for Padding Oracle
OTG-CRYPST-003 Testing for Sensitive information sent via unencrypted channels
Business Logic Testing
OTG-BUSLOGIC-001 Test Business Logic Data Validation
OTG-BUSLOGIC-002 Test Ability to Forge Requests
OTG-BUSLOGIC-003 Test Integrity Checks
OTG-BUSLOGIC-004 Test for Process Timing
OTG-BUSLOGIC-005 Test Number of Times a Function Can be Used Limits
OTG-BUSLOGIC-006 Testing for the Circumvention of Work Flows
OTG-BUSLOGIC-007 Test Defenses Against Application Mis-use
OTG-BUSLOGIC-008 Test Upload of Unexpected File Types
OTG-BUSLOGIC-009 Test Upload of Malicious Files
Client Side Testing
OTG-CLIENT-001 Testing for DOM based Cross Site Scripting
OTG-CLIENT-002 Testing for JavaScript Execution
OTG-CLIENT-003 Testing for HTML Injection
OTG-CLIENT-004 Testing for Client Side URL Redirect
OTG-CLIENT-005 Testing for CSS Injection
OTG-CLIENT-006 Testing for Client Side Resource Manipulation
OTG-CLIENT-007 Test Cross Origin Resource Sharing
OTG-CLIENT-008 Testing for Cross Site Flashing
OTG-CLIENT-009 Testing for Clickjacking
OTG-CLIENT-010 Testing WebSockets
OTG-CLIENT-011 Test Web Messaging
OTG-CLIENT-012 Test Local Storage

Appendix

This section is often used to describe the commercial and open-source tools that were used in conducting the assessment. When custom scripts or code are utilized during the assessment, it should be disclosed in this section or noted as attachment. Customers appreciate when the methodology used by the consultants is included. It gives them an idea of the thoroughness of the assessment and what areas were included.

References Industry standard vulnerability severity and risk rankings (CVSS) [1] – http://www.first.org/cvss

Retrieved from "https://wiki.owasp.org/index.php?title=Reporting&oldid=186313"