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 Vulnerability Management Guide"

From OWASP
Jump to: navigation, search
(→‎Related Projects)
m
 
(11 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
−
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
+
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
−
<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>
 
−
==Project About==
 
−
<span style="color:#ff0000">
 
−
{{:Projects/OWASP_Example_Project_About_Page}}
 
  
−
 
+
==OWASP Vulnerability Management Guide==
−
==OWASP Documentation Project Template==
+
<span style="color:#000000">
−
<span style="color:#ff0000">
+
Vulnerability management is one of the most effective means of controlling cybersecurity risk.  Yet, as indicated by the wave of massive data breaches and ransomware attacks, all too often organizations are compromised over missing patches and misconfigurations.  Vulnerability management seeks to help organizations identify such weaknesses in its security posture so that they can be rectified before they are exploited by attackers. The OWASP Vulnerability Management Guide project seeks to establish guidance on the best practices that organizations can use establish a vulnerability management program within their organization.  The guide provides in depth coverage of the full vulnerability management lifecycle including the preparation phase, the vulnerability identification/scanning phase, the reporting phase, and remediation phase.
−
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
 
 
</span>
 
</span>
  
−
The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
+
==Description==
 +
<span style="color:#000000">
 +
The vulnerability management guide should help to breakdown vulnerability management process into a manageable repeatable cycles tailored to your organizational needs. Target audience: information security practitioners of all levels, IT professionals, and business leaders.
  
−
==Description==
+
[[Talk:OWASP_Vulnerability_Management_Guide#OWASP_Vulnerability_Management_Guide_v.1|Vulnerability Management Cycle]]:
−
<span style="color:#ff0000">
+
* DETECTION
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. 
+
* REPORTING
 +
* REMEDIATION
 
</span>
 
</span>
−
 
−
The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category.  The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
 
−
 
−
Creating a new set of project pages from scratch can be a challenging task.  By providing a sample layout, with instructional text and examples, the OWASP Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
 
−
 
−
Contextual custom dictionary builder with character substitution and word variations for pen-testers
 
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
+
<span style="color:#000000">
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
+
The OWASP Vulnerability Management project is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.  
 
</span>
 
</span>
−
 
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}. 
 
  
 
==Roadmap==
 
==Roadmap==
−
<span style="color:#ff0000">
+
<span style="color:#000000">
−
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
+
As of '''September 2018''', the highest priorities for the next 8 months are:  
−
<strong>
+
* a “bare bones” list (done!);
−
* Complete the first draft of the Tool Project Template
+
* a logical diagram (coming soon);
−
* Get other people to review the Tool Project Template and provide feedback
+
* a Power Point presentation (coming soon);
−
* Incorporate feedback into changes in the Tool Project Template
+
* a DIY guide with notes that reference controls, useful sources, and examples (coming 2019);
−
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
+
* a DIY guide with the notes, examples, and illustrations (coming 2020).
−
</strong>
 
  
−
Subsequent Releases will add
+
Subsequent releases will be unscheduled:
−
<strong>
+
* Bug Fix
−
* Internationalization Support
+
* Internationalization
−
* Additional Unit Tests
 
−
* Automated Regression tests
 
−
</strong>
 
  
−
==Getting Involved==
+
</span>
−
<span style="color:#ff0000">
 
−
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
 
−
You do not have to be a security expert or a programmer to contribute.
 
−
Some of the ways you can help are as follows:
 
  
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
| valign="top"  style="padding-left:25px;width:200px;" |
  
−
== Project Resources ==
+
==Getting Involved==
−
<span style="color:#ff0000">
+
<span style="color:#000000">
−
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.  
+
Get Involved by:
 +
* '''Promoting'''. Please spread the word!
 +
* '''Adopting'''. The best contribution is your adoption!
 +
* '''Collaborating'''. Please specify in comments how would you like to contribute on [https://github.com/lizfrenz/owasp-vuln-mngmnt GitHub].  
 
</span>
 
</span>
−
 
−
[https://github.com/SamanthaGroves Installation Package]
 
−
 
−
[https://github.com/SamanthaGroves Source Code]
 
−
 
−
[https://github.com/SamanthaGroves What's New (Revision History)]
 
−
 
−
[https://github.com/SamanthaGroves Documentation]
 
−
 
−
[https://github.com/SamanthaGroves Wiki Home Page]
 
−
 
−
[https://github.com/SamanthaGroves Issue Tracker]
 
−
 
−
[https://github.com/SamanthaGroves Slide Presentation]
 
−
 
−
[https://github.com/SamanthaGroves Video]
 
  
 
== Project Leader ==
 
== Project Leader ==
 
<span style="color:#000000">
 
<span style="color:#000000">
−
Elizabeth Frenz is a highly experienced information security professional that specializes in taking risk based approaches to improving the security and quality of software products. She works as Information Security Analyst for DOE DIIT. Previously in her career she led the vulnerability management program for a Fortune 500 company that builds software solutions for the pharmaceutical industry. Elizabeth also has extensive experience in the identity and access management arena and was one of the contributors to an IEEE standard for using biometrics for identity and access management.  She is an active member in the NY information security scene and serves as chapter leader of the NYC OWASP chapter.  Elizabeth holds an MS degree in Systems Management from NYU.
+
* [https://www.owasp.org/index.php/User:Efrenz Elizabeth Frenz]
 
</span>
 
</span>
  
−
== Related Projects ==
+
== Donate to OWASP ==
−
<span style="color:#000000">
+
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">{{#widget:PayPal Donation
−
No related OWASP projects yet.
+
|target=_blank
−
</span>
+
|budget=Other (Website Donation) }}</div>
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Tool_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 99: Line 64:
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]
+
   | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Document]]
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
+
   | rowspan="2" width="50%" valign="top" align="center" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
−
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]   
+
   | width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=Builders]]   
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
+
   | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=Defenders]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/3.0/| Creative Commons Attribution ShareAlike 3.0 License]]
+
   | colspan="2" align="center" | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/3.0/| Creative Commons Attribution ShareAlike 3.0 License]]
 
   |}
 
   |}
 
