Difference between revisions of "Testing: Conduct search engine discovery/reconnaissance for information leakage (OTG-INFO-001)"
|Line 50:||Line 50:|
== Remediation ==
== Remediation ==
Revision as of 07:08, 21 July 2013
This article is part of the new OWASP Testing Guide v4.
At the moment the project is in the REVIEW phase.
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: http://www.owasp.org/index.php/OWASP_Testing_Project
There are direct and indirect elements to Search engine discovery and reconnaissance. Direct methods relate to searching the Google Index and remove the associated web content from the Google Cache. Indirect methods relate to gleaning sensitive design and configuration information by searching forums, newsgroups and tendering websites.
Once the GoogleBot has completed crawling, it commences indexing the web page based on tags and associated attributes, such as <TITLE>, in order to return the relevant search results. 
If the robots.txt file is not updated during the lifetime of the web site, then it is possible for web content not intended to be included in Google's Search Results to be returned.
Therefore, it must be removed from the Google Cache.
To understand what sensitive design and configuration information is exposed of the application/system/organisation both directly (on the organisation's website) or indirectly (on a third party website)
How to Test
Black Box Testing
Using the advanced "site:" search operator, it is possible to restrict Search Results to a specific domain .
Google provides the Advanced "cache:" search operator , but this is the equivalent to clicking the "Cached" next to each Google Search Result. Hence, the use of the Advanced "site:" Search Operator and then clicking "Cached" is preferred.
The Google SOAP Search API supports the doGetCachedPage and the associated doGetCachedPageResponse SOAP Messages  to assist with retrieving cached pages. An implementation of this is under development by the OWASP "Google Hacking" Project.
To find the web content of owasp.org indexed by Google Cache the following Google Search Query is issued:
To display the index.html of owasp.org as cached by Google the following Google Search Query is issued:
Gray Box testing and example
Grey Box testing is the same as Black Box testing above.
 FoundStone SiteDigger - http://www.mcafee.com/uk/downloads/free-tools/sitedigger.aspx
 Google Hacker - http://yehg.net/lab/pr0js/files.php/googlehacker.zip
 Stach & Liu's Google Hacking Diggity Project - http://www.stachliu.com/resources/tools/google-hacking-diggity-project/
 "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" - http://www.google.com/support/webmasters/bin/answer.py?answer=70897
 "Operators and More Search Help" - http://support.google.com/websearch/bin/answer.py?hl=en&answer=136861
Carefully consider the sensitivity of design and configuration information before it is posted online. Periodically review the sensitivity of design and configuration information that is posted online.