Category:OWASP Project

= Welcome = {| style="width: 100%;" {| style="border: 0px solid ; background: transparent none repeat scroll 0% 0%; width: 100%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;"
 * style="width: 100%; color: rgb(0, 0, 0);" |
 * style="width: 100%; color: rgb(0, 0, 0);" |
 * style="width: 95%; color: rgb(0, 0, 0);" |
 * style="width: 95%; color: rgb(0, 0, 0);" |

Welcome to the OWASP Global Projects Page
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. OWASP currently has over 142 active projects, and new project applications are submitted every week.

This is one of the most popular divisions of OWASP as it gives members an opportunity to freely test theories and ideas with the professional advice and support of the OWASP community. Every project has an associated mail list. You can view all the lists, examine their archives, and subscribe to any project by visiting the OWASP Project Mailing Lists page. A summary of recent project announcements is available on the OWASP Updates page.

Download the OWASP Projects Handbook 2013

Start a New OWASP Project

Project Online Resources

OWASP Project Inventory
All OWASP tools, document, and code library projects are organized into the following categories:


 * Incubator Projects: OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway.


 * Lab Projects: OWASP Labs projects represent projects that have produced an OWASP reviewed deliverable of value.


 * Flagship Projects: The OWASP Flagship designation is given to projects that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole.

Who Should Start an OWASP Project?

 * Application Developers.
 * Software Architects.
 * Information Security Authors.
 * Those who would like the support of a world wide professional community to develop or test an idea.
 * Anyone wishing to take advantage of the professional body of knowledge OWASP has to offer.

Contact Us
If you have any questions, please do not hesitate to contact the OWASP Projects Manager, Samantha Groves by using the form provided here. Please allow five working days for your question or comment to be answered. This is due to the large amount of queries the foundation staff receive every day. We thank you for your patience.

Social Media
We recommend using the links below to find our official OWASP social media channels. These are a great way to keep in touch with the different initiatives going on at OWASP throughout the world. They are all updated regularly by chapter leaders, project leaders, the OWASP Board Members, and our OWASP Staff. If you have any questions or concerns about any of these accounts, please drop us a line using our "Contact Us" form found above.




 * }


 * style="border: 3px solid rgb(204, 204, 204); vertical-align: top; width: 95%; font-size: 95%; color: rgb(0, 0, 0);" |










 * style="width: 110px; font-size: 95%; color: rgb(0, 0, 0);" |
 * }

= Starting a New Project =

So you want to start a project...
Starting an OWASP Project is easy. You don't have to be an application security expert. You just have to have the drive and desire to make a contribution to the application security community.

Here are some of the guidelines for running a successful OWASP project:


 * The best OWASP projects are strategic - they make it easier to produce secure applications by filling a gap in the application security knowledge-base or technology support.


 * You can run a single person project, but it's usually best to get the community involved. You should be prepared to support a mailing list, build a team, speak at conferences, and promote your project.


 * You can contribute existing documents or tools to OWASP! Assuming you have the intellectual property rights to a work, you can open it to the world as an OWASP Project. Please coordinate this with OWASP by contacting owasp(at)owasp.org.


 * Available Grants to consider if you need funding - Click Here


 * You should promote your project through the OWASP channels as well as by outside means. Get people to blog about it!

Creating a new project
The first thing you have to do if you want to start a new project is submit a new OWASP Project application. Please submit a new project application here.

A - PROJECT
 * You will need to gather the following information together for your application:
 * 1) Project Name,
 * 2) Project purpose / overview,
 * 3) Project Roadmap,
 * 4) Project links (if any) to external sites,
 * 5) Project License,
 * 6) Project Leader name,
 * 7) Project Leader email address,
 * 8) Project Leader wiki account - the username (you'll need this to edit the wiki),
 * 9) Project Contributor(s) (if any) - name email and wiki account (if any),
 * 10) Project Main Links (if any).


 * Check out the Guidelines for OWASP Projects.
 * Grant Spending Policy
 * Project Spending Policy
 * Project Sponsorship Operational Guidelines

Funding your Project
An OWASP project does not receive any funding for development at project inception; however, a new project does have the opportunity to submit a request to receive funds if they are available for the year. Additionally, project leaders have the option of seeking sponsorship from outside organizations, but project leaders are required to seek funding through their own initiative. Please contact the OWASP Projects Manager for more information.

Project Release
As your project reaches a point that you'd like OWASP to assist in its promotion, the will need the following information to help spread the word about your project:


 * 1) Short 5 sentence paragraph outlining what your project is about, what you hope to accomplish with your project, what value your project brings to software security, and contributor and project leader names and contact information.
 * 2) Link to your wiki page.
 * 3) Link to your code repository or a link to where readers can download your project.
 * 4) Latest Release description answering the following questions: What is it?, What does it do?, Where can I get it?, Who should I contact if something goes wrong?.

