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. 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).

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.
 * Projects are listed below.

Beta Status Projects

 * Beta quality projects are complete and ready to use with documentation.
 * Projects are listed below.

Alpha Status Projects

 * Alpha quality projects are generally usable but may lack documentation or quality review.
 * Projects are listed below.

Inactive Projects

 * Inactive projects are unrated projects (projects that have not reached any one of Alpha, Beta, or Release status) which may have been abandoned. Efforts are being made to contact project leads to determine status and plans for future work.
 * Projects are listed below.