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 "Testing: Information Gathering"
m |
|||
| (32 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Template:OWASP Testing Guide v4}} | |
| − | {{Template:OWASP Testing Guide | ||
| − | + | ''' 4.2 Information Gathering ''' | |
---- | ---- | ||
| + | |||
The first phase in security assessment is focused on collecting as much information as possible about a target application. | The first phase in security assessment is focused on collecting as much information as possible about a target application. | ||
| − | Information Gathering is | + | Information Gathering is the most critical step of an application security test. The security test should endeavour to test as much of the code base as possible. Thus mapping all possible paths through the code to facilitate thorough testing is paramount. |
This task can be carried out in many different ways. | This task can be carried out in many different ways. | ||
| − | + | By using public tools (search engines), scanners, sending simple HTTP requests, or specially crafted requests, it is possible to force the application to leak information, e.g., disclosing error messages or revealing the versions and technologies used.<br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | [[Testing for Application Discovery (OWASP-IG-005)|4.2.5 Application Discovery (OWASP-IG-005)]] [rename to "Enumerate applications on webserver"]<br> | ||
Application discovery is an activity oriented to the identification of the web applications hosted on a web server/application server.<br> | Application discovery is an activity oriented to the identification of the web applications hosted on a web server/application server.<br> | ||
| − | This analysis is important because | + | This analysis is important because often there is not a direct link connecting the main application backend. Discovery analysis can be useful to reveal details such as web applications used for administrative purposes. In addition, it can reveal old versions of files or artifacts such as undeleted, obsolete scripts, crafted during the test/development phase or as the result of maintenance. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | [[Testing: Spiders, Robots, and Crawlers (OWASP-IG-001)|4.2.1 Spiders, Robots and Crawlers (OWASP-IG-001)]] [rename to "Review webserver metafiles" ] | |
| − | This | + | This phase of the Information Gathering process consists of browsing and capturing resources related to the application being tested. |
| − | [[ | + | [[Testing: Review webpage comments and metadata (OWASP-IG-00x)|4.2.x Review webpage comments and metadata(OWASP-IG-00x)]] |
| + | Review the webpage metadata, HTML, JavaScript comments for sensitive information and disabled links/scripts. | ||
| − | + | [[Testing: Identify application entry points (OWASP-IG-003)|4.2.3 Identify application entry points (OWASP-IG-003)]]<br> | |
| − | + | Enumerating the application and its attack surface is a key precursor before any attack should commence. This section will help you identify and map out every area within the application that should be investigated once your enumeration and mapping phase has been completed. | |
| − | [[ | + | [[Testing: Identify application exit/handover points (OWASP-IG-00x)|4.2.x Identify application exit/handover points (OWASP-IG-00x)]]<br> |
| + | Identify the functional exit points of the application and points where the application hands over to another application that may, or may not, be within scope of testing (e.g. handover to a payment gateway). | ||
| − | + | [[Testing: Map paths through the application (OWASP-IG-00x)|4.2.x Map paths through the application (OWASP-IG-00x)]]<br> | |
| + | Enumerating the application and its attack surface is a key precursor before any attack should commence. This section will help you identify and map out every area within the application that should be investigated once your enumeration and mapping phase has been completed. | ||
| − | [[ | + | [[Testing for Web Server Fingerprint (OWASP-IG-00x)|4.2.x Testing Web Server Fingerprint (OWASP-IG-00x)]]<br> |
| + | Application fingerprint is the first step of the Information Gathering process; knowing the version and type of a running web server allows testers to determine known vulnerabilities and the appropriate exploits to use during testing. | ||
| − | + | [[Testing for Web Application Fingerprint (OWASP-IG-004)|4.2.4 Testing Web Application Fingerprint (OWASP-IG-004)]]<br> | |
| + | Application fingerprint is the first step of the Information Gathering process; knowing the version and type of a running web server allows testers to determine known vulnerabilities and the appropriate exploits to use during testing. | ||
| + | [[Testing for Error Codes (OWASP-IG-006)|4.2.6 Analysis of Error Codes (OWASP-IG-006)]]<br> | ||
| + | During a penetration test, web applications may divulge information that is not intended to be seen by an end user. Information such as error codes can inform the tester about technologies and products being used by the application.<br> | ||
| + | In many cases, error codes can be easily invoked without the need for specialist skills or tools, due to bad exception handling design and coding. | ||
| + | [[Testing: Search engine discovery/reconnaissance (OWASP-IG-002)|4.2.2 Search Engine Discovery/Reconnaissance (OWASP-IG-002)]]<br> | ||
| + | Search engines, such as Google, can be used to discover issues related to the web application structure or error pages produced by the application that have been publicly exposed. | ||
| − | + | Clearly, focusing only on the web application will not be an exhaustive test. It cannot be as comprehensive as the information possibly gathered by performing a broader infrastructure analysis. | |
Latest revision as of 05:27, 8 November 2012
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
4.2 Information Gathering
The first phase in security assessment is focused on collecting as much information as possible about a target application. Information Gathering is the most critical step of an application security test. The security test should endeavour to test as much of the code base as possible. Thus mapping all possible paths through the code to facilitate thorough testing is paramount.
This task can be carried out in many different ways.
By using public tools (search engines), scanners, sending simple HTTP requests, or specially crafted requests, it is possible to force the application to leak information, e.g., disclosing error messages or revealing the versions and technologies used.
4.2.5 Application Discovery (OWASP-IG-005) [rename to "Enumerate applications on webserver"]
Application discovery is an activity oriented to the identification of the web applications hosted on a web server/application server.
This analysis is important because often there is not a direct link connecting the main application backend. Discovery analysis can be useful to reveal details such as web applications used for administrative purposes. In addition, it can reveal old versions of files or artifacts such as undeleted, obsolete scripts, crafted during the test/development phase or as the result of maintenance.
4.2.1 Spiders, Robots and Crawlers (OWASP-IG-001) [rename to "Review webserver metafiles" ] This phase of the Information Gathering process consists of browsing and capturing resources related to the application being tested.
4.2.x Review webpage comments and metadata(OWASP-IG-00x) Review the webpage metadata, HTML, JavaScript comments for sensitive information and disabled links/scripts.
4.2.3 Identify application entry points (OWASP-IG-003)
Enumerating the application and its attack surface is a key precursor before any attack should commence. This section will help you identify and map out every area within the application that should be investigated once your enumeration and mapping phase has been completed.
4.2.x Identify application exit/handover points (OWASP-IG-00x)
Identify the functional exit points of the application and points where the application hands over to another application that may, or may not, be within scope of testing (e.g. handover to a payment gateway).
4.2.x Map paths through the application (OWASP-IG-00x)
Enumerating the application and its attack surface is a key precursor before any attack should commence. This section will help you identify and map out every area within the application that should be investigated once your enumeration and mapping phase has been completed.
4.2.x Testing Web Server Fingerprint (OWASP-IG-00x)
Application fingerprint is the first step of the Information Gathering process; knowing the version and type of a running web server allows testers to determine known vulnerabilities and the appropriate exploits to use during testing.
4.2.4 Testing Web Application Fingerprint (OWASP-IG-004)
Application fingerprint is the first step of the Information Gathering process; knowing the version and type of a running web server allows testers to determine known vulnerabilities and the appropriate exploits to use during testing.
4.2.6 Analysis of Error Codes (OWASP-IG-006)
During a penetration test, web applications may divulge information that is not intended to be seen by an end user. Information such as error codes can inform the tester about technologies and products being used by the application.
In many cases, error codes can be easily invoked without the need for specialist skills or tools, due to bad exception handling design and coding.
4.2.2 Search Engine Discovery/Reconnaissance (OWASP-IG-002)
Search engines, such as Google, can be used to discover issues related to the web application structure or error pages produced by the application that have been publicly exposed.
Clearly, focusing only on the web application will not be an exhaustive test. It cannot be as comprehensive as the information possibly gathered by performing a broader infrastructure analysis.