Project Process Forms
These forms were created to help project leaders, and those interested in a going through a process in the OWASP projects infrastructure. They facilitate the management of each query based on the specific task an applicant will need help with. The forms are described below, and they are linked with their designated online application form.


 * Project Transition Application:The OWASP project transition form gives current project leaders an easy way of handing over project administration information to individuals wishing to take over a project.


 * Project Review Application:This form is for current project leaders to request a review of their project based on OWASP graduation criteria. The aim is to designate an OWASP volunteer to review these projects within 3 months time.


 * Project Donation Application:This form is for projects outside of the OWASP project infrastructure. Project Leaders for these open source projects can choose to partner or give their project to OWASP directly through this form.


 * Project Adoption Request:This form is used when someone is interested in adopting an archived project.


 * Project Abandonment Request:The OWASP project abandonment form gives current project leaders an easy way of letting the OWASP Foundation know that they wish to resign their project leader duties. This form should be used when no replacement project leader exists to take over these duties.


 * Incubator Project Graduation Application:This application form is for Incubator Projects to apply for Labs Project status.

= Online Resources =

Project Online Resources
= Project Assessments =

OWASP Project Lifecycle
The OWASP Projects Lifecycle represents a balance between keeping a very loose structure around OWASP projects, and ensuring that OWASP consumers are not confused about a project’s maturity and quality. The lifecycle stage allows consumers to easily identify mature projects, and projects that are proofs of concept, experimental, and classified as prototypes in their current state. The greater the maturity of the project, the greater the level of responsibility for the project leader. These responsibilities are not trivial as OWASP provides incentives and benefits (Section 7) for projects who take on these added responsibilities.

The OWASP Project Lifecycle is broken down into the following stages:

Incubator Projects: OWASP Incubator projects represent the experimental playground where projects are still being designed, ideas are still being proven, and development is still underway. The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity; moreover, the label allows project leaders to leverage the OWASP name while their project is still maturing. OWASP Incubator projects are given a place on the OWASP Projects Portal to leverage the organizations' infrastructure, and establish their presence and project history.

Labs Projects: OWASP Labs projects represent projects that have produced a deliverable of significant value. Leaders of OWASP Labs projects are expected to stand behind the quality of their projects as these projects have matured to the point where they are accepted by a significant portion of the OWASP community. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are ready for mainstream usage. OWASP Labs Projects are meant to be the collection of established projects that have gained community support and acclaim by undergoing the project review process.

Flagship Projects: The OWASP Flagship designation is given to projects that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole. Eligible projects are selected from the OWASP Labs project pool. This selection process generally ensures that there is only one project of each type covering any particular security space. OWASP Flagship projects represent projects that are not only mature, but are also projects that OWASP as an organization provides direct support to maintaining. The core mission of OWASP is to make application security visible and so as an organization, OWASP has a vested interest in the success of its Flagship projects. Since Flagship projects have such high visibility, these projects are expected to uphold the most stringent requirements of all OWASP Projects.

OWASP Project Stage Benefits
This section outlines the benefits of starting an OWASP project, and the benefits of being at each different stage in the projects lifecycle. In my short time here at OWASP as the PM, I have had several potential project leaders ask me what the benefits are of starting their project with OWASP. Below is my proposal for each Stage’s benefits.

Incubator
 * Financial Donation Management Assistance
 * Project Review Support
 * WASPY Awards Nominations
 * OWASP OSS and OPT Participation
 * Opportunity to submit proposal: $500 for Development.
 * Community Engagement and Support
 * Recognition and visibility of being associated with the OWASP Brand.

Labs
 * All benefits given to Incubator Projects
 * Technical Writing Support
 * Graphic Design Support
 * Project Promotion Support
 * OWASP OSS and OPT: Preference

Flagship
 * All benefits given to Incubator & Labs Projects
 * Grant finding and proposal writing help
 * Yearly marketing plan development
 * OWASP OSS and OPT participation preference

For more detailed information on OWASP Project Stage Benefits, please see the 2013 Project Handbook.

OWASP Project Graduation
The Project Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs. In order to be considered for OWASP Labs, an Incubator project must have submitted an OWASP reviewed deliverable, and obtained at least two (2) positive responses for each of the core criteria project health questions.

The review centers around the following core questions. Each core question has three (3) specific questions made up of binary queries. A project must receive at least two (2) positive responses from each reviewer in two of the binary questions, to warrant a postive response for the core question. Each core question must receive a positive response from both project reviewers to pass the Project Health Assessment for Incubator Projects.


 * Project Graduation Criteria Checklist

