Click here to return to the previous page.
| 50% REVIEW PROCESS
|
|
Project Deliveries & Objectives
|
OWASP Classic ASP Security Project's Deliveries & Objectives
|
| 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.
|
- Creation of a Common Object Repository for ASP applications based on OWASP ESAPI Project including objects and/or references to libraries for security applications all this aligned with OWASP Top10 and OWASP Guide. (In progress)
- Create Documentation aligned to OWASP Code Review Project Checklist providing additional technology-specific checks. (Done)
- Addition of expression for Code Review Tool to support Classic ASP applications. (Done)
- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (missing)
- This same module will compliment the OWASP Validation Documentation Project. (missing)
|
|
2. At what extent have the project deliveries & objectives been accomplished? Having in consideration the assumed ones, please quantify in terms of percentage.
|
- Creation of a Common Object Repository for ASP applications based on OWASP ESAPI Project (50% or ESAPI classes)
- Create Documentation aligned to OWASP Code Review Project Checklist providing additional technology-specific checks. (100% it it published in OWASP site by now)
- Addition of expression for Code Review Tool to support Classic ASP applications. (100% DB update with ASP keyworkds sent to code review project owner)
- Implementation of Version 1 of Stinger for ASP either by using an installable COM library or ISAPI. (0%)
- This same module will compliment the OWASP Validation Documentation Project. (0%)
|
|
3. What kind of help is required either from the Reviewers or from the OWASP Community?
|
None so far, eveything is going smooth :)
|
