Category:OWASP Tools Project - Revision history

Kait Disney-Leugers at 19:54, 23 January 2014

2014-01-23T19:54:15Z

Kait Disney-Leugers at 18:35, 23 January 2014

2014-01-23T18:35:43Z

Kait Disney-Leugers at 02:02, 23 January 2014

2014-01-23T02:02:40Z

Vishal Garg at 12:58, 13 March 2013

2013-03-13T12:58:01Z

Vishal Garg at 22:39, 12 June 2010

2010-06-12T22:39:55Z

Paulo Coimbra at 17:48, 9 March 2010

2010-03-09T17:48:26Z

Vishal Garg at 18:36, 19 December 2009

2009-12-19T18:36:12Z

Vishal Garg: Undo revision 70114 by Vishal Garg (Talk)

2009-09-29T21:17:52Z

Undo revision 70114 by Vishal Garg (Talk)

Vishal Garg at 20:51, 29 September 2009

2009-09-29T20:51:45Z

Vishal Garg at 12:23, 15 September 2009

2009-09-15T12:23:48Z

@@ Line 4: / Line 4: @@
 ! width="500" align="center" | <br>
 |-
-| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/Category:OWASP_Project]]
+| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
 | align="right" |

@@ Line 1: / Line 1: @@
-[[Image:OWASP Inactive Banner.jpg|1155px]]
+{|
 [[Category:OWASP Project|Tools Project]]
 [[Category:OWASP Document]]

← Older revision		Revision as of 02:02, 23 January 2014
Line 1:		Line 1:
		+	[[Image:OWASP Inactive Banner.jpg\|1155px]]
	[[Category:OWASP Project\|Tools Project]]		[[Category:OWASP Project\|Tools Project]]
	[[Category:OWASP Document]]		[[Category:OWASP Document]]

@@ Line 36: / Line 36: @@
 | project_description = The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their effectiveness.
 | project_license = [http://creativecommons.org/licenses/by-sa/3.0/ '''Creative Commons Attribution ShareAlike 3.0''']
-| leader_name = Vishal Garg
+| leader_name =
 | leader_email =
-| leader_username = Vishal Garg
+| leader_username =
-| maintainer_name = Vishal Garg
+| maintainer_name =
 | maintainer_email =
-| maintainer_username = Vishal Garg
+| maintainer_username =
 | contributor_name1 = Dave van Stein
 | contributor_email1 =
@@ Line 101: / Line 101: @@
 | current_release_download_link =
 | current_release_rating =
-| current_release_leader_name = Vishal Garg
+| current_release_leader_name =
 | current_release_leader_email =
-| current_release_leader_username = Vishal Garg
+| current_release_leader_username =
 | current_release_details =
 | last_reviewed_release_name =

← Older revision		Revision as of 22:39, 12 June 2010
Line 4:		Line 4:

	==== Main ====		==== Main ====
		+
		+	== Vision ==
		+
		+	Our vision is to provide access to application security tools, resources and eductional material to everyone interested to learn and work in application security. We aim to achieve this by creating a repository of all the available resoruces at one place.

	== Overview ==		== Overview ==

← Older revision		Revision as of 18:36, 19 December 2009
Line 19:		Line 19:
	* Testing the tools against test applications to see how effectively the tool meets the rating criteria		* Testing the tools against test applications to see how effectively the tool meets the rating criteria
	* Provide rating to the tools based on their efficiency and performance		* Provide rating to the tools based on their efficiency and performance
−
−
−	~~== Project Progress ==~~
−
−	* As of August 2009, in its initial stage, we are in the process of gathering information on tools; and defining the rating ceiteria and the test procedure for identified tools.
−	* The planned deadline for identification of first set of tools and defining rating criteria and test procedure is 31 October 2009.

@@ Line 9: / Line 9: @@
 New open source and commercial web application security tools are released almost every day. These tools are used either to detect vulnerabilities within web applications or to protect web applications from exploitation of potential vulnerabilties that may be present in these applications. With so many tools at hand, it may sometimes be difficult to make a decision about the selection of a tool that best meets your requirements.
-The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and evaluate them according to a predefind criteria to assess their efficiency and performance.
+The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their efficiency and performance.
 == Project Roadmap ==
-* Defining categories of tools
+* Defining categories for tools
 * Identification of tools within these categories
-* Define evaluation criteria and the test procedure for identified tools
+* Define rating criteria and the test procedure for identified tools
-* Testing the tools against test applications to see how effectively these tools meet the evaluation criteria
+* Testing the tools against test applications to see how effectively the tool meets the rating criteria
 * Provide rating to the tools based on their efficiency and performance
@@ Line 23: / Line 23: @@
 == Project Progress ==
-* As of August 2009, in its initial stage, we are in the process of gathering information on tools; and defining the evaluation ceiteria and the test procedure for identified tools.
+* As of August 2009, in its initial stage, we are in the process of gathering information on tools; and defining the rating ceiteria and the test procedure for identified tools.
-* The planned deadline for identification of first set of tools and defining evaluation criteria and test procedure is 31 October 2009.
+* The planned deadline for identification of first set of tools and defining rating criteria and test procedure is 31 October 2009.

← Older revision		Revision as of 12:23, 15 September 2009
Line 9:		Line 9:
	New open source and commercial web application security tools are released almost every day. These tools are used either to detect vulnerabilities within web applications or to protect web applications from exploitation of potential vulnerabilties that may be present in these applications. With so many tools at hand, it may sometimes be difficult to make a decision about the selection of a tool that best meets your requirements.		New open source and commercial web application security tools are released almost every day. These tools are used either to detect vulnerabilities within web applications or to protect web applications from exploitation of potential vulnerabilties that may be present in these applications. With so many tools at hand, it may sometimes be difficult to make a decision about the selection of a tool that best meets your requirements.

−	The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their ~~effectiveness~~.	+	The OWASP Tools Project has been created to provide unbiased, practical information and guidance about application security tools that are used to detect vulnerabilities or to protect against vulnerabilities. The goal of this project is to identify any available tools, categorise them and rate them according to a predefind criteria to assess their efficiency and performance.