OWASP Project Health Assessment
The Project Health Assessment is an optional process undertaken at the request of a project leader when he/she applies for Project Graduation The purpose of this assessment is to determine whether a project meets the minimum criteria of an OWASP Project outlined in the Project Health Assessment Criteria Document. If a project passes the assessment, it then becomes eligible to graduate into the OWASP Labs Project stage. In order to be considered for OWASP Labs, an Incubator project must have submitted an OWASP reviewed deliverable, and obtained at least two (2) positive responses for each of the core criteria project health questions.

OWASP Project Deliverable/Release Assessment
The Project Deliverable/Release Review is an optional process undertaken at the request of a project leader using the Project Deliverable Review Form. The purpose of this process is to review a project’s progress, and to make sure the project is heading in the right direction based on the roadmap they provided at project inception.

Reviews must be performed by two (2) OWASP Chapter or Project Leaders, and their review must answer affirmatively to at least the first two (2) core Project Deliverable/Release Review questions. A project must pass the OWASP Project Deliverable/Release Assessment in order to graduate into the OWASP Labs Project stage.


 * Project Deliverable/Release Assessment Criteria Checklist

= Project Inventory =

Flagship Projects
The OWASP Flagship designation is given to projects that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole. OWASP Flagship projects represent projects that are not only mature, but are also projects that OWASP as an organization provides direct support to maintaining.

Code
 * OWASP AntiSamy Project
 * OWASP Enterprise Security API
 * OWASP ModSecurity Core Rule Set Project
 * OWASP CSRFGuard Project

Tools
 * OWASP Web Testing Environment Project
 * OWASP WebGoat Project
 * OWASP Zed Attack Proxy

Documentation
 * OWASP Application Security Verification Standard Project
 * OWASP Code Review Guide Project
 * OWASP Codes of Conduct
 * OWASP Development Guide Project
 * OWASP Secure Coding Practices - Quick Reference Guide
 * OWASP Software Assurance Maturity Model (SAMM)
 * OWASP Testing Guide Project
 * OWASP Top Ten Project

Labs Projects
OWASP Labs projects represent projects that have produced a deliverable of value. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are at least ready for mainstream usage.

Tools
 * OWASP Broken Web Applications Project
 * OWASP CSRFTester Project
 * OWASP EnDe Project
 * OWASP Hackademic Challenges Project
 * OWASP HTTP POST Tool
 * OWASP Java XML Templates Project
 * OWASP Mantra Security Framework
 * OWASP Mutillidae Project
 * OWASP O2 Platform
 * OWASP Vicnum Project
 * OWASP Wapiti Project
 * OWASP Yasca Project

Documentation
 * OWASP AppSec Tutorial Series
 * OWASP AppSensor Project
 * OWASP CTF Project
 * OWASP Legal Project
 * OWASP Podcast Project
 * Virtual Patching Best Practices

Incubator Projects
OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway. The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity. The label also allows project leaders to leverage the OWASP name while their project is still maturing.

Code
 * OWASP OPA
 * OWASP Java Encoder Project
 * OWASP Passfault
 * OWASP OctoMS
 * OWASP AW00t
 * OWASP JSON Sanitizer
 * OWASP Security Research and Development Framework
 * OWASP 1-Liner
 * OWASP Focus
 * OWASP PHPRBAC Project
 * OWASP EJSF Project
 * OWASP Barbarus
 * OWASP iMAS - iOS Mobile Application Security Project
 * OWASP RBAC Project
 * OWASP PHP Security Project
 * OWASP Simple Host Base Incidence Detection System Project
 * OWASP File Format Validation Project
 * OWASP JAWS Project
 * OWASP Node.js Goat Project
 * OWASP System Vulnerable Code Project
 * OWASP ISO/IEC 27034 Application Security Controls Project

