Project Information:template WSFuzzer Project - First Review - Self Evaluation - A

From OWASP
Jump to: navigation, search

Click here to return to the previous page.

FINAL REVIEW
PART I

Project Deliveries & Objectives

OWASP WSFuzzer Project's Goals

QUESTIONS ANSWERS

1. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please exemplify writing down those of them that haven't been realised.

Based on field feedback WSFuzzer is an active part of a web application pen testers toolkit. Hence in that respect the main objective of the software has been realized. Moreover from a functional perspective WSFuzzer does effectively automate the SOAP fuzzing process. The area of non-realization for WSFuzzer would be in the integration with other toolsets, or making the WSFuzzer functionality available to other tools.

2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.

Automating SOAP Fuzzing - 100%
Becoming part of a pen testers toolkit - 100%
Integration with other tools - 0%

3. What kind of help is required either from the Reviewers or from the OWASP Community?

Feedback from the community would be great. We get feedback from the field but not it is not OWASP centric. Technical help is ultimately what is necessary, coding and testing in particular to make WSFuzzer the best it can be.
PART II

Assessment Criteria

OWASP Project Assessment Criteria

QUESTIONS ANSWERS

1. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Alpha Quality status?

WSFuzzer is now changed over to use the LGPL License.
The "Alpha Quality Tool project tag" is missing, this project was initiated as Beta within OWASP.

2. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Beta Quality status?

WSFuzzer does not have a "common About Box or help menu" since it does not have a GUI.
There is no build instruction neither because it is written in a scripting language, there is no compilation process.
I have no reviewers for the project.

3. Having into consideration the OWASP Project Assessment Methodology which criteria, if any, haven’t been fulfilled in terms of Release Quality status?

Fortify and Findbugs are Java centric, WSFuzzer is written in Python.
I don't have any Powerpoint presentations for WSFuzzer.

4. What kind of help is required either from the Reviewers or from the OWASP Community?

The project now has 1 reviewer so getting a second to fulfill this type of requirement is a real need.