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"
m (minor tweak to how it works section) |
m (minor text tweaks) |
||
Line 7: | Line 7: | ||
==Introduction== | ==Introduction== | ||
<span style="color:#000000"> | <span style="color:#000000"> | ||
− | During 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 | + | During web application penetration testing, it is important to enumerate your application's attack surface. While Dynamic Application Security Testing (DAST) tools (such as [https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project OWASP ZAP] and [https://portswigger.net/ PortSwigger Burp Suite]) 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. |
</span> | </span> | ||
==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 | + | The Attack Surface Detector is available as a plugin to both 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: |
{{#ev:youtube|jUUJNRcmqwI}} | {{#ev:youtube|jUUJNRcmqwI}} | ||
Line 22: | Line 22: | ||
==How it Works== | ==How it Works== | ||
<span style="color:#000000"> | <span style="color:#000000"> | ||
− | The 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 | + | The 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 ZAP and Burp Suite to help improve testing coverage.</span> |
==Supported Frameworks== | ==Supported Frameworks== | ||
Line 53: | Line 53: | ||
==Acknowledgements== | ==Acknowledgements== | ||
<span style="color:#000000"> | <span style="color:#000000"> | ||
− | The Attack Surface Detection project is led by [https://securedecisions.com/ Secure | + | The Attack Surface Detection project is led by [https://securedecisions.com/ Secure Decisions] and was developed in collaboration with [https://www.denimgroup.com/ Denim Group] under a research grant sponsored by Department of Homeland Security (DHS) Science and Technology Directorate, Cyber Security Division (DHS S&T/CSD), BAA via contract number HHSP233201600058C. |
</span> | </span> | ||
Revision as of 22:08, 9 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 OWASP ZAP and PortSwigger Burp Suite) 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 where you can see a list of endpoints, endpoint details, and their corresponding requests: 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 ZAP and Burp Suite to help improve testing coverage. Supported Frameworks
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. LicensingThe Attack Surface Detector plugin is free to use. It is licensed under the link Mozilla Public License 2.0. AcknowledgementsThe Attack Surface Detection project is led by Secure Decisions and was developed in collaboration with Denim Group under a research grant sponsored by Department of Homeland Security (DHS) Science and Technology Directorate, Cyber Security Division (DHS S&T/CSD), BAA via contract number HHSP233201600058C. |
Project Resources
ASD Plugin for OWASP ZAP:ASD Plugin for PortSwigger Burp:ASD Command-Line Tool:Contact UsProject Leader: Ken Prole Email: [email protected] Related Projects
Classifications |