OWASP Example Incubator

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved
• Project About

Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project. The OWASP Incubator Tool/Code Example This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful. Who is ZAP for? ZAP is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. Also, if you are just beginning to learn about security, ZAP is a great tool that allows you to understand much better how these attacks works and affect web applications. Zap provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually. One of the biggest advantages of ZAP are: is Free, Open Source Cross platform Easy to install Supports multiple languages Can be easily integrated with other tools Description This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible. The Zed Attack Proxy (ZAP) is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually. Although this is a sample template, the project is real! Please contribute to this project. Licensing A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. The OWASP Security Principles are free to use. In fact it is encouraged!!! Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together. The OWASP ZAP is licensed under the Apache License, Version 2.0 Presentation This is where you can link to slide presentations related to your project. For a quick overview of ZAP and to see some of the more advanced ZAP features see these tutorial videos on YouTube:   Project Leader A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members. Simon Bennetts Related Projects This is where you can link to other OWASP Projects that are similar to yours. Are you new to web security vulnerabilities? Understanding what are the most critical web application security risks is necessary to comprehend how to use and work with ZAP. There are many resources available if your are looking for information about the most common security risks. One of the most dangerous and common attacks is Injection Flaws,which allows an attacker to relay malicious code through the Web app to another systems within the network. ZAP has different features that allows you to test and find out if your Web application has these kind of flaws. We strongly recommend newbies the following resources: [OWASP TOP 10] [SANS TOP 25] [IEEE TOP 10 Security Flaws] Openhub OWASP Project Openhub

Quick Download This is where you can link to your install files. ZAP 2.3.1 is now available! Download it here: Review this project A link to Openhub review project URL Please help us improve, [Review this project] Repository This is where you can link to your Open Repository URL such as Github or Google code. News and Events This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project. [20 Nov 2013] News 2 [30 Sep 2013] News 1 Classifications Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

Contributors

The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. Be sure to provide a link to a complete list of all the amazing people in your project's community as well.

The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here.

The first contributors to the project were:

• YOUR NAME BELONGS HERE

A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.  

Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.

Weekly Releases

We generate weekly releases of ZAP from the trunk, typically every Monday, available from https://sourceforge.net/projects/zaproxy/files/weekly/

The details of the changes in each weekly release are on the WeeklyFixes wiki page. These are just intended for people who want to use all of the features we've added since the last 'full' release but dont want the hassle of building ZAP from the source code.

While we endeavor to ensure that weekly releases are robust, things may be broken or only partially implemented. If you have not used ZAP before it might be better to start with the latest 'full' release.

We will still carry on doing full releases, which we expect most people to continue to use. For background to weekly releases see this post on the official ZAP blog. http://zaproxy.blogspot.co.uk/

For complete list of releases visit https://code.google.com/p/zaproxy/wiki/HelpReleasesReleases

This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project

PROJECT INFO What does this OWASP project offer you?	RELEASE(S) INFO What releases are available for this project?
what is this project? Name: N/A Purpose: N/A License: N/A who is working on this project? Project Leader(s): N/A how can you learn more? Project Pamphlet: Not Yet Created Project Presentation: Mailing list: N/A Project Roadmap: Not Yet Created Key Contacts Contact the GPC to contribute to this project Contact the GPC to review or sponsor this project	current release pending last reviewed release pending other releases