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 Application Security Program Quick Start Guide Project"

From OWASP
Jump to: navigation, search
(→‎Main)
(→‎Core Content)
 
(46 intermediate revisions by 2 users not shown)
Line 8: Line 8:
  
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- 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 Application Security Program Quick Start Guide Project==
 
==The OWASP Application Security Program Quick Start Guide Project==
  
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
−
<span style="color:#ff0000">
+
 
−
This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program . The intended goal of the AppSec program is to implement measures throughout the code's life-cycle to prevent gaps in the application security policy or the underlying system through flaws in the design, development, deployment, upgrade, or maintenance of the application.
+
This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program . The intended goal of the AppSec program is to implement measures throughout the code's life-cycle to prevent gaps in the application security policy or the underlying system through flaws in the design, development, deployment, upgrade, or maintenance of the application.
 +
 
 
The application security program should effectively manage the security of its application systems, protecting information from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality and availability.
 
The application security program should effectively manage the security of its application systems, protecting information from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality and availability.
−
A fundamental component of this improved application security management is the ability to demonstrate acceptable levels of risk based on defined KPIs, including but limited to:  
+
 
−
• The number of vulnerabilities present in an application
+
A fundamental component of this improved application security management is the ability to demonstrate acceptable levels of risk based on defined KPIs, including but not limited to:  
−
• The time to fix vulnerabilities
+
 
−
• The remediation rate of vulnerabilities  
+
*The number of vulnerabilities present in an application
−
• The time vulnerabilities remain open.
+
*The time to fix vulnerabilities
 +
*The remediation rate of vulnerabilities  
 +
*The time vulnerabilities remain open.
 +
 
 
The application security program deliverables include a holistic view of the state of security for each application, identifying the risks associated with the application and the countermeasures implemented to mitigate those risks, explaining how security is implemented, planning for system downtimes and emergencies, and providing a formal plan to improve the security in one or more of these areas.
 
The application security program deliverables include a holistic view of the state of security for each application, identifying the risks associated with the application and the countermeasures implemented to mitigate those risks, explaining how security is implemented, planning for system downtimes and emergencies, and providing a formal plan to improve the security in one or more of these areas.
  
−
</span>
 
  
  
−
==Description==
+
==Audience==
 +
 
 +
The intended audience of this document is anyone from security engineers, developers, program managers, senior managers or a senior executive. This guide should be considered the start of a comprehensive approach, it is intended to give the basic questions and answers that should be asked by those who are in charge of the application security program in your organization, this includes those responsible for managing the risk of the entire organization.
 +
 
  
−
This guide is intended to be a [relatively] short, straightforward introductory guide to standing-up or improving upon an Application Security Program that implements measures throughout the code's life-cycle to prevent security gaps.
 
  
 
==Licensing==
 
==Licensing==
  
 
Creative Commons Attribution-NonCommercial-ShareAlike
 
Creative Commons Attribution-NonCommercial-ShareAlike
 +
 +
 +
==Project Sponsor==
 +
