This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
SpoC 007 - Orizon Project - Progress Page
From OWASP
News
22nd August 2007 - Orizon release 0.40 is available at sourceforge site. This is an important milestone in the development process. Safe coding recipes APIs are working and the class handling source code being reviewed is now capable of applying a check over the source code xml representation. In fact, static code review is possible by now.
13th July 2007 - The project status as Spoc 2007 start is summarized in the following:
- java sources are translated into XML using JDK6 APIs;
- Orizon classes are in a refactoring stage in order to reflect a better approach in design phase;
- library containing checks is now a Zip file instead of a plain XML file. The library file will contain "receipts", XML files containing security checks grouped by category.
What is missing by now is some checks. I'm looking the web in order to collect "coding best practices" and trying to formalize them in XML.
Next actions
Id | Description | Priority | Blocking? |
---|---|---|---|
OR-1 | Collecting safe coding best practices | High | No |
OR-2 | Creating APIs for XML reports | Low | No |
OR-3 | Creating code to handle dynamic test cases generation | Medium | No |
SpoC 2007 Goals
Goal | Completeness (%) | Included in Orizon release | Estimated inclusion time |
---|---|---|---|
Static analysis | 70% | 0.45 | August 2007 (the end of) |
Dynamic analysis | 0% | 0.50 | September 2007 |
Creating a library with 30 checks included | 33,34% (10 tests out of 30) | 0.50 | September 2007 (mid of) |
Support for C language | 0% | 0.60 | November 2007 |
Capability to export results in XML with customizable CSS | 10% | 0.50 | September 2007 |