|}
 
|}
Line 112: Line 77:
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
−
[[Category:OWASP Project]] [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]  
 +
[[Category:OWASP_Document]]

Latest revision as of 03:17, 2 May 2019

OWASP Project Header.jpg


OWASP Vulnerability Management Guide

Vulnerability management is one of the most effective means of controlling cybersecurity risk. Yet, as indicated by the wave of massive data breaches and ransomware attacks, all too often organizations are compromised over missing patches and misconfigurations. Vulnerability management seeks to help organizations identify such weaknesses in its security posture so that they can be rectified before they are exploited by attackers. The OWASP Vulnerability Management Guide project seeks to establish guidance on the best practices that organizations can use establish a vulnerability management program within their organization. The guide provides in depth coverage of the full vulnerability management lifecycle including the preparation phase, the vulnerability identification/scanning phase, the reporting phase, and remediation phase.

Description

The vulnerability management guide should help to breakdown vulnerability management process into a manageable repeatable cycles tailored to your organizational needs. Target audience: information security practitioners of all levels, IT professionals, and business leaders.

Vulnerability Management Cycle:

  • DETECTION
  • REPORTING
  • REMEDIATION

Licensing

The OWASP Vulnerability Management project is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Roadmap

As of September 2018, the highest priorities for the next 8 months are:

  • a “bare bones” list (done!);
  • a logical diagram (coming soon);
  • a Power Point presentation (coming soon);
  • a DIY guide with notes that reference controls, useful sources, and examples (coming 2019);
  • a DIY guide with the notes, examples, and illustrations (coming 2020).

Subsequent releases will be unscheduled:

  • Bug Fix
  • Internationalization

Getting Involved

Get Involved by:

  • Promoting. Please spread the word!
  • Adopting. The best contribution is your adoption!
  • Collaborating. Please specify in comments how would you like to contribute on GitHub.

Project Leader

Classifications

Project Type Files DOC.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Creative Commons Attribution ShareAlike 3.0 License
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Vulnerability_Management_Guide&oldid=250925"