4.0

More documents

Recommendations

Info

210 5 Reporting 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. 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. 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: 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
211 Reporting Test ID Lowest version 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-008 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
Page 1 and 2:
1 Testing Guide 4.0 Project Leaders
Page 3 and 4:
Testing Guide Foreword - Table of c
Page 5 and 6:
3 Testing Guide Foreword - Table of
Page 7 and 8:
5 Testing Guide Foreword - By Eoin
Page 9 and 10:
7 Testing Guide Frontispiece 1 Test
Page 11 and 12:
9 Testing Guide Introduction 2 The
Page 13 and 14:
11 Testing Guide Introduction vide
Page 15 and 16:
13 Testing Guide Introduction Testi
Page 17 and 18:
15 Testing Guide Introduction laid
Page 19 and 20:
17 Testing Guide Introduction valid
Page 21 and 22:
19 Testing Guide Introduction USER
Page 23 and 24:
21 Testing Guide Introduction ment
Page 25 and 26:
23 Testing Guide Introduction offen
Page 27 and 28:
25 The OWASP Testing Framework sect
Page 29 and 30:
27 Web Application Penetration Test
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
101 Web Application Penetration Tes
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162: 159 Web Application Penetration Tes
Page 211: 209 same code can be applied to ses
Page 215 and 216: 213 Reporting Test ID Business Logi
Page 217 and 218: 215 Appendix kajfghlhfkcocafkcjlajl
Page 219 and 220: 217 Appendix Testing - http:/www.ni
Page 221 and 222: 219 Cross Site Scripting (XSS) For
Page 223 and 224: 221 LDAP Injection For details on L
show all

4.0

Create successful ePaper yourself

Delete template?

Save as template?