OWASP Vulnerability Management Guide - Revision history

Efrenz at 03:17, 2 May 2019

2019-05-02T03:17:49Z

2018-09-24T04:45:09Z

2018-09-24T04:42:49Z

‎Description

2018-09-24T04:40:37Z

2018-09-24T04:34:14Z

2018-09-24T04:32:55Z

2018-09-24T02:48:47Z

‎Getting Involved

2018-09-24T02:40:19Z

‎Roadmap

2018-09-24T02:36:29Z

2018-09-24T02:36:06Z

@@ Line 29: / Line 29: @@
 As of '''September 2018''', the highest priorities for the next 8 months are:
 * a “bare bones” list (done!);
-* a logical diagram (coming Q4 2018);
+* a logical diagram (coming soon);
-* a Power Point presentation (coming Q4 2018);
+* a Power Point presentation (coming soon);
-* a DIY guide with notes that reference controls, useful sources, and examples (coming Q1 2019);
+* a DIY guide with notes that reference controls, useful sources, and examples (coming 2019);
-* a DIY guide with the notes, examples, and illustrations (coming Q1 2019).
+* a DIY guide with the notes, examples, and illustrations (coming 2020).
 Subsequent releases will be unscheduled:

@@ Line 24: / Line 24: @@
 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>
 ==Roadmap==
@@ Line 55: / Line 54: @@
 * [https://www.owasp.org/index.php/User:Efrenz Elizabeth Frenz]
 </span>
 ==Classifications==

@@ Line 14: / Line 14: @@
 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:
+[[Talk:OWASP_Vulnerability_Management_Guide#OWASP_Vulnerability_Management_Guide_v.1|Vulnerability Management Cycle]]:
 * DETECTION
 * REPORTING

@@ Line 48: / Line 48: @@
 * '''Promoting'''. Please spread the word!
 * '''Adopting'''. The best contribution is your adoption!
-* '''Collaborating'''. Please leave a comment using Discussion tab link to GitHub.
+* '''Collaborating'''. Please specify in comments how would you like to contribute on [https://github.com/lizfrenz/owasp-vuln-mngmnt GitHub].
 </span>

@@ Line 29: / Line 29: @@
 <span style="color:#000000">
 As of '''September 2018''', the highest priorities for the next 8 months are:
-* a “bare bones” list (coming soon);
+* a “bare bones” list (done!);
 * a logical diagram (coming Q4 2018);
 * a Power Point presentation (coming Q4 2018);

← Older revision		Revision as of 04:32, 24 September 2018
Line 40:		Line 40:

	</span>		</span>
		+
		+	\| valign="top" style="padding-left:25px;width:200px;" \|

	==Getting Involved==		==Getting Involved==

@@ Line 43: / Line 43: @@
 ==Getting Involved==
 <span style="color:#000000">
-Involvement in the development and promotion of the <strong>OWASP Vulnerability Management Guide</strong> is actively encouraged!
+Get Involved by:
-You do not have to be a security expert or a programmer to contribute.
+* '''Promoting'''. Please spread the word!
-Some of the ways you can help are as follows:
+* '''Adopting'''. The best contribution is your adoption!
+* '''Collaborating'''. Please leave a comment using Discussion tab link to GitHub.
-Spreading awareness of the project
+</span>
 == Project Leader ==

@@ Line 12: / Line 12: @@
 ==Description==
 <span style="color:#000000">
-The guide will demonstrate a set of best practices that organizations can use to establish an effective and efficient vulnerability management program.
+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.
 </span>