The Testing guide originated in 2003 with Dan Cuthbert as one of the original editors. It was handed over to Eoin Keary in 2005 and transformed into a wiki.

The Testing guide originated in 2003 with Dan Cuthbert as one of the original editors. It was handed over to Eoin Keary in 2005 and transformed into a wiki.

Being a wiki it is easier for people to contribute and should make updating much easier.

Being a wiki it is easier for people to contribute and should make updating much easier.

−

Matteo Meucci has decided to take on the Testing guide (which is not a trivial feat) and update it.

+

[[User:Mmeucci|Matteo Meucci]] has decided to take on the Testing guide (which is not a trivial feat) and update it.

'''Problem to be Addressed'''

'''Problem to be Addressed'''

Line 18:

Line 24:

A reference to the testing community that is updated by the community. It should provide many of the answers one would look for when testing the security of a web application.

A reference to the testing community that is updated by the community. It should provide many of the answers one would look for when testing the security of a web application.

−

== Goals and Deliverables ==

+

=== Goals and Deliverables ===

The guide to be updated with a defined list of topics and the current guide reviewed.

The guide to be updated with a defined list of topics and the current guide reviewed.

Line 28:

Line 34:

A defined list of additional topics shall then be added. They must be reviewed also for quality.

A defined list of additional topics shall then be added. They must be reviewed also for quality.

* Please refer to the [http://www.owasp.org/index.php/OWASP_Autumn_of_Code_2006_-_Projects:_Testing_Guide_-_Progress progress page] for updated information about the project

* Please refer to the [http://www.owasp.org/index.php/OWASP_Autumn_of_Code_2006_-_Projects:_Testing_Guide_-_Progress progress page] for updated information about the project

−

Here is the working [http://www.owasp.org/index.php/OWASP_Testing_Guide_v2_Table_of_Contents Testing Guide] to be reviewed

+

Here is the working [http://www.owasp.org/index.php/OWASP_Testing_Guide_v2_Table_of_Contents Testing Guide]<br>

+

Here is the [http://www.owasp.org/index.php/OWASP_Testing_Guide_v2_Review_Panel Review Panel]

−

==Feedback and Participation==

+

===Feedback and Participation===

We hope you find the information in the OWASP Testing project useful. Please contribute back to the project by sending your comments, questions, and suggestions to the OWASP Testing mailing list. Thanks!

We hope you find the information in the OWASP Testing project useful. Please contribute back to the project by sending your comments, questions, and suggestions to the OWASP Testing mailing list. Thanks!

Line 51:

Line 58:

A revised and updated Testing Guide which shall be more extensive than ever before.

A revised and updated Testing Guide which shall be more extensive than ever before.

−

== Risks and Rewards ==

+

=== Risks and Rewards ===

The size of this task can not be underestimated. It is a large time-consuming task.

The size of this task can not be underestimated. It is a large time-consuming task.

Project History

Background and Motivation

History Behind Project
The Testing guide originated in 2003 with Dan Cuthbert as one of the original editors. It was handed over to Eoin Keary in 2005 and transformed into a wiki.
Being a wiki it is easier for people to contribute and should make updating much easier.
Matteo Meucci has decided to take on the Testing guide (which is not a trivial feat) and update it.

Problem to be Addressed
Many additional sections should be updated and reviewed. Also additional areas of discovery should be addressed. the guide currently covers alot but could (and should) cover much more.

Benefit to OWASP Members and Community
A reference to the testing community that is updated by the community. It should provide many of the answers one would look for when testing the security of a web application.

Goals and Deliverables

The guide to be updated with a defined list of topics and the current guide reviewed.
the list of additional topics has been agreed with the AoC.

Plan of Approach
A review of the existing material is required first.
Any material that required an update shall be rectified then.
A defined list of additional topics shall then be added. They must be reviewed also for quality.

Please refer to the progress page for updated information about the project

Feedback and Participation

We hope you find the information in the OWASP Testing project useful. Please contribute back to the project by sending your comments, questions, and suggestions to the OWASP Testing mailing list. Thanks!

To join the OWASP Testing mailing list or view the archives, please visit the subscription page.

If you want to contribute, please view the Index and post a message on ml. Tell us what par. you want to write, then read the rule to write.