Tools
 * OWASP WhatTheFuzz Project
 * OWASP Security Tools for Developers Project
 * OWASP OVAL Content Project
 * OWASP NAXSI Project
 * OWASP Passw3rd Project
 * OWASP File Hash Repository
 * OWASP WebGoat.NET
 * OWASP OWTF
 * OWASP Path Traverser
 * OWASP Watiqay
 * OWASP Security Shepherd
 * OWASP Xenotix XSS Exploit Framework
 * OWASP Mantra OS
 * OWASP XSSER
 * OWASP Academy Portal Project
 * OWASP ASIDE Project
 * OWASP iGoat Project
 * OWASP Proxy Project
 * OWASP SamuraiWTF
 * O-Saft
 * OWASP Crowdtesting
 * OWASP OpenStack Security Project
 * OWASP Desktop Goat and Top 5 Project
 * OWASP Bricks
 * OWASP Dependency Check
 * OWASP Hive Project
 * OWASP Droid Fusion
 * OWASP iSABEL Proxy Server
 * OWASP Rails Goat Project
 * OWASP Bywaf Project
 * OWASP S.T.I.N.G Project
 * OWASP Application Fuzzing Framework Project
 * OWASP VaultDB Project
 * OWASP WS-Amplification DoS Project
 * OWASP Mutillidae 2 Project
 * OWASP Skanda - SSRF Exploitation Framework
 * OWASP SeraphimDroid Project
 * OWASP Unmaskme Project
 * OWASP Androïck Project
 * OWASP SafeNuGet Project
 * OWASP WebSandBox Project
 * OWASP HA Vulnerability Scanner Project
 * OWASP Dependency Track Project
 * OWASP PHP Portscaner Project
 * OWASP Java HTML Sanitizer Project
 * OWASP Pygoat Project
 * OWASP Python Security Project
 * OWASP Web Knocking Project
 * OWASP Financial Information Exchange Security Project
 * OWASP STeBB Project
 * OWASP NINJA PingU Project

Documentation
 * OWASP Data Exchange Format Project
 * OWASP Cheat Sheets Project
 * OWASP Proactive Controls
 * OWASP Java/J2EE Secure Development Curriculum
 * OWASP Security Baseline Project
 * OWASP Software Security Assurance Process
 * OWASP Web Application Security Accessibility Project
 * OWASP Application Security Requirements Project
 * OWASP Common Numbering Project
 * OWASP Application Security Assessment Standards Project
 * OWASP Application Security Skills Assessment
 * OWASP Computer Based Training Project (OWASP CBT Project)
 * OWASP Enterprise Application Security Project
 * OWASP Exams Project
 * OWASP GoatDroid Project
 * OWASP Request For Proposal
 * OWASP University Challenge
 * OWASP Hacking-Lab
 * OWASP Application Security Awareness Top 10 E-learning Project
 * OWASP Periodic Table of Vulnerabilities
 * WASC/OWASP Web Application Firewall Evaluation Criteria (WAFEC)
 * OWASP ESAPI Swingset Project
 * OWASP Press
 * OWASP CISO Survey
 * OWASP Application Security Guide For CISOs
 * OWASP Scada Security Project
 * OWASP Cornucopia
 * OWASP Secure Application Design Project
 * OWASP Top 10 Fuer Entwickler Project
 * OWASP Good Component Practices Project
 * OWASP Web Application Security Quick Reference Guide Project
 * OWASP Windows Binary Executable Files Security Checks Project
 * OWASP Wordpress Security Checklist Project
 * OWASP Supporting Legacy Web Applications in the Current Environment Project
 * OWASP Security Principles Project
 * OWASP Ruby on Rails and friends Security Guide Project
 * OWASP Framework Security Project
 * OWASP Media Project
 * OWASP Global Chapter Meetings Project
 * OWASP This I Believe Security Project
 * OWASP Vulnerable Web Applications Directory Project
 * OWASP Game Security Framework Project
 * OWASP Security Labeling System Project
 * OWASP IoTs Project
 * OWASP Insecure Web Components Project
 * OWASP Reverse Engineering and Code Modification Prevention Project
 * OWASP Student Chapters Project
 * OWASP Education Project

Donated Projects
OWASP Donated Projects are inactive projects that have been donated to the OWASP Projects Infrastructure.

Tools


 * OWASP Excess XSS Project

Inactive Projects
Archived Projects

