OWASP Product Requirement Recommendations Library

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

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 Product Requirement Recommendations Library
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.

Description
The OWASP Product Requirement Recommendations Library is a list of best practice recommended security product requirements that can be easily used for new web application development projects.

Licensing
Creative Commons Attribution ShareAlike 3.0


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is OWASP Product Requirement Recommendations Library?
Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?

The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the OWASP Press. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.

This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.

Presentation

 * Proposal Project PPT @ http://rgrupe.com/OWASP/ OWASP_PRRL_Overview.pptx
 * In-work, very rough draft of Product Requirements Recommendations Document (PRRD) @ http://rgrupe.com/OWASP/OWASP_PPRD.xlsx (Recommendations tab)

Project Leader

 * [mailto:robert@rgrupe.com Robert Grupe]

Related Projects
This is where you can link to other OWASP Projects that are similar to yours.

Openhub

 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download
This is where you can link to your repository.

In Print
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.

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.


 * }

=FAQs=

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.

= Acknowledgements =

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:


 * Dennis Groves
 * Andrew Martin
 * Josh Thomas
 * YOUR NAME BELONGS HERE

= Road Map and Getting Involved =

2014Q4: Start-Up Initiation Goals - Proposed Project Approval - Recruitment - Categorisation Taxonomy 1st Draft - PRRD 1st Draft Planning - Initial Project  Backlog - Plan/Roadmap/Sprints Promotion - OWASP Wiki Page - PPT on SlideShare - OWASP Mail List - LinkedIn - NewsBits Research - Collaboration platform - WebApp Security Controls Categorisation Taxonomy - WebApp Functionality Taxonomy

2015Q1: Execution Kickoff - OWASP Cheat sheets in PPRD - 1st Quarterly Release - Partners & Sponsors - Promotion: PR

2015-Next: - Mobile Web App Version - Regulatory Requirements - Etc. =Project About=

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