Projects/OWASP Testing Project/Releases/Testing Guide V 4.0/Roadmap - Revision history

Mmeucci at 16:14, 23 July 2010

2010-07-23T16:14:28Z

Mmeucci at 16:38, 22 July 2010

2010-07-22T16:38:34Z

Mmeucci at 14:36, 18 July 2010

2010-07-18T14:36:44Z

Mmeucci at 14:35, 18 July 2010

2010-07-18T14:35:39Z

Mmeucci at 14:33, 18 July 2010

2010-07-18T14:33:45Z

Mmeucci at 14:22, 18 July 2010

2010-07-18T14:22:05Z

Mmeucci at 14:20, 18 July 2010

2010-07-18T14:20:50Z

Mmeucci at 22:55, 16 July 2010

2010-07-16T22:55:35Z

Mmeucci at 22:54, 16 July 2010

2010-07-16T22:54:52Z

Mmeucci at 22:52, 16 July 2010

2010-07-16T22:52:57Z

@@ Line 27: / Line 27: @@
 ** 15th December 2010: Create the RC1,
 ** 15th January 2011: Release the version 4.
 * '''Project Roadmap'''

@@ Line 29: / Line 29: @@
 * '''Project Roadmap'''
-- 1st phase: Brainstorming
+- 1st phase: Brainstorming<br>
 th July 2010: starting a brainstorming with the OWASP Leaders and
-project contributors to share goals and project's objectives.
+project contributors to share goals and project's objectives.<br>
 The following are the main improvements we have to realize:
 - Inserting new testing techniques, OWASP Top10 update: HTTP Verb
@@ Line 37: / Line 37: @@
 Object References, Insecure Cryptographic Storage, Failure to Restrict
 URL Access, Insufficient Transport Layer Protection, Unvalidated
-Redirects and Forwards.
+Redirects and Forwards.<br>
-- Review and improve all the sections in v3,
+- Review and improve all the sections in v3<br>
 - Create a more readable guide, eliminating some sections that are not
 really useful, Rationalize some sections as Session Management
-Testing,
+Testing<br>
-- Create a new section: Client side security and Firefox extensions testing.
+- Create a new section: Client side security and Firefox extensions testing<br>
-- Create a test case for each test to perform using O2 platform
+- Create a test case for each test to perform using O2 platform<br>
-- 2nd phase: Set-up the team
+- 2nd phase: Set-up the team<br>
 th August: Introduce the new project to the OWASP mailing list
 seeking for contributors. We need to involve also the final users of
@@ Line 51: / Line 51: @@
 they would like to improve that).
-- 3rd phase: Create a new Index
+- 3rd phase: Create a new Index<br>
 th September: creating a new table of contents of the OTGv4
 assigning a task for each contributor.
@@ Line 57: / Line 57: @@
 http://www.owasp.org/index.php/OWASP_Testing_Guide_v3_Table_of_Contents
-- 4th phase:  Writing and reviewing
+- 4th phase:  Writing and reviewing<br>
-st October 2010: Starting writing
+st October 2010: Starting writing<br>
-st November 2010:Starting the first review phase,
+st November 2010:Starting the first review phase<br>
-th November 2010: Starting writing articles II phase,
+th November 2010: Starting writing articles II phase<br>
-st December 2010: Starting the second review phase,
+st December 2010: Starting the second review phase<br>
-th December 2010: Create the RC1,
+th December 2010: Create the RC1<br>
-th January 2011: Release the version 4.
+th January 2011: Release the version 4.<br>
 ----

@@ Line 1: / Line 1: @@
-This is the OWASP Testing Guide Project for v4.<br>
+This is the OWASP Testing Guide Project Roadmap for v4.<br>
 You can download the stable version v3 [http://www.owasp.org/images/5/56/OWASP_Testing_Guide_v3.pdf here] <br>
@@ Line 105: / Line 105: @@
 to this set of vulnerabilities telling how to write code to protect
 the application for each vulnerability.

← Older revision		Revision as of 14:35, 18 July 2010
Line 1:		Line 1:
		+	This is the OWASP Testing Guide Project for v4.<br>
		+	You can download the stable version v3 [http://www.owasp.org/images/5/56/OWASP_Testing_Guide_v3.pdf here] <br>
		+
		+	Back to the OWASP Testing Guide Project:
		+	http://www.owasp.org/index.php/OWASP_Testing_Project
		+
		+
	*'''Introduction and Project purpose for v4'''		*'''Introduction and Project purpose for v4'''
	The OWASP Testing Guide v3 includes a "best practice" penetration		The OWASP Testing Guide v3 includes a "best practice" penetration

@@ Line 12: / Line 12: @@
 * '''Project Deadlines'''
 ** 17th July 2010: Start a brainstorming for the new index starting from "Release Description",
-** 5th August 2010: Create the new index and the new team,
+** 15th August 2010: Create the new index and the new team,
-** 6th August 2010: Starting writing articles,
+** 15th September 2010: Starting writing articles,
-** 15th September 2010: Starting the first review phase,
+** 1st October 2010: Starting writing
-** 15th October 2010: Starting writing articles II phase,
+** 1st November 2010:Starting the first review phase,
-** 15th November 2010: Starting the second review phase,
+** 15th November 2010: Starting writing articles II phase,
 ** 15th December 2010: Create the RC1,
 ** 15th January 2011: Release the version 4.
@@ Line 62: / Line 63: @@
 '''18th July 2010'''
-* Start: 1st phase: brainstorming
+* Start 1st phase: brainstorming
 Now, we are at the 1st phase, and I think this phase it's the most
 important to create a solid project as we saw from the last versions.

@@ Line 1: / Line 1: @@
-*Project Roadmap
+Introduction and Project purpose for v4:
-**Introduce the new project to the testing Guide mailing list,
+============================
-**Involve the contributors: we need to involve also the final users of the Testing Guide (for example Banking Companies to understand how they would like to improve that).
+The OWASP Testing Guide v3 includes a "best practice" penetration
-** Update the OWASP vulnerability database. I mean we can update this:<br>
+testing framework which users can implement in their own organizations
-** http://www.owasp.org/index.php/Testing_Checklist<br>
+and a "low level" penetration testing guide that describes techniques
-** Inserting new testing techniques, OWASP Top10 update: HTTP Verb tampering, HTTP Parameter Pollutions, URL Redirection, Insecure Direct Object References, Insecure Cryptographic Storage, Failure to Restrict URL Access, Insufficient Transport Layer Protection, Unvalidated Redirects and Forwards.
+for testing most common web application and web service security
-** Create a test case for each test to perform using O2 platform
+issues. Nowadays the Testing Guide has become the standard to perform
-** Review and improve all the sections in v3,
+a Web Application Penetration Testing and many Companies all around
-** Create a more readable guide, eliminating some sections that are not really useful, Rationalize some sections as Session Management Testing,
+the world have adopted it.
-** Create a new section: Client side security and Firefox extensions testing.
+It is vital for the project mantaining an updated project that
-* Project Plan:
+* Project Deadlines:
 ** 17th July 2010: Start a brainstorming for the new index starting from "Release Description",
 ** 5th August 2010: Create the new index and the new team,
@@ Line 19: / Line 20: @@
 ** 15th December 2010: Create the RC1,
 ** 15th January 2011: Release the version 4.