OWASP Archived Projects are inactive Labs projects. If you are interested in pursuing any of the projects below, please contact us and let us know of your interest.


 * OWASP Access Control Rules Tester Project
 * OWASP Application Security Metrics Project
 * OWASP AppSec FAQ Project
 * OWASP ASDR Project
 * OWASP Backend Security Project
 * OWASP Best Practices: Use of Web Application Firewalls
 * OWASP CAL9000 Project
 * OWASP CLASP Project
 * OWASP CodeCrawler Project
 * OWASP Content Validation using Java Annotations Project
 * OWASP DirBuster Project
 * OWASP Encoding Project
 * OWASP Google Hacking Project
 * OWASP Insecure Web App Project
 * OWASP Interceptor Project
 * OWASP JSP Testing Tool Project
 * OWASP LiveCD Education Project
 * OWASP Logging Guide
 * OWASP NetBouncer Project
 * OWASP OpenPGP Extensions for HTTP - Enigform and mod_openpgp Project
 * OWASP OpenSign Server Project
 * OWASP Pantera Web Assessment Studio Project
 * OWASP PHP Project
 * OWASP Report Generator
 * OWASP Scholastic Application Security Assessment Project
 * OWASP Security Analysis of Core J2EE Design Patterns Project
 * OWASP Security Spending Benchmarks Project
 * OWASP Site Generator Project
 * OWASP Skavenger Project
 * OWASP Source Code Flaws Top 10 Project
 * OWASP Sprajax Project
 * OWASP Sqlibench Project
 * OWASP sqliX Project
 * OWASP Stinger Project
 * OWASP Teachable Static Analysis Workbench Project
 * OWASP Tiger
 * OWASP Tools Project
 * OWASP Uniform Reporting Guidelines
 * OWASP Webekci Project
 * JBroFuzz
 * OWASP SWAAT Project
 * OWASP Secure Web Application Framework Manifesto
 * OWASP Orizon Project
 * OWASP Scrubbr
 * OWASP JavaScript Sandboxes Project
 * OWASP Joomla Vulnerability Scanner Project
 * OWASP LAPSE Project
 * OWASP Hatkit Datafiddler Project
 * OWASP Hatkit Proxy Project
 * OWASP Fiddler Addons for Security Testing Project
 * OWASP Forward Exploit Tool Project
 * OWASP Fuzzing Code Database
 * OWASP Cloud ‐ 10 Project
 * OWASP Web Browser Testing System Project
 * OWASP WebScarab Project
 * OWASP Webslayer Project
 * OWASP WSFuzzer Project
 * OWASP Security Assurance Testing of Virtual Worlds Project
 * OWASP WAF Project
 * OWASP VFW Project
 * OWASP SIMBA Project
 * OWASP ONYX
 * OWASP Java Uncertain Form Submit Prevention
 * OWASP Ecuador
 * OWASP ESOP Framework
 * OWASP Alchemist Project
 * OWASP Secure the Flag Project
 * OWASP Browser Security ACID Test Project
 * OWASP AJAX Crawling Tool
 * OWASP Threat Modeling Project
 * OWASP Crossword of the Month
 * OWASP Secure Password Project
 * OWASP Myth Breakers Project
 * OWASP Project Partnership Model
 * OWASP Browser Security Project
 * OWASP Application Security Program for Managers
 * OWASP Favicon Database Project
 * OWASP Embedded Application Security
 * OWASP Security JDIs Project

= Brand Resources =

The Brand Usage Rules
OWASP's philosophy is that achieving security involves all parts of an organization, including people, process, and technology. We support the use of our brand consistent with this philosophy. However, we cannot allow the use of our brand when it implies something inconsistent with OWASP's comprehensive and balanced approach to application security. Therefore, we have defined these brand usage rules to clarify appropriate and inappropriate uses of the OWASP brand, including our name, domain, logos, project names, and other trademarks.

The Brand Guideline documents and rules below provide details and instruction on how to use the OWASP logo and brand. The quick reference sheet goes over the basics of the OWASP brand logo and a brief overview of customizable options. The Brand Guidelines document gives the entire description of the OWASP brand, its public use, and the options to customize the logo based on personal desire. The guidelines cover the OWASP signature, size and spacing, colors, imagery, and typefaces.

Rules
The following rules make reference to the OWASP Materials, meaning any tools, documentation, or other content from OWASP. The rules also make reference to "OWASP Published Standards" which are currently in the process of being developed and released. Currently there are no OWASP Published Standards.


 * 1) The OWASP Brand may be used to direct people to the OWASP website for information about application security.
 * 2) The OWASP Brand may be used in commentary about the materials found on the OWASP website.
 * 3) The OWASP Brand may be used by OWASP Members in good standing to promote a person or company's involvement in OWASP.
 * 4) The OWASP Brand may be used in association with an application security assessment only if a complete and detailed methodology, sufficient to reproduce the results, is disclosed.
 * 5) The OWASP Brand must not be used in a manner that suggests that The OWASP Foundation supports, advocates, or recommends any particular product or technology.
 * 6) The OWASP Brand must not be used in a manner that suggests that a product or technology is compliant with any OWASP Materials other than an OWASP Published Standard.
 * 7) The OWASP Brand must not be used in a manner that suggests that a product or technology can enable compliance with any OWASP Materials other than an OWASP Published Standard.
 * 8) The OWASP Brand must not be used in any materials that could mislead readers by narrowly interpreting a broad application security category. For example, a vendor product that can find or protect against forced browsing must not claim that they address all of the access control category.
 * 9) The OWASP Brand may be used by special arrangement with The OWASP Foundation.

Project Icons & Templates
The templates and icons below are the files used for our OWASP Projects. Here you will find icons that you can place on your wiki template to let viewers know what type of project they are looking at, and what stage the project is in. The operational OWASP Project wiki template can be copied onto another project page. If you require more assistance with these files and/or templates, please contact the OWASP staff for assistance

