OWASP Attack Surface Detector Project - Revision history

KenProle: Logo update

2018-10-08T14:31:17Z

Logo update

KenProle at 13:40, 17 September 2018

2018-09-17T13:40:13Z

KenProle: /* How it Works */

2018-09-17T13:37:01Z

‎How it Works

KenProle at 13:33, 17 September 2018

2018-09-17T13:33:08Z

KenProle at 13:31, 17 September 2018

2018-09-17T13:31:53Z

KenProle at 02:03, 11 September 2018

2018-09-11T02:03:48Z

KenProle at 16:31, 10 September 2018

2018-09-10T16:31:13Z

KenProle at 16:30, 10 September 2018

2018-09-10T16:30:41Z

KenProle at 14:32, 10 September 2018

2018-09-10T14:32:43Z

KenProle at 01:43, 10 September 2018

2018-09-10T01:43:59Z

@@ Line 1: / Line 1: @@
 <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
@@ Line 4: / Line 5: @@
 | style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
 <span style="color:#ff0000"></span>
 ==Introduction==
 <span style="color:#000000">

@@ Line 25: / Line 25: @@
 <span style="color:#000000">
 The Attack Surface Detector performs static code analyses to identify web application 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>
@@ Line 71: / Line 69: @@
 == Project Resources ==
 <span style="color:#ff0000"></span>
 ====ASD Plugin for OWASP ZAP:====
 [https://github.com/secdec/attack-surface-detector-zap/releases Download ZAP Plugin]

@@ Line 24: / Line 24: @@
 ==How it Works==
 <span style="color:#000000">
-The Attack Surface Detector performs static code analyses to identify web application 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>
+The Attack Surface Detector performs static code analyses to identify web application 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 Languages and Frameworks==

@@ Line 7: / Line 7: @@
 ==Introduction==
 <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 [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, optional parameters, and uncover parameter datatypes and name. These endpoints and parameters not found often go untested, which can leave your application open to an attacker.
+	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, optional parameters, and parameter datatypes and name. These endpoints and parameters not found often go untested, which can leave your application open to an attacker.
 </span>

@@ Line 7: / Line 7: @@
 ==Introduction==
 <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 [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.
+	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, optional parameters, and uncover parameter datatypes and name. These endpoints and parameters not found often go untested, which can leave your application open to an attacker.
 </span>
 ==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>
+The Attack Surface Detector tool uncovers 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>
 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>

@@ Line 45: / Line 45: @@
 ==Roadmap==
-We continue to improve the attack surface detection accuracy for existing supported languages and frameworks, and we are looking to add additional language support, particularly for PHP and Python. If there are any PHP or Python developers that are looking to contribute, [mailto:info@securedecisions.com lease let us know].<br>
+We continue to improve the attack surface detection accuracy for existing supported languages and frameworks, and we are looking to add additional language support, particularly for PHP and Python. If there are any PHP or Python developers that are looking to contribute, [mailto:info@securedecisions.com please let us know].<br>
-We are also looking to extend ASD for use in automated headless usage of ZAP and Burp and move the ASD ZAP plugin out of alpha classification, which requires [https://github.com/zaproxy/zap-extensions/wiki/AddOnsBeta internationalization]. If anyone can help, we would love for contributions.<br>
+We are also looking to extend ASD for use in automated headless usage of ZAP and Burp and move the ASD ZAP plugin out of alpha classification, which requires [https://github.com/zaproxy/zap-extensions/wiki/AddOnsBeta internationalization]. If anyone can help, we would love your contributions.<br>
 Finally, we are really interested in what the community thinks will help improve ASD and we will adjust our roadmap based on that feedback.
@@ Line 61: / Line 61: @@
 ==Acknowledgements==
 <span style="color:#000000">
-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.
+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 the Department of Homeland Security (DHS) Science and Technology Directorate, Cyber Security Division (DHS S&T/CSD), BAA via contract number HHSP233201600058C.
 </span>

← Older revision		Revision as of 14:32, 10 September 2018
Line 94:		Line 94:

	[https://github.com/secdec/attack-surface-detector-cli GitHub Source Code]		[https://github.com/secdec/attack-surface-detector-cli GitHub Source Code]
		+
		+	== News and Events ==
		+	* <span style="background: #66CCFF; font-size:85%;padding:2px;">24 Aug 2018</span> [https://github.com/secdec/attack-surface-detector-zap/releases Version 1.1.2 of the ASD ZAP plugin is out!]
		+	* <span style="background: #66CCFF; font-size:85%;padding:2px;">23 Aug 2018</span> [https://github.com/secdec/attack-surface-detector-burp/releases Version 1.1.2 of the ASD Burp Suite plugin is out!]
		+	* <span style="background: #66CCFF; font-size:85%;padding:2px;">20 Jul 2018</span> [https://github.com/secdec/attack-surface-detector-cli/releases Version 1.2.16 of the ASD CLI is out!]

	== Contact Us ==		== Contact Us ==

@@ Line 43: / Line 43: @@
 </span>
 ==Roadmap==
@@ Line 53: / Line 50: @@
 Finally, we are really interested in what the community thinks will help improve ASD and we will adjust our roadmap based on that feedback.
 ==Licensing==