Difference between revisions of "Category:OWASP Project"
|Line 122:||Line 122:|
* [https://www.owasp.org/index.php/OWASP_Hackademic_Challenges_Project OWASP Hackademic Challenges Project]
* [https://www.owasp.org/index.php/OWASP_Hackademic_Challenges_Project OWASP Hackademic Challenges Project]
* [https://www.owasp.org/index.php/OWASP_Mantra_-_Security_Framework OWASP Mantra Security Framework]
* [https://www.owasp.org/index.php/OWASP_Mantra_-_Security_Framework OWASP Mantra Security Framework]
* [https://www.owasp.org/index.php/OWASP_O2_Platform OWASP O2 Platform]
* [https://www.owasp.org/index.php/OWASP_O2_Platform OWASP O2 Platform]
* [https://www.owasp.org/index.php/Project_Information:template_Vicnum_Project OWASP Vicnum Project]
* [https://www.owasp.org/index.php/Project_Information:template_Vicnum_Project OWASP Vicnum Project]
Revision as of 13:08, 14 July 2014
- Project Inventory
- Project Task Force
- Online Resources
- Starting a New Project
- Project Assessments
- Brand Resources
- Sponsorships and Donations
- Contact US
The OWASP Flagship designation is given to projects that have demonstrated strategic value to OWASP and application security as a whole. Projects are being evaluated to determine the level of maturity, an update regarding the status flagship projects will be announce by mid August 2014.
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.
- OWASP Broken Web Applications Project
- OWASP CSRFTester Project
- OWASP EnDe Project
- OWASP Hackademic Challenges Project
- OWASP Mantra Security Framework
- OWASP O2 Platform
- OWASP Vicnum Project
- OWASP Wapiti Project
- OWASP Yasca Project
- OWASP OWTF
- OWASP Web Testing Environment Project
- OWASP WebGoat Project
- OWASP Zed Attack Proxy
- OWASP AppSec Tutorial Series
- OWASP AppSensor Project
- OWASP CTF Project
- OWASP Legal Project
- OWASP Podcast Project
- Virtual Patching Best Practices
- 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
- OWASP AntiSamy Project
- OWASP Enterprise Security API
- OWASP ModSecurity Core Rule Set Project
- OWASP CSRFGuard 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.
- OWASP OPA
- OWASP Java Encoder Project
- OWASP JSON Sanitizer
- OWASP Passfault
- OWASP Java File I/O Security Project
- OWASP Security Research and Development Framework
- OWASP Focus
- OWASP PHPRBAC Project
- OWASP EJSF Project
- OWASP iMAS - iOS Mobile Application Security Project
- OWASP RBAC Project
- OWASP PHP Security 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
- OWASP Secure Headers Project
- OWASP Hardened Phalcon Project
- OWASP Barbarus
- OWASP Faux Bank Project
- OWASP Java HTML Sanitizer Project
- OWASP Java XML Templates Project
- OWASP NAXSI Project
- OWASP Passw3rd Project
- OWASP WebGoat.NET
- 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 SamuraiWTF
- OWASP OpenStack Security Project
- OWASP Bricks
- OWASP Dependency Check
- OWASP Hive Project
- OWASP Rails Goat Project
- OWASP Bywaf Project
- OWASP S.T.I.N.G Project
- OWASP Mutillidae 2 Project
- OWASP Skanda - SSRF Exploitation Framework
- OWASP SeraphimDroid Project
- OWASP Androïck Project
- OWASP SafeNuGet Project
- OWASP WebSandBox Project
- OWASP Dependency Track Project
- OWASP PHP Portscaner Project
- OWASP Python Security Project
- OWASP WebSpa Project
- OWASP Financial Information Exchange Security Project
- OWASP NINJA PingU Project
- OWASP Encoder Comparison Reference Project
- OWASP sqliX Project
- OWASP LAPSE Project
- OWASP Orizon Project
- OWASP WASC Distributed Web Honeypots Project
- OWASP Click Me Project
- OWASP Secure TDD Project
- OWASP XSecurity Project
- OWASP Pyttacker Project
- OWASP Code Pulse Project
- OWASP HTTP POST Tool
- OWASP PHP Security Training Project
- OWASP iOSForensic
- OWASP Project Metrics
- OWASP Store Sheep Project
- OWASP SonarQube Project
- OWASP URL Checker
- OWASP Data Exchange Format Project
- OWASP Cheat Sheets Project
- OWASP Proactive Controls
- OWASP Security Baseline Project
- OWASP Application Security Requirements Project
- OWASP Application Security Assessment Standards Project
- 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
- WASC/OWASP Web Application Firewall Evaluation Criteria (WAFEC)
- 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 Web Application Security Quick Reference Guide Project
- OWASP Supporting Legacy Web Applications in the Current Environment Project
- OWASP Security Principles Project
- OWASP Media Project
- OWASP Global Chapter Meetings Project
- OWASP Vulnerable Web Applications Directory Project
- OWASP Game Security Framework Project
- OWASP Insecure Web Components Project
- OWASP Reverse Engineering and Code Modification Prevention Project
- OWASP Student Chapters Project
- OWASP Education Project
- OWASP Speakers Project
- OWASP Internet of Things Top Ten Project
- OWASP .NET Project
- OWASP Research Book Project
- OWASP Open Cyber Security Framework Project
- OWASP Top 10 Privacy Risks Project
- OWASP WASC Web Hacking Incidents Database Project
- OWASP Security Frameworks Project
- OWASP Incident Response Project
- OWASP Embedded Application Security
- OWASP STING Game Project
- OWASP Ruby on Rails and Friends Security Guide
- OWASP Secure Development Training
- OWASP Periodic Table of Vulnerabilities
- OWASP Top Trumps for Projects
OWASP Donated Projects are inactive projects that have been donated to the OWASP Projects Infrastructure.
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 Stinger Project
- OWASP Teachable Static Analysis Workbench Project
- OWASP Tiger
- OWASP Tools Project
- OWASP Uniform Reporting Guidelines
- OWASP Webekci Project
- OWASP SWAAT Project
- OWASP Secure Web Application Framework Manifesto
- OWASP Scrubbr
- OWASP Joomla Vulnerability Scanner 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 Security JDIs Project
- OWASP File Hash Repository
- OWASP Crowdtesting
- OWASP Application Security Skills Assessment
- OWASP Common Numbering Project
- OWASP WhatTheFuzz Project
- OWASP Security Tools for Developers Project
- OWASP Proxy Project
- OWASP AW00t
- OWASP Framework Security Project
- OWASP Desktop Goat and Top 5 Project
- OWASP OVAL Content Project
- OWASP Software Security Assurance Process
- OWASP Application Fuzzing Framework Project
- OWASP Good Component Practices Project
- OWASP 1-Liner
- OWASP Java Project
- OWASP Web Application Security Accessibility Project
- OWASP OctoMS
- OWASP Java/J2EE Secure Development Curriculum
- OWASP Droid Fusion
- OWASP iSABEL Proxy Server
- OWASP WS-Amplification DoS Project
- OWASP Windows Binary Executable Files Security Checks Project
- OWASP Wordpress Security Checklist Project
- OWASP Simple Host Base Incidence Detection System Project
- OWASP Unmaskme Project
- OWASP HA Vulnerability Scanner Project
- OWASP Pygoat Project
- OWASP Security Labeling System Project
- OWASP IoTs Project
- OWASP STeBB Project
- OWASP Ultimatum Project
- OWASP ESAPI Swingset Project
- OWASP VaultDB Project
OWASP Project Task Force
This task force is focused on OWASP Projects with a first focus on cleaning up the OWASP incubator list
Current To-do list
Tracking of current stuff is done temporary here as we plan to use Jira in the long run.
- Clean up of Incubator Projects and inactivate projects without a release or updates for over a year.
- Inactive/Active Project Audits:https://groups.google.com/a/owasp.org/forum/?hl=en#!forum/projects-task-force (must be OWASP member)
- Project Reviews: See here for more details
- [Task: Project Metrics Collection Project Metrics Collection: Data needed]
- Plan next EU Project Summit 2015 Amsterdam
- AppSecUSA 2014 Projects Summit Rescue
- USA Summit 2014 is happening wiki page here
- LAB Projects Code Analysis Report
- The Proposal Evaluation Methodology for OWASP Projects - Johanna has put together a proposal for evaluating project. The proposal can be found here: Proposal Evaluation.
- Create a coherent wiki page for the Project Dashboard.
To-do list: Future Tasks
- Gather support and funding to have 1 large OWASP Summit.
- Design a more sustainable revenue stream using the Project’s IP.
- Identify & promote cross-project collaboration to move clusters of projects forward, with e.g. work groups that work on a certain domain.
- Start a task force of people with spare cycles that can help projects that need extra man-power of are falling behind in delivery of new releases (especially the flag ship projects).
- create a new mailing list (in google groups) for this task force: https://groups.google.com/a/owasp.org/forum/?hl=en#!forum/projects-task-force
- Submissions for Open Source Showcase at AppSec EU: See here for more details: Completed by Team. - May 02, 2014
- Need to review Java HTML Sanitizer Project: See here for more details: Removed from the Review List - Samantha - May 02, 2014
- Wikify Projects Dashboard: Removed as agreed it is unnecessary - Samantha - May 02, 2014
- Move the Google Groups to OWASP Google App - Jonathan - July 16, 2014
- Inactivated all Incubator Documentation projects with no release in over a year and no updates. - August 2, 2014.
- Need to get all project repos added to https://www.openhub.net/orgs/OWASP: DONE- 88 projects have an open repository
- Created the Project Dashboard. Look for link once the wiki page has been created.
This task force exists on the assumption that it has a mandate from the OWASP leaders to act on behalf of the OWASP community on what is best for OWASP Projects. We are in the process of submitting a Committee Proposal for Project reviews
If somebody (namely an OWASP Leader or Board member) disagree with any of the decisions made, he/she has two options:
- join this Task Force/Committe
- create another equivalent 'OWASP Projects group' and do a better job there
note that Committee 2.0 will change this as this task force might converge to a new Committee or fall under one if needed
- Johanna Curiel
- Timo Goosen
- Abbas Naderi
- Jason Johnson
- Noreen Whysel - OWASP Community Manager (Staff)
- Azzedine Islam Mennouchi
OWASP Projects Task Force (Concept)
This is a new type of OWASP initiative, focused on 'getting things done', the concept is still evolving but here are the current (in draft) guiding principles:
- this 'task force is an invitation-only group' (to join the task force, requests should be made directly with existing task force members)
- all existing members have VETO power, and it is assumed that all decisions are backed up with all existing members
- only existing members can send the invitations
- there is a 1 month minimum activity required (or the member is temporarily out).
- invitations are automatically approved in 24h
- existing members can VETO new members (and existing members can be kickout by majority)
- there an one special member who has veto power the responsibility to enforce the 'one month contribution MIA scenario' (i.e. to kick out the 'non contributing members')
- all communication MUST be made (as much as practically possible) under public mediums: Wiki, public mailings, public Hangout sessions
- there are NO decisions made BEHIND closed doors, or without a solid digital (hyperlinkable) trail
Google Group You must be logged in your OWASP Google App account to view and post to the group.
Project Online Resources
This page is for OWASP project leaders and details some of the online services that have been found to be useful for OWASP projects.
How to Run a Successful Open Source Project
Openhub (formerly known as Ohloh)
OWASP is a registered Organisation on Openduck, a free, public directory of Free and Open Source Software and the contributors who create and maintain it.
If you manage an OWASP project you should:
- Register yourself on Openhub
- Make sure your project is registered on Openduck- you can add it yourself if it is not
- Register yourself as the manager
- Check that the settings are correct, especially the repositories
- Make sure it belongs to the OWASP organisation - Contact OWASP or Simon Bennetts if it is not
- Claim all of your contributions to open source projects
- Consider including Openhub Widgets on your project homepage or wiki
- Help other OWASP projects by flagging and rating the ones you use
Other Free Services
These are all free to open source projects.
- http://crowdin.net/ a translation and localization management platform
- https://scan.coverity.com/ C/C++/C# and Java static source code analysis
- https://www.mir-swamp.org/ - This web based code analysis service is 100% FREE of charge and is open to the public
Other Paid For Services
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.
- You will need to gather the following information together for your application:
A - PROJECT
- Project Name,
- Project purpose / overview,
- Project Roadmap,
- Project links (if any) to external sites,
- Project License,
- Project Leader name,
- Project Leader email address,
- Project Leader wiki account - the username (you'll need this to edit the wiki),
- Project Contributor(s) (if any) - name email and wiki account (if any),
- Project Main Links (if any).
- Check out the Guidelines for OWASP Projects.
- Grant Spending Policy
- Project Spending Policy
- Project Sponsorship Operational Guidelines
OWASP Recommended Licenses
|Allow commercial uses of your work?|
|Allow modifications of your work?|
|Yes, no restriction except attribution||Yes, as long as modification are also opensource||No|
(fewest restrictions, even allowing proprietary modifications and proprietary forks of your project, and more up-to-date than BSD license)
(requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)
|Sorry, such licenses are not opensource and are not eligible to become an OWASP Sponsored Project. If this is really what you want, consider using CC-BY-ND or CC-BY-NC-ND. See http://creativecommons.org/choose for more information and note that they label these two license as "not a Free Culture License"|
(prevents GPL's SaaS loophole)
|Library Project||LGPL 3.0
(similar to GPL but modified for use with libraries that may be called by other proprietary programs)
|Document Project (includes E-Learning, presos, books, etc)||CC-BY 3.0|
(like Apache but for documents)
(like GPL but for documents. Alternately you can use GFDL, but projects like Debian and Ubuntu don't accept it)
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.
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:
- 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.
- Link to your wiki page.
- Link to your code repository or a link to where readers can download your project.
- 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.
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.
- 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.
- All benefits given to Incubator Projects
- Technical Writing Support
- Graphic Design Support
- Project Promotion Support
- OWASP OSS and OPT: Preference
- 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.
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.
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.
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.
- The OWASP Brand may be used to direct people to the OWASP website for information about application security.
- The OWASP Brand may be used in commentary about the materials found on the OWASP website.
- The OWASP Brand may be used by OWASP Members in good standing to promote a person or company's involvement in OWASP.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
Book Cover Files
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.
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 strategic value to OWASP and application security as a whole.
- 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.
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.
If you need any help with anything projects related, or if you simply need some more information, please do not hesitate to Contact Us.
This category has the following 143 subcategories, out of 143 total.
Pages in category "OWASP Project"
The following 200 pages are in this category, out of 326 total.(previous 200) (next 200)