OWASP Operational Wiki Template

OWASP Example Template: DO NOT EDIT









Book Cover Files
Lulu Guide

Below you will find the Adobe Illustrator, Photoshop, and In-Design files for past OWASP Documentation books. You will need a copy of Adobe Creative Suite to edit these files. If you want to use these templates, but do not have Adobe Creative Suite, please contact the OWASP staff for assistance.

Download the Book Cover Zip File

= Terminology =

OWASP Project Infrastructure

 * OWASP Project Lifecycle: The OWASP Projects Lifecycle represents a balance between keeping a very loose structure around OWASP projects, and ensuring that OWASP consumers are not confused about a project’s maturity and quality. The lifecycle stage allows consumers to easily identify mature projects, and projects that are proofs of concept, experimental, and classified as prototypes in their current state.


 * Incubator Project: OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway. The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity. The label also allows project leaders to leverage the OWASP name while their project is still maturing.


 * Labs Project: OWASP Labs projects represent projects that have produced a deliverable of value. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are at least ready for mainstream usage.


 * Flagship Project: The OWASP Flagship designation is given to projects that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole. OWASP Flagship projects represent projects that are not only mature, but are also projects that OWASP as an organization provides direct support to maintaining.


 * Project Benefits: The standard list of resources and incentives made available to project leaders based on their project's current maturity level.

OWASP Project Reviews

 * Project Reviews: Project reviews are the method OWASP uses to establish a minimal baseline of project characteristics and release quality. Reviews are not mandatory, but they are necessary if a project leader wishes to graduate to the next level of maturity within the OWASP Global Projects infrastructure. Projects can be reviewed when an Incubator project wishes to graduate into the OWASP Labs designation, and project releases can be reviewed if they want the quality of their deliverable to be vouched for by OWASP.


 * Project Reviewer Pool: The project reviewer pool is made up of veteran reviewers who have proven themselves dedicated to executing quality reviews of projects.


 * Project Graduation: The Project Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs.


 * Project Health Assessment: The Project Health Assessment is an optional process undertaken at the request of a project leader when he/she applies for Project Graduation The purpose of this assessment is to determine whether a project meets the minimum criteria of an OWASP Project outlined in the Project Health Assessment Criteria Document.


 * Project Release: A project release refers to the final deliverable a project produces. It is the final product of the project.


 * Project Deliverable/Release Review: The Project Deliverable/Release Review is an optional process undertaken at the request of a project leader using the Project Deliverable Review Form. The purpose of this process is to review a project’s progress, and to make sure the project is heading in the right direction based on the roadmap they provided at project inception.

OWASP Projects Processes

 * Project Processes: The set of streamlined processes that exist to help projects move smoothly through the OWASP Project Lifecycle.


 * Project Inception Process: The Project Inception Process is how a brand new idea becomes an OWASP Project. Such projects are labeled as OWASP Incubator projects. The process involves submitting the proposed project name, project leader information, project description, project roadmap, and selecting an appropriate open-source license for the project using the New Project Form on the Projects Portal.


 * Project Donation Process: The Project Donation Process is used for a project that has an existing functional release, but is not currently associated with OWASP. This process is the primary mechanism by which individuals or organizations can transfer the ownership of their project’s copyright to OWASP.


 * Project Transition Process: The Project Transition Process is used to transition leadership of a project to a new project leader. This is a simple automated process to transfer the relevant accounts, mailing lists, and other project resources to the new project leader.


 * Project Abandonment Process: The Project Abandonment Process was put in place for those occasions in which a project leader is no longer able to manage their project, and has not been able to find a suitable replacement for the leader role. Project Abandonment can also occur when the project leader feels his/her project has become obsolete. Under these circumstances, the acting project leader is encourage do submit the Project Abandonment Form found in the Projects Portal.


 * Incubator Graduation Process: The Incubator Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs.

Projects at Conferences

 * AppSec Conferences: OWASP AppSec conferences bring together industry, government, security researchers, and practitioners to discuss the state of the art in application security. This series was launched in the United States in 2004 and Europe in 2005. Global AppSec conferences are held annually in North America, Latin America, Europe, and Asia Pacific.


 * Open Source Showcase: The Open Source Showcase is an OWASP AppSec Conference event module designed to give Open Source project leaders the opportunity to demo their projects.


 * OWASP Project Track: The OWASP Project Track is an OWASP AppSec Conference event module designed to give OWASP Project leaders the opportunity to showcase their projects as an official conference presenter.

OWASP Projects General

 * OWASP Code of Ethics: The OWASP Code of Ethics are the set of guidelines and principles that the OWASP Foundation expects all of its members and conference attendees to abide by. A copy of the Code of Ethics can be found here in the OWASP About page.

