OWASP - User contributions [en]

User:Mattjay

2015-01-05T23:22:44Z

Mattjay:

https://twitter.com/mattjay
Matt Johansen is a Sr. Manager for the Threat Research Center at WhiteHat Security where he manages a team of Application Security Specialists, Engineers and Supervisors to prevent website security attacks and protect companies' and their customers' data.
Before this he was an Application Security Engineer where he oversaw and assessed more than 35,000 web applications that WhiteHat has under contract for many Fortune 500 companies across a range of technologies.

He was previously a security consultant, where he was responsible for performing network and web application penetration tests. Mr. Johansen is also an instructor of Web Application Security at Adelphi University, where he received his Bachelor of Science in Computer Science, and San Jose State University. He has also been utilized by the SANS Institute as an industry expert for certification review.

Speaking Engagements: (http://mattjay.github.io/talks/)
-BlackHat USA 2011, 2013, 2014
-Defcon 19
-SXSW 2014
-AppSecUSA 2014
-BSidesLV 2011, 2012
-BSidesLA 2011, 2012, 2013, 2014
-BSidesAustin 2014
-Hacker Halted 2011
-FBI's International Conference on Cyber Security
-RSA Conference
-LASCON
-SecTor
-Multiple OWASP Chapters

Certifications: GCIH, GWEB

OWASP Application Security Program Quick Start Guide Project

2015-01-05T23:12:50Z

Mattjay: /* Project lead and authors */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |



==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 [https://whitehatsec.com/ WhiteHat Security Inc.].

[[File:WhiteHatSecurity-logo-small.png | link=https://whitehatsec.com/]]


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://www.owasp.org/index.php?title=Application_Security_Program_Quick_Start_Guide Project Page.].

== Presentation ==



Placeholder


== Project lead and authors ==

* [[User:Gabrielgumbs| '''Gabriel Gumbs''']]
* [[User:JeremiahGrossman| '''Jeremiah Grossman''']]
* [[User:Rsnake| '''Robert Hansen''']]
* [[User:Jerryhoff|'''Jerry Hoff''']]
* [[User:Mattjay|'''Matt Johansen''']]

== Related Projects ==









| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==



[https://www.owasp.org/images/5/53/OWASP_Quick_Start_Guide.pdf Free downloadable PDF]


== Project Mailing List ==
[https://lists.owasp.org/mailman/listinfo/owasp-application-security-program-quick-start-guide Project Mailing List]

== News and Events ==


Initial release pending

==Classifications==

{| width="200" cellpadding="2"
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
|-
| 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=]]
|}

|}

=FAQs=



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.

= Acknowledgements =

==Contributors==

The first contributors to the project were:

* [mailto:gabriel@rfc1122.com Gabriel Gumbs]
* [mailto:jeremiah@whitehatsec.com Jeremiah Grossman]
* [mailto:jerry.hoff@whitehatsec.com Jerry Hoff]
* [mailto:robert.hansen@whitehatsec.com Robert Hansen]
* [mailto:matt@whitehatsec.com Matt Johansen]

= Road Map and Getting Involved =

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.

=Project About=



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


{{:Projects/OWASP_Example_Project_About_Page}}


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]

OWASP Application Security Program Quick Start Guide Project

2015-01-05T23:11:57Z

Mattjay: /* Contributors */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |



==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 [https://whitehatsec.com/ WhiteHat Security Inc.].

[[File:WhiteHatSecurity-logo-small.png | link=https://whitehatsec.com/]]


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://www.owasp.org/index.php?title=Application_Security_Program_Quick_Start_Guide Project Page.].

== Presentation ==



Placeholder


== Project lead and authors ==

* [[User:Gabrielgumbs| '''Gabriel Gumbs''']]
* [[User:JeremiahGrossman| '''Jeremiah Grossman''']]
* [[User:Rsnake| '''Robert Hansen''']]
* [[User:Jerryhoff|'''Jerry Hoff''']]

== Related Projects ==









| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==



[https://www.owasp.org/images/5/53/OWASP_Quick_Start_Guide.pdf Free downloadable PDF]


== Project Mailing List ==
[https://lists.owasp.org/mailman/listinfo/owasp-application-security-program-quick-start-guide Project Mailing List]

== News and Events ==


Initial release pending

==Classifications==

{| width="200" cellpadding="2"
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
|-
| 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=]]
|}

|}

=FAQs=



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.

= Acknowledgements =

==Contributors==

The first contributors to the project were:

* [mailto:gabriel@rfc1122.com Gabriel Gumbs]
* [mailto:jeremiah@whitehatsec.com Jeremiah Grossman]
* [mailto:jerry.hoff@whitehatsec.com Jerry Hoff]
* [mailto:robert.hansen@whitehatsec.com Robert Hansen]
* [mailto:matt@whitehatsec.com Matt Johansen]

= Road Map and Getting Involved =

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.

=Project About=



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


{{:Projects/OWASP_Example_Project_About_Page}}


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]

Application Security Program Quick Start Guide

2015-01-05T23:10:45Z

Mattjay: /* Project lead and authors */

__NOTOC__

{| width="100%" cellspacing="0" cellpadding="10"
|- valign="top"
| width="70%" style="background:#d9e9f9" |

= The Application Security Program Quick Start Guide =

=== Preface ===

This guide is intended to be a short, straightforward introductory guide to standing-up or improving an Application Security Program1. 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 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.

== [[Day 1]] ==
''''' Key Activities: '''''
*[[Day_1#Management|Management]]
*[[Day_1#Security|Security]]
*[[Day_1#IT Operations|IT Operations]]
*[[Day_1#Engineering Groups|Engineering Groups]]

== [[Day 2]] ==
''''' Key Activities: '''''
*[[Day_2#Asset Discovery|Asset Discovery]]
*[[Day_2#Asset Risk Prioritization|Asset Risk Prioritization]]
*[[Day_2#Communication Plan|Communication Plan]]

== [[Day 3]] ==
''''' Key Activities: '''''
*[[Day_3#Vulnerability Assessments|Vulnerability Assessments]]
*[[Day_3#Vulnerability Delivery|Vulnerability Delivery]]

== [[Day 4]] ==
''''' Key Activities: '''''
*[[Day_4#Measured Metrics|Measured Metrics]]

== [[Day 5]] ==
''''' Key activities: '''''
*[[Day_5#Compensating Controls|Compensating Controls]]
*[[Day_5#Mitigating Controls|Mitigating Controls]]
*[[Day_5#Remediation Prioritization|Remediation Prioritization]]

== Conclusion ==
Setting up an effective application security program does require commitment from all elements of the business, and a clear understanding of what resources need to be protected and what level of risk is acceptable. However, given that information, setting up an application security program need not be confusing, difficult, or complex. The keys to success involve planning, making key financial decisions, ensuring all roles and responsibilities are clearly assigned and that all stakeholders within the organization know what to expect.

== Licensing ==

The OWASP Application Security Program Quick Start Guide is free to use. It is licensed under the [http://creativecommons.org/licenses/by-nc-sa/4.0/ Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license].
You are free to:
*Share — copy and redistribute the material in any medium or format
*Adapt — remix, transform, and build upon the material for non-commercial use

The licensor cannot revoke these freedoms as long as you follow the license terms.

| width="100" style="max-height:200px;overflow:hidden;background:#fff;margin:0;padding:0;" cellpadding="0" |

| width="30%" style="background:#eeeeee" |

=Credits =

== Project lead and authors ==

* [[User:Gabrielgumbs| '''Gabriel Gumbs''']]
* [[User:JeremiahGrossman| '''Jeremiah Grossman''']]
* [[User:Rsnake| '''Robert Hansen''']]
* [[User:Jerryhoff|'''Jerry Hoff''']]
* [[User: Mattjay| '''Matt Johansen''']]

== Further Information ==
[https://lists.owasp.org/mailman/listinfo/owasp-application-security-program-quick-start-guide Project Mailing List]

== Application Security Program Quick Start Guide ==

The OWASP Application Security Program Quick Start Guide is also available as
* [https://www.owasp.org/images/5/53/OWASP_Quick_Start_Guide.pdf Free downloadable PDF]

For full information about the Application Security Program Quick Start Guide, including mailing list details, the forward plan, how to contribute, the project status, and alternative media, see the project page:
* [https://www.owasp.org/index.php/OWASP_Application_Security_Program_Quick_Start_Guide_Project The Application Security Program Quick Start Guide Project Page]

|}