Security/Threat Analysis - Revision history

Lhinds at 13:54, 14 March 2018

2018-03-14T13:54:41Z

Shohel at 11:46, 11 July 2014

2014-07-11T11:46:20Z

Shohel: /* Threat Modelling Process for OpenStack Projects */

2014-06-30T07:49:14Z

‎Threat Modelling Process for OpenStack Projects

Shohel at 10:49, 5 June 2014

2014-06-05T10:49:42Z

Shohel at 10:19, 5 June 2014

2014-06-05T10:19:23Z

Shohel at 08:23, 5 June 2014

2014-06-05T08:23:44Z

Cristian Fiorentino at 21:32, 24 April 2014

2014-04-24T21:32:43Z

Shohel: /* Ongoing Work */

2014-04-23T06:42:37Z

‎Ongoing Work

Shohel: /* Ongoing Work */

2014-04-23T06:41:58Z

‎Ongoing Work

Shohel: /* Threat Modelling Process for OpenStack Projects */

2014-04-23T06:39:50Z

‎Threat Modelling Process for OpenStack Projects

@@ Line 12: / Line 12: @@
 [https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.md Threat Modelling process]
-=== Ongoing Work ===
+===== Git Repo: =====
 Earlier we have used Google Docs for sharing documents, documents are still shared from Google Docs,
@@ Line 19: / Line 23: @@
 [https://drive.google.com/file/d/0B1aEVfmQtqnobzB6M21uMEFXNUE/edit?usp=sharing Keystone Threat Modelling]
-===== Git Repo: =====
+https://github.com/shohel02/OpenStack_Threat_Modelling
 ===== Nova: =====
@@ Line 31: / Line 31: @@
 https://github.com/criscad/OpenStack_Threat_Modelling.git
 === Earlier reports on Threat Modelling related to OpenStack ===

@@ Line 10: / Line 10: @@
 Technical steps are defined below:
-[https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.pdf Threat Modelling process]
+[https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.md Threat Modelling process]
 === Ongoing Work ===

@@ Line 9: / Line 9: @@
 Check the [[Security/Threat_Analysis/process|process page]] to know the overall process
-A technical steps are defined below:
+Technical steps are defined below:
 [https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.pdf Threat Modelling process]

@@ Line 11: / Line 11: @@
 A technical steps are defined below:
 [https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.pdf Threat Modelling process]
 === Ongoing Work ===
@@ Line 35: / Line 33: @@
 === Meeting ===
-Meeting on IRC Channel every alternate Fridays's  17.00 UTC
+( <sub>Meeting on IRC Channel every alternate Fridays's  17.00 UTC
-at Freenode's  ##openstack-threat-analysis  (unofficial channel),
+at Freenode's  ##openstack-threat-analysis  (unofficial channel)</sub>  )
 [[Security/Threat_Analysis/Meetings|Meeting Information]]

@@ Line 6: / Line 6: @@
 </gallery>
-===== Threat Modelling Process for OpenStack Projects =====
+==== Threat Modelling Process for OpenStack Projects ====
-Check the process page to know the overall process
+Check the [[Security/Threat_Analysis/process|process page]] to know the overall process
 A technical steps are defined below:

@@ Line 1: / Line 1: @@
 == OpenStack Threat Modelling ==
-Security is one of the biggest concern for any cloud solutions. The aim of this project is proactively identify threats and weakness in OpenStack Cloud and contribute to build a secure and robust platform. Threat modelling takes a comprehensive look at the system at hand – components, protocols and code - against the existence and capability of an adversary looking for known vulnerabilities. When a threat is identified, it is tallied and reported to the development team. In some cases, the threat analysis team may also include a suggestion to fix the vulnerabilities and related threat.
+Security is one of the biggest concern for any cloud solutions. The aim of this project is proactively identify threats and weakness in OpenStack Cloud and contribute to build a secure and robust platform. Threat modelling takes a comprehensive look at the system at hand – components, protocols and code - against the existence and capability of an adversary looking for known vulnerabilities. When a threat is identified, it is tallied and reported to the development team. In some cases, the threat analysis team may also include a suggestion to fix the vulnerabilities and related threat. A simplified view of threat modelling steps are provided below:
 <gallery widths=550px heights=400px>
 File:Threat_Modeling_steps.png
@@ Line 8: / Line 7: @@
 ===== Threat Modelling Process for OpenStack Projects =====
 [https://github.com/shohel02/OpenStack_Threat_Modelling/blob/master/Threat_modeling_process.pdf Threat Modelling process]

← Older revision		Revision as of 21:32, 24 April 2014
Line 27:		Line 27:

	===== Nova: =====		===== Nova: =====
		+
		+	Includes a High Level Threat Model Analysis for Nova.
		+	This is WIP, documentation is still in DRAFT version.
		+
		+	https://github.com/criscad/OpenStack_Threat_Modelling.git

	=== Meeting ===		=== Meeting ===

@@ Line 8: / Line 8: @@
 ===== Threat Modelling Process for OpenStack Projects =====
-[[File:Threat_modeling_process.pdf|thumbnail|Threat Modelling Process]]
 == Resources ==