This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Product Requirement Recommendations Library"

From OWASP
Jump to: navigation, search
(Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...")
 
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
=Main=
 
=Main=
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
−
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div>
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.
 
−
</span>
 
  
 
==The OWASP Product Requirement Recommendations Library==
 
==The OWASP Product Requirement Recommendations Library==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
<!--  
−
<span style="color:#ff0000">
+
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.
−
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.
+
-->
−
</span>
 
−
 
 
  
 +
The OWASP Product Requirement Recommendations Library (PRRL) is a list of best practice recommended security product requirements that can be easily used for new web application definition and User Acceptance Testing (UAT) criteria.
  
 
==Description==
 
==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.
+
The objectives of OWASP PRRL are to:
 +
<ul>
 +
<li>Improve end-product security design
 +
<li>Enable efficient application security consideration and definition in early PDLC phases Scoping and Design.
 +
    <ul>
 +
    <li>Reduce time and resource needs for project AppSec requirements discovery and definitions
 +
    </ul>
 +
<li>Improve application development and testing estimations for security best practice and regulatory compliance
 +
<li>Establish an industry recognized best practice benchmark standard that can be used evaluate application security designs
 +
<li>Make OWASP recommendations more accessible to business/non-technical stakeholders
 +
</ul>
  
 
==Licensing==
 
==Licensing==
Line 32: Line 36:
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
−
== What is OWASP Product Requirement Recommendations Library? ==
+
== What is PRRL? ==
−
 
+
<!--  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
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?
−
<span style="color:#ff0000">
 
−
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?
 
−
</span>
 
−
 
 
 
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 [http://scriptogr.am/dennis-groves/post/owasp-press 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.
 
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 [http://scriptogr.am/dennis-groves/post/owasp-press 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.
 +
-->
  
−
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
+
OWASP PRRL is working to develop:
 +
<ul>
 +
<li>OWASP Product Requirement Recommendations Library (PRRL)
 +
<li>Best Practice Application Security Work Flow Process Diagrams
 +
<li>Requirements Categorizations Taxonomy: Application Functionality, Risks, Controls
 +
<li>Application and Content Security Best Practices Resources Links
 +
</ul>
  
 
== Presentation ==
 
== Presentation ==
  
−
* Proposal Project PPT @ http://rgrupe.com/OWASP/ OWASP_PRRL_Overview.pptx
+
* [http://www.slideshare.net/rgrupe/owasp-prrl-overview Project Overview]
−
* In-work, very rough draft of Product Requirements Recommendations Document (PRRD) @ http://rgrupe.com/OWASP/OWASP_PPRD.xlsx (Recommendations tab)
 
  
 
== Project Leader ==
 
== Project Leader ==
−
 
  
 
* [mailto:[email protected] Robert Grupe]
 
* [mailto:[email protected] Robert Grupe]
−
 
  
 
== Related Projects ==
 
== Related Projects ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [https://www.owasp.org/index.php/Category:OWASP_Guide_Project OWASP Developer Guide]
−
<span style="color:#ff0000">
+
* [https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP Application Security Verification Standard]
−
This is where you can link to other OWASP Projects that are similar to yours.  
+
* [https://www.owasp.org/index.php/Category:OWASP_Testing_Project OWASP Testing Project]
−
</span>
 
−
 
 
−
 
 
−
 
 
−
== Openhub ==
 
  
 +
<!-- Unused Section
 +
Openhub
 +
-->
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
| valign="top"  style="padding-left:25px;width:200px;" |
 
| valign="top"  style="padding-left:25px;width:200px;" |
  
−
== Quick Download ==
+
==Quick Download==
−
 
+
<ul>
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
<li>Coming 2015Q1: 1st draft of OWASP (PRRL)
−
<span style="color:#ff0000">
+
</ul>
−
This is where you can link to your repository.
+
<!-- Unused Sections
−
</span>
+
In Print
−
 
+
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.  
−
 
+
-->
−
 
 
−
== In Print ==
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.  
 
−
</span>
 
−
 
 
−
 
 
  
 
==Classifications==
 
==Classifications==
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.
 
−
</span>
 
  
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
Line 109: Line 98:
  
 
=FAQs=
 
=FAQs=
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.'
 
−
</span>
 
−
 
  
 
==How can I participate in your project?==
 
==How can I participate in your project?==
Line 120: Line 103:
  
 
==If I am not a programmer can I participate in your project?==
 
==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.  
+
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 contributors who are interested in researching and writing product requirements based on international security standards and legal and regulatory requirements (personal data protection, PCI, HIPAA, etc.).
  
 
= Acknowledgements =
 
= Acknowledgements =
Line 126: Line 109:
 
==Contributors==
 
==Contributors==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
<!--  
 
<span style="color:#ff0000">
 
<span style="color:#ff0000">
 
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.  
 
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.  
Line 132: Line 115:
 
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
</span>
 
</span>
 +
-->
  
−
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].  
+
The OWASP Product Requirements Recommendations Library project is a new project to be developed by a pioneering worldwide team of volunteers.  
  
−
The first contributors to the project were:
+
The first contributors to the project have been:
  
−
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+
<!-- * [https://www.owasp.org/index.php/User:Robert_Grupe Robert Grupe] -->
−
* [https://github.com/sublimino Andrew Martin]
+
* [http://www.rgrupe.com Robert Grupe]
−
* [https://github.com/Lambdanaut Josh Thomas]
 
 
* '''YOUR NAME BELONGS HERE'''
 
* '''YOUR NAME BELONGS HERE'''
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
  
−
2014Q4: Start-Up Initiation
+
<ul><b>2014Q4/2015Q1: Start-Up Initiation</b>
−
Goals
+
<li>Goals
−
- Proposed Project Approval
+
<ul>
−
- Recruitment
+
<li>Proposed Project Approval
−
- Categorisation Taxonomy 1st Draft
+
<li>Recruitment
−
- PRRD 1st Draft
+
<li>Categorisation Taxonomy 1st Draft
−
Planning
+
<li>PRRD 1st Draft
−
- Initial  Project  Backlog
+
</ul>
−
- Plan/Roadmap/Sprints
+
<li>Planning
−
Promotion
+
<ul>
−
- OWASP Wiki Page
+
<li>Initial  Project  Backlog
−
- PPT on SlideShare
+
<li>Plan/Roadmap/Sprints
−
- OWASP Mail List
+
</ul>
−
- LinkedIn  
+
<li>Promotion
−
- NewsBits
+
<ul>
−
Research
+
<li>OWASP Wiki Page
−
- Collaboration platform
+
<li>PPT on SlideShare
−
- WebApp Security Controls  Categorisation Taxonomy
+
<li>OWASP Mail List
−
- WebApp Functionality Taxonomy
+
<li>LinkedIn  
 +
<li>NewsBits
 +
</ul>
 +
<li>Research
 +
<ul>
 +
<li>Collaboration platform
 +
<li>WebApp Security Controls  Categorisation Taxonomy
 +
<li>WebApp Functionality Taxonomy
 +
</ul>
 +
</ul>
  
−
2015Q1: Execution Kickoff
+
<ul><b>2015Q2: Execution Kickoff</b>
−
- OWASP Cheat sheets in PPRD
+
<li>OWASP Cheat sheets in PPRD
−
- 1st Quarterly Release
+
<li>1st Quarterly Release
−
- Partners & Sponsors
+
<li>Partners & Sponsors
−
- Promotion: PR
+
<li>Promotion: PR
 +
</ul>
 +
 
 +
<ul><b>2015-Next:</b>
 +
<li>Mobile Web App Version
 +
<li>Regulatory Requirements
 +
<li>Etc.
 +
</ul>
  
−
2015-Next:
 
−
- Mobile Web App Version
 
−
- Regulatory Requirements
 
−
- Etc.
 
 
=Project About=
 
=Project About=
−
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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
 
−
</span>
 
  
 
{{:Projects/OWASP_Example_Project_About_Page}}  
 
{{:Projects/OWASP_Example_Project_About_Page}}  

Latest revision as of 12:05, 19 May 2015

OWASP Inactive Banner.jpg

The OWASP Product Requirement Recommendations Library

The OWASP Product Requirement Recommendations Library (PRRL) is a list of best practice recommended security product requirements that can be easily used for new web application definition and User Acceptance Testing (UAT) criteria.

Description

The objectives of OWASP PRRL are to:

  • Improve end-product security design
  • Enable efficient application security consideration and definition in early PDLC phases Scoping and Design.
    • Reduce time and resource needs for project AppSec requirements discovery and definitions
  • Improve application development and testing estimations for security best practice and regulatory compliance
  • Establish an industry recognized best practice benchmark standard that can be used evaluate application security designs
  • Make OWASP recommendations more accessible to business/non-technical stakeholders

Licensing

Creative Commons Attribution ShareAlike 3.0

What is PRRL?

OWASP PRRL is working to develop:

  • OWASP Product Requirement Recommendations Library (PRRL)
  • Best Practice Application Security Work Flow Process Diagrams
  • Requirements Categorizations Taxonomy: Application Functionality, Risks, Controls
  • Application and Content Security Best Practices Resources Links

Presentation

Project Leader

Related Projects

Quick Download

  • Coming 2015Q1: 1st draft of OWASP (PRRL)

Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

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 contributors who are interested in researching and writing product requirements based on international security standards and legal and regulatory requirements (personal data protection, PCI, HIPAA, etc.).

Contributors

The OWASP Product Requirements Recommendations Library project is a new project to be developed by a pioneering worldwide team of volunteers.

The first contributors to the project have been:

    2014Q4/2015Q1: 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
    2015Q2: Execution Kickoff
  • OWASP Cheat sheets in PPRD
  • 1st Quarterly Release
  • Partners & Sponsors
  • Promotion: PR
    2015-Next:
  • Mobile Web App Version
  • Regulatory Requirements
  • Etc.
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


Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Product_Requirement_Recommendations_Library&oldid=195006"