Difference between revisions of "Category:OWASP Application Security Requirements Project"

From OWASP
Jump to: navigation, search
m (added verbage about target audience being non-technical)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[:Category:OWASP Project|Click here to return to OWASP Projects page.]]
+
= 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|Click here to see (& edit, if wanted) the template.]]  
{{:Project Information:template Application Security Requirements Project}}
+
{{:Project Information:template Application Security Requirements Project}}---->
[[Category:OWASP Project|Application Security Requirements Project]]
+
  
==Overview==
+
== Overview ==
OWASP believe that clearly articulating project-agnostic web application security requirements&mdash;providing both high-level/general and low-level/specific ''sine quibus non''&mdash;is the best way to ensure that software is developed with strong, robust, yet workable security guidance.
+
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 intent of this project is to assemble a useful base of generic/common web application security requirements that could be used in most projects.
+
* The product of this project is intended to help all involved in web application security, whether it is project management, risk assessment, software development, testing, etc.
+
* The ''reason d'etre'' of this project is that, whilst security requirements are sometimes well captured and clearly defined, there are other times when they are not, for any number of reasons.
+
* Requirements, use-cases, and user stories will tend to be business-focused.  In other words, requirements will be developed more for the consumption of Business Analysts and Project Managers rather than hard-core code warriors.
+
  
==Joining the Project==
+
* '''Project purpose:''' To assemble a useful base of generic security requirements that could be used in most applications.
If you are interested in volunteering for the project, or just have a comment or question, please join the OWASP AppSec Requirements [http://lists.owasp.org/mailman/listinfo/owasp-appsec-requirements mailing list].
+
* '''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 Administrivia==
+
= About =
This project was initiated around September of 2007 under the management of Jamie Fisher. The project was rechartered in August of 2008. The interim project manager is [[User:Mchalmers|Matthew Chalmers]].
+
 
 +
{{:Projects/OWASP Application Security Requirements Project | Project About}}
 +
 
 +
= Roadmap =
 +
 
 +
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 ==
 +
#. 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
 +
 
 +
==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 18:04, 2 January 2014

[edit]

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
  • Contact the GPC to report a problem or concern about this project or to update information.
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.