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 "OWASP Attack Surface Detector Project"
(updated project resources) |
(updates getting involved section) |
||
Line 12: | Line 12: | ||
==What is the Attack Surface Detector?== | ==What is the Attack Surface Detector?== | ||
The Attack Surface Detector tool figures out the endpoints of a web application, the parameters these endpoints accept, and the data type of those parameters. This includes the unlinked endpoints a spider won't find in client-side code, or optional parameters totally unused in client-side code. It also has the capability to calculate the changes in attack surface between two versions of an application.<br><br> | The Attack Surface Detector tool figures out the endpoints of a web application, the parameters these endpoints accept, and the data type of those parameters. This includes the unlinked endpoints a spider won't find in client-side code, or optional parameters totally unused in client-side code. It also has the capability to calculate the changes in attack surface between two versions of an application.<br><br> | ||
− | The Attack Surface Detector is available as a plugin to both OWASP ZAP and Burp Suite, and a Command Line Interface (CLI) tool. The CLI tool exports the attack surface as a JSON output, which can then be used by the ZAP and Burp Suite plugin. This is helpful for cases where the source code is not provided to the penetration tester directly. The CLI tool can also be used for other custom integration where you want to discover an application attack surface or changes in the attack surface.<br><br> | + | The Attack Surface Detector is available as a plugin to both OWASP ZAP and Burp Suite, and a Command Line Interface (CLI) tool is also available. The CLI tool exports the attack surface as a JSON output, which can then be used by the ZAP and Burp Suite plugin. This is helpful for cases where the source code is not provided to the penetration tester directly. The CLI tool can also be used for other custom integration where you want to discover an application attack surface or changes in the attack surface.<br><br> |
For a quick overview of the Attack Surface Detection tool, see this YouTube video. | For a quick overview of the Attack Surface Detection tool, see this YouTube video. | ||
Line 49: | Line 49: | ||
==Getting Involved== | ==Getting Involved== | ||
<span style="color:#000000"> | <span style="color:#000000"> | ||
− | Contributions to the Attack Surface Detector project are encouraged and welcome. | + | Contributions to the Attack Surface Detector project are encouraged and welcome. Additions of new features and enhancements can be provided through [https://github.com/secdec/attack-surface-detector-zap/issues GitHub]. We are eager to get user feedback, so please reach out to us or fill out this [https://www.surveymonkey.com/r/D2N87GB ASD survey]. |
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | | | style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
Revision as of 17:19, 7 September 2018
IntroductionDuring web application penetration testing, it is important to enumerate your application's attack surface. While Dynamic Application Security Testing (DAST) tools (such as Burp Suite and ZAP) are good at spidering to identify application attack surfaces, they will often fail to identify unlinked endpoints and optional parameters. These endpoints and parameters not found often go untested, which can leave your application open to an attacker. What is the Attack Surface Detector?The Attack Surface Detector tool figures out the endpoints of a web application, the parameters these endpoints accept, and the data type of those parameters. This includes the unlinked endpoints a spider won't find in client-side code, or optional parameters totally unused in client-side code. It also has the capability to calculate the changes in attack surface between two versions of an application. Below is a screenshot of the Burp Suite Attack Surface Detector plugin in action: How it WorksThe Attack Surface Detector performs static code analyses to identify web app endpoints by parsing routes and identifying parameters (with supported languages and frameworks). This data is made available in Burp Suite and OWASP ZAP to help improve testing coverage. Supported Frameworks
LicensingThe Attack Surface Detector plugin is free to use. It is licensed under the link Mozilla Public License 2.0. Getting InvolvedContributions to the Attack Surface Detector project are encouraged and welcome. Additions of new features and enhancements can be provided through GitHub. We are eager to get user feedback, so please reach out to us or fill out this ASD survey. |
Project Resources
ASD Plugin for OWASP ZAP:ASD Plugin for PortSwigger Burp:ASD command-line tool:Project LeaderKen Prole Email: [email protected] Related Projects
Classifications
|