= Sponsorships and Donations =

Donate to OWASP Global Projects
OWASP Projects, a global division of the OWASP Foundation, is run under the same world wide not-for-profit charitable status as all the foundation strategic groups. OWASP provides a platform for contributors to share their work while providing them with the project and community support they need throughout their project development. All OWASP Projects are run by volunteers and they rely on personal donations and sponsorship to continue their development. Donate to OWASP Projects, and we promise to spend your money wisely on open source initiatives.

This is how your money can help:


 * $20 could help us spread the word on the importance of open source initiatives in the Application Security industry.
 * $100 could help fund OWASP project demos at major conferences.
 * $250 could help get our volunteer Project Leaders to speaking engagements.



= PM Information =

Projects Reports
2014


 * Project Manager Report: January 10 2014
 * Project Manager Report: January 17 2014

2013


 * GPC Meeting: January 04 2013 Project Manager Report
 * GPC Meeting: January 11 2013 Project Manager Report
 * GPC Meeting: January 18 2013 Project Manager Report
 * GPC Meeting: January 25 2013 Project Manager Report
 * GPC Meeting: February 01 2013 Project Manager Report
 * GPC Meeting: February 08 2013 Project Manager Report
 * GPC Meeting: February 15 2013 Project Manager Report
 * GPC Meeting: February 22 2013 Project Manager Report
 * Project Manager Report: March 01 2013
 * Project Manager Report: March 08 2013
 * Project Manager Report: March 15 2013
 * Project Manager Report: March 22 2013
 * Project Manager Report: March 29 2013
 * Project Manager Report: April 05 2013
 * Project Manager Report: April 12 2013
 * Project Manager Report: April 19 2013
 * Project Manager Report: April 26 2013
 * Project Manager Report: May 03 2013
 * Project Manager Report: May 10 2013
 * Project Manager Report: May 17 2013
 * Project Manager Report: May 24 2013
 * Project Manager Report: May 31 2013
 * Project Manager Report: June 07 2013
 * Project Manager Report: June 14 2013
 * Project Manager Report: June 21 2013 - No Report this week. PM was away at a week long course.
 * Project Manager Report: June 28 2013
 * Project Manager Report: July 05 2013
 * Project Manager Report: July 12 2013
 * Project Manager Report: July 19 2013
 * Project Manager Report: July 26 2013
 * Project Manager Report: August 02 2013 - No Report this week. PM was away at Black Hat & DEFCON 2013.
 * Project Manager Report: August 09 2013
 * Project Manager Report: August 16 2013
 * Project Manager Report: August 23 2013
 * Project Manager Report: August 30 2013
 * Project Manager Report: September 06 2013 - No Report this week. PM was away.
 * Project Manager Report: September 13 2013
 * Project Manager Report: September 20 2013
 * Project Manager Report: September 27 2013
 * Project Manager Report: October 04 2013
 * Project Manager Report: October 12 2013
 * Project Manager Report: October 18 2013
 * Project Manager Report: October 25 2013
 * Project Manager Report: November 01 2013
 * Project Manager Report: November 08 2013
 * Project Manager Report: November 15 2013
 * Project Manager Report: November 22 2013 - No Report this week. PM was away at AppSec USA 2013.
 * Project Manager Report: November 29 2013 - No Report this week. National Holiday.
 * Project Manager Report: December 06 2013
 * Project Manager Report: December 13 2013
 * Project Manager Report: December 20 2013

2012


 * GPC Meeting: August 24 2012 Project Manager Report
 * GPC Meeting: September 07 2012 Project Manager Report
 * GPC Meeting: September 14 2012 Project Manager Report
 * GPC Meeting: September 21 2012 Project Manager Report
 * GPC Meeting: September 28 2012 Project Manager Report
 * GPC Meeting: October 05 2012 Project Manager Report
 * GPC Meeting: October 12 2012 Project Manager Report
 * GPC Meeting: October 19 2012 Project Manager Report
 * GPC Meeting: November 09 2012 Project Manager Report
 * GPC Meeting: November 16 2012 Project Manager Report
 * GPC Meeting: November 30 2012 Project Manager Report
 * GPC Meeting: December 07 2012 Project Manager Report
 * GPC Meeting: December 14 2012 Project Manager Report
 * GPC Meeting: December 21 2012 Project Manager Report
 * GPC Meeting: December 27 2012 Project Manager Report

Board Meeting Reports

 * Board Meeting: August 2012 Project Manager Report
 * Board Meeting: September 2012 Project Manager Report
 * Board Meeting: October 2012 Project Manager Report
 * Board Meeting: November 2012 Project Manager Report
 * Board Meeting: December 2012 Project Manager Report
 * Board Meeting: January 2013 Project Manager Report
 * Board Meeting: February 2013 Project Manager Report
 * Board Meeting: March 2013 Project Manager Report
 * Board Meeting: April 2013 Project Manager Report
 * Board Meeting: May 2013 Project Manager Report
 * Board Meeting: June 2013 Project Manager Report
 * Board Meeting: July 2013 Project Manager Report
 * Board Meeting: August 2013 Project Manager Report
 * Board Meeting: September 2013 Project Manager Report
 * Board Meeting: November 2013 Project Manager Report
 * Board Meeting: December 2013 Project Manager Report

Project Funds

 * Chapter and Individual Project Funds
 * Project Reboot 2012 Information
 * Q1 2013: Funds Allocated to Projects
 * Q2 2013: Funds Allocated to Projects
 * Q3 2013: Funds Allocated to Projects
 * Q4 2013: Funds Allocated to Projects

Project Grants: Proposals Awarded

 * OWASP Guidebooks Proposal
 * 1) Amount: $25,000 USD
 * 2) Status: Awarded. The first payment has been allocated to our project budgets. The second invoice has now been sent to Georgia Tech and payment has been received.
 * 3) OWASP Development Guide Plan
 * 4) OWASP Testing Guide Plan
 * 5) OWASP Code Review Guide Plan


 * Google Grants Proposal
 * 1) Amount: $120,000 USD in Adwords Funds
 * 2) Status: Awarded.
 * 3) Note: There is no link to show the proposal for this grant. There was a form that was submitted to Google, and we did not receive a record of this form.


 * Google Summer of Code
 * 1) Amount: $5,500
 * 2) Status: Awarded


 * Projects breakdown:
 * 4 ZAP Projects: $2,000
 * 4 OWTF Projects: $2,000
 * 1 PHP Security Project: $500
 * 1 Hackademics Project: $500
 * 1 Modsecurity Project: $500
 * Note: Big thank you to Fabio Cerullo for coordinating and managing this award.


 * OWASP AppSensor Grant Proposal
 * 1) Amount: ￼$15,000 USD
 * 2) Status: Awarded.


 * Total Funds Awarded: $172,170 USD for 2013.

Proposals Denied

 * European Commission Grant Proposal
 * 1) Amount: €250,000
 * 2) Status: Denied.


 * OWASP OpenSAMM Grant Proposal
 * 1) Amount: $112,000 USD
 * 2) Status: Denied


 * OWASP ESAPI Grant Proposal
 * 1) Amount: $25,000 USD
 * 2) Status: Denied


 * OWASP ModSecurity CRS Proposal
 * 1) Amount: $30,000 USD
 * 2) Status: Denied


 * OWASP OWTF Grant Proposal
 * 1) Amount: $55,800 USD
 * 2) Status: Denied

Project Presentations

 * OWASP Projects Presentation: Phoenix Chapter Talk
 * OWASP Projects Webinar
 * OWASP Project Infrastructure: Solutions

Projects Manger's Quarterly Strategic Objectives
Goals and Objectives: 2013 Q4
 * 1) Finish planning Project Summit & Execute Summit at AppSec USA.
 * 2) Develop & Finish Global Projects Strategy for 2014: Includes Budget
 * 3) Finish Fundraising Strategy for 2014: Includes Budget


 * Ongoing Objectives for 2013
 * Quarterly Report to DHS
 * Continue helping leaders reach their grant required milestones
 * Finalise graphic design delivery from Patrick: 2 pieces to go.

Goals and Objectives: 2013 Q3
 * 1) Marketing: Work with Sarah to solicit feedback from community on Marketing deliverables and finalize relationship with Patrick and Denita.
 * 2) Project Review Process - Work with new Technical Project advisors to finalize project review criteria and process.
 * 3) Grants: Develop a grant strategy for rest of 2013 and 2014, utilizing fundraising intern(s) as part of this strategy.


 * Ongoing Objectives for 2013
 * Work with Project leaders to reach grant required milestones - ONGOING
 * Develop a project charter outlining appropriate grant revenue spending and grant required milestones. - DUE IN SEPTEMBER - ONGOING
 * Oversight of Marketing and Graphic Design deliverables (Phase 2/Phase 3) provided by 3rd party contractor

Contact the Projects Manager
If you need any help with anything projects related, or if you simply need some more information, please do not hesitate to contact the OWASP Projects Manager, Samantha Groves.

= Contact US =

OWASP Representation

 * Samantha Groves: OWASP Projects Manager

If you need any help with anything projects related, or if you simply need some more information, please do not hesitate to contact the OWASP Projects Manager, Samantha Groves.