Category:OWASP Project

An OWASP project is a collection of related tasks that have a defined roadmap and team members. OWASP project leaders are responsible for defining the vision, roadmap, and tasks for the project. The project leader also promotes the project and builds the team.

If you would like to start a new project please review the How to Start an OWASP Project guide. Please contact the Global Project Committee members to discuss project ideas and how they might fit into OWASP. All OWASP projects must be free and open and have their homepage on the OWASP portal. You can read all the guidelines in the Project Assessment Criteria.

Every project has an associated mail list. You can view all the lists, examine their archives, and subscribe to any of them on the OWASP Project Mailing Lists page. 

Release Quality Projects
Release quality projects are generally the level of quality of professional tools or documents. Tools and documents are organized into the following categories:


 * PROTECT - These are tools and documents that can be used to guard against security-related design and implementation flaws.
 * DETECT - These are tools and documents that can be used to find security-related design and implementation flaws.
 * LIFE CYCLE - These are tools and documents that can be used to add security-related activities into the Software Development Life Cycle (SDLC).

We have started the process of defining detailed guidelines which indicate what will be required from an OWASP Project in order for it to be classified an OWASP Release quality project (see Project Assessment Criteria). Please note that not all the projects below have been evaluated under this criteria and might be re-classified once that process is completed.

Beta Status Projects
Beta quality projects are complete and ready to use with documentation. Tools and documents are organized into the following categories:


 * PROTECT - These are tools and documents that can be used to guard against security-related design and implementation flaws.
 * DETECT - These are tools and documents that can be used to find security-related design and implementation flaws.
 * LIFE CYCLE - These are tools and documents that can be used to add security-related activities into the Software Development Life Cycle (SDLC).

We have defined what is required to reach Beta quality as an OWASP project (see Project Assessment Criteria). Not all projects have been evaluated yet under this criteria and might be re-classified once that process is completed. All projects starting with the OWASP Summer of Code 2008 have been assessed.

Alpha Status Projects
Alpha quality projects are generally usable but may lack documentation or quality review. Tools and documents are organized into the following categories:


 * PROTECT - These are tools and documents that can be used to guard against security-related design and implementation flaws.
 * DETECT - These are tools and documents that can be used to find security-related design and implementation flaws.
 * LIFE CYCLE - These are tools and documents that can be used to add security-related activities into the Software Development Life Cycle (SDLC).

We have started the process of defining detailed guidelines which indicate what will be required from an OWASP Project in order for it to be classified an OWASP Alpha quality project (see Project Assessment Criteria). Please note that the projects below have NOT been evaluated under this criteria and might be re-classified once that process is completed.

Inactive Projects
The criteria is still being developed. Tools and documents are organized into the following categories:


 * PROTECT - These are tools and documents that can be used to guard against security-related design and implementation flaws.
 * DETECT - These are tools and documents that can be used to find security-related design and implementation flaws.
 * LIFE CYCLE - These are tools and documents that can be used to add security-related activities into the Software Development Life Cycle (SDLC).