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"
(5 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;">[[ | + | <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 --> | ||
Line 13: | Line 13: | ||
--> | --> | ||
+ | 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 | + | 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 25: | 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 | + | == What is PRRL? == |
− | |||
<!-- | <!-- | ||
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? | 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? | ||
Line 32: | Line 42: | ||
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 == | ||
− | * | + | * [http://www.slideshare.net/rgrupe/owasp-prrl-overview Project Overview] |
− | |||
− | |||
− | -- | ||
== Project Leader == | == Project Leader == | ||
Line 46: | Line 61: | ||
== Related Projects == | == Related Projects == | ||
+ | * [https://www.owasp.org/index.php/Category:OWASP_Guide_Project OWASP Developer Guide] | ||
+ | * [https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP Application Security Verification Standard] | ||
* [https://www.owasp.org/index.php/Category:OWASP_Testing_Project OWASP Testing Project] | * [https://www.owasp.org/index.php/Category:OWASP_Testing_Project OWASP Testing Project] | ||
Line 55: | Line 72: | ||
| valign="top" style="padding-left:25px;width:200px;" | | | valign="top" style="padding-left:25px;width:200px;" | | ||
+ | ==Quick Download== | ||
+ | <ul> | ||
+ | <li>Coming 2015Q1: 1st draft of OWASP (PRRL) | ||
+ | </ul> | ||
<!-- Unused Sections | <!-- Unused Sections | ||
− | |||
− | |||
− | |||
In Print | In Print | ||
This is where you place links to where your project product can be downloaded or purchased, in the case of a book. | This is where you place links to where your project product can be downloaded or purchased, in the case of a book. | ||
--> | --> | ||
− | |||
==Classifications== | ==Classifications== | ||
Line 86: | 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 | + | 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 = |
Latest revision as of 12:05, 19 May 2015
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:
- Robert Grupe
- YOUR NAME BELONGS HERE
- 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
- 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? | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|