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 "Category:OWASP Application Security Requirements Project"

From OWASP
Jump to: navigation, search
(Application Security Requirements Overview)
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==About==
+
{|
 +
|-
 +
! width="700" align="center" | <br>
 +
! width="500" align="center" | <br>
 +
|-
 +
| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]
 +
| align="right" |
  
The intention of the OWASP Application Security Requirements project is to assemble a comprehensive list of generic (document) application security requirements that could be used in most projects.
+
|}
 +
= Application Security Requirements Project =
 +
<!--- [[:Category:OWASP Project|Click here to return to OWASP Projects page.]]
 +
[[:Project Information:template Application Security Requirements Project|Click here to see (& edit, if wanted) the template.]]
 +
{{:Project Information:template Application Security Requirements Project}}---->
  
The output of the guide is intended to help all involved in application security, whether its project management, risk assessment, development, testing, etc.
+
== Overview ==
 +
Clearly articulating project-agnostic application security requirements —both general and specific requirements — is the best way to ensure that software is developed under strong and workable security guidance
  
The reason for this project is that while security requirements are sometimes captured well and defined clearly, I feel there are other times when they may not, for any number of reasons.
+
* '''Project purpose:''' To assemble a useful base of generic security requirements that could be used in most applications.
 +
* '''Intended audience:''' Every person involved in application security, but especially for those responsible of sytem analysis and design.
 +
* '''Project products:''' Deliverables would be business-focused, developed for Business Analysts and Project Managers rather than software developers.
  
OWASP believe that clearly articulating an application security requirements guide detailing both high-level and specific requirements is the best way to ensure that a strong, robust yet workable guide can become default in all aspects of application security.
+
= About =
  
==Joining the Project==
+
{{:Projects/OWASP Application Security Requirements Project | Project About}}
If you are interested in volunteering for the project, or have a comment, question, or suggestion, please join the Application Security Requirements [http://lists.owasp.org/mailman/listinfo/owasp-appsec-requirements mailing list].
 
  
==Application Security Requirements Overview==
+
= Roadmap =
  
The intention of the OWASP Application Security Requirements project is to assemble a comprehensive list of generic (document) application security requirements that could be used in most projects.
+
We are just re-starting the project after a couple of years without any progress.
 +
We need all the help we can get to make this a successful project
  
[[Category:Technology]]
+
== Short-term actions ==
 +
#. Identify (map from other owasp projects) categorization and prioritize
 +
#. Identify software development standards to document requirements
 +
#. Define work plan
 +
#. Define document's introduction (scope of the document, composition of the document)
 +
#. Write first draft related to web applications
 +
#. Review and adjust plan
  
[[Category:OWASP Project]]
+
==Long-term actions==
 +
* Write requirements for mobile applications
 +
* Write requirements for web services
 +
* Write requirements for mobile applications
 +
 
 +
<br> __NOTOC__ <headertabs />
 +
 
 +
[[Category:OWASP_Document]] [[Category:OWASP_Alpha_Quality_Document]]
 +
[[Category:OWASP Project|Application Security Requirements Project]]

Latest revision as of 00:43, 27 July 2014



OWASP Inactive Banner.jpg

Overview

Clearly articulating project-agnostic application security requirements —both general and specific requirements — is the best way to ensure that software is developed under strong and workable security guidance

  • Project purpose: To assemble a useful base of generic security requirements that could be used in most applications.
  • Intended audience: Every person involved in application security, but especially for those responsible of sytem analysis and design.
  • Project products: Deliverables would be business-focused, developed for Business Analysts and Project Managers rather than software developers.
PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Application Security Requirements Project (home page)
Purpose: To assemble a useful base of generic security requirements that could be used in most applications.
License: Creative Commons Attribution ShareAlike 3.0 license
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Main links:
Key Contacts
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases

We are just re-starting the project after a couple of years without any progress. We need all the help we can get to make this a successful project

Short-term actions

  1. . Identify (map from other owasp projects) categorization and prioritize
  2. . Identify software development standards to document requirements
  3. . Define work plan
  4. . Define document's introduction (scope of the document, composition of the document)
  5. . Write first draft related to web applications
  6. . Review and adjust plan

Long-term actions

  • Write requirements for mobile applications
  • Write requirements for web services
  • Write requirements for mobile applications

Media in category "OWASP Application Security Requirements Project"

This category contains only the following file.