The OWASP Application Security Program Quick Start Guide Project is sponsored by [https://whitehatsec.com/ WhiteHat Security Inc.].
 +
 +
[[File:WhiteHatSecurity-logo-small.png | link=https://whitehatsec.com/]]
 +
  
 
<!-- 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;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 Application Security Program Quick Start Guide Project? ==
+
== Core Content ==
 +
 
 +
Broken out into non-calendar days. The guide prioritizes the activities needed to measure and improve the relative security of web applications under the same authority. Included are additional resources to the related task, such as asset management and security policies.
 +
 
 +
Table of Contents
  
−
This guide is intended to be a [relatively] short, straightforward introductory guide to standing-up or improving upon an Application Security Program that implements measures throughout the code's life-cycle to prevent security gaps.
+
*[[Day 1]] - Landscape Evaluation
 +
*[[Day 2]] - Assets & Communication Plans
 +
*[[Day 3]] - Assessments
 +
*[[Day 4]] - Metrics
 +
*[[Day 5]] - Controls & Prioritization
 +
 
 +
The complete TOC along with the HTML content can be found on the [https://www.owasp.org/index.php?title=Application_Security_Program_Quick_Start_Guide Project Page.].
  
 
== Presentation ==
 
== Presentation ==
Line 47: Line 67:
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- 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">
−
This is where you can link to slide presentations related to your project.
+
Placeholder
 
</span>
 
</span>
  
Line 53: Line 73:
  
  
−
== Project Leader ==
+
== Project lead and authors ==
−
 
 
−
 
 
−
 
 
−
* [mailto:[email protected] Gabriel Gumbs]
 
  
 +
* [https://twitter.com/GabrielGumbs Gabriel Gumbs]
 +
* [https://twitter.com/jeremiahg Jeremiah Grossman]]
 +
* [https://twitter.com/RSnake Robert Hansen]
 +
* [https://twitter.com/jerryhoff Jerry Hoff]
 +
* [https://twitter.com/mattjay Matt Johansen]
  
 
== Related Projects ==
 
== Related Projects ==
Line 64: Line 85:
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- 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">
−
This is where you can link to other OWASP Projects that are similar to yours.
 
−
</span>
 
  
 +
<!-- https://www.owasp.org/index.php/OWASP_Application_Security_Guide_For_CISOs_Project -->
  
 +
</span>
  
−
== Openhub ==
 
  
  
Line 80: Line 100:
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- 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">
−
This is where you can link to your repository.
+
*[https://www.owasp.org/images/9/97/OWASP_Quick_Start_Guide_v.1.0.docx Word Document]
 +
*[https://www.owasp.org/images/5/53/OWASP_Quick_Start_Guide.pdf Downloadable PDF]     
 
</span>
 
</span>
  
−
 
+
== Project Mailing List ==
 +
[https://lists.owasp.org/mailman/listinfo/owasp-application-security-program-quick-start-guide Project Mailing List]
  
 
== News and Events ==
 
== News and Events ==
  
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
−
<span style="color:#ff0000">
+
Initial release pending
−
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
 
−
</span>
 
−
 
 
−
 
 
−
 
 
−
== 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>
 
  
  
Line 112: Line 124:
 
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
 
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
 
   |-
 
   |-
−
   | colspan="2" align="center"  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]  
+
   | colspan="2" align="center"  | [[File:CC-BY-NC-SA-4.0.png|link=http://creativecommons.org/licenses/by-nc-sa/4.0/]]  
 
   |-
 
   |-
 
   | colspan="2" align="center"  | [[File:Project_Type_Files_DOC.jpg|link=]]   
 
   | colspan="2" align="center"  | [[File:Project_Type_Files_DOC.jpg|link=]]   
Line 143: Line 155:
 
* [mailto:[email protected] Jerry Hoff]
 
* [mailto:[email protected] Jerry Hoff]
 
* [mailto:[email protected] Robert Hansen]
 
* [mailto:[email protected] Robert Hansen]
 +
* [mailto:[email protected] Matt Johansen]
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =

Latest revision as of 20:22, 6 January 2015

OWASP Project Header.jpg


The OWASP Application Security Program Quick Start Guide Project

This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program . The intended goal of the AppSec program is to implement measures throughout the code's life-cycle to prevent gaps in the application security policy or the underlying system through flaws in the design, development, deployment, upgrade, or maintenance of the application.

The application security program should effectively manage the security of its application systems, protecting information from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality and availability.

A fundamental component of this improved application security management is the ability to demonstrate acceptable levels of risk based on defined KPIs, including but not limited to:

  • The number of vulnerabilities present in an application
  • The time to fix vulnerabilities
  • The remediation rate of vulnerabilities
  • The time vulnerabilities remain open.

The application security program deliverables include a holistic view of the state of security for each application, identifying the risks associated with the application and the countermeasures implemented to mitigate those risks, explaining how security is implemented, planning for system downtimes and emergencies, and providing a formal plan to improve the security in one or more of these areas.


Audience

The intended audience of this document is anyone from security engineers, developers, program managers, senior managers or a senior executive. This guide should be considered the start of a comprehensive approach, it is intended to give the basic questions and answers that should be asked by those who are in charge of the application security program in your organization, this includes those responsible for managing the risk of the entire organization.


Licensing

Creative Commons Attribution-NonCommercial-ShareAlike


Project Sponsor

The OWASP Application Security Program Quick Start Guide Project is sponsored by WhiteHat Security Inc..

WhiteHatSecurity-logo-small.png


Core Content

Broken out into non-calendar days. The guide prioritizes the activities needed to measure and improve the relative security of web applications under the same authority. Included are additional resources to the related task, such as asset management and security policies.

Table of Contents

  • Day 1 - Landscape Evaluation
  • Day 2 - Assets & Communication Plans
  • Day 3 - Assessments
  • Day 4 - Metrics
  • Day 5 - Controls & Prioritization

The complete TOC along with the HTML content can be found on the Project Page..

Presentation

Placeholder



Project lead and authors

Related Projects

Quick Download

Project Mailing List

Project Mailing List

News and Events

Initial release pending


Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
CC-BY-NC-SA-4.0.png
Project Type Files DOC.jpg

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.

Contributors

The first contributors to the project were:

The roadmap will consists of updates to remain relevant with updated technologies and processes. The deliverable will be a 'living' wiki along with several PDF downloads.

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


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_Application_Security_Program_Quick_Start_Guide_Project&oldid=187650"