OWASP Threat Model Project - Revision history

Swierckx: correcting subscription link

2018-12-04T18:27:44Z

correcting subscription link

Swierckx: updated contact information

2017-11-07T08:11:49Z

updated contact information

Swierckx: removed unwanted sections

2017-11-06T16:54:08Z

removed unwanted sections

Swierckx: better description

2017-11-06T16:52:35Z

better description

Adamshostack: a few nits

2017-11-06T16:48:08Z

a few nits

Swierckx: removed unwanted sections

2017-11-06T16:41:59Z

removed unwanted sections

Swierckx: more content

2017-11-06T16:37:21Z

Swierckx: another batch of initial updates

2017-11-06T16:29:14Z

another batch of initial updates

Swierckx: added roadmap

2017-11-06T16:19:26Z

added roadmap

Swierckx: added Avi as project leader

2017-11-06T15:49:16Z

added Avi as project leader

@@ Line 55: / Line 55: @@
 https://owasp.slack.com/messages/C1CS3C6AF
-If you are not yet a member of the OWASP Slack community, you can subscribe at https://owasp.herokuapp.com/
+If you are not yet a member of the OWASP Slack community, you can subscribe at https://owaspslack.com/
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->

@@ Line 50: / Line 50: @@
 * [[OWASP Cloud Security Project]]
-== Openhub ==
+== Contact Us ==
-* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
+https://owasp.slack.com/messages/C1CS3C6AF
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
@@ Line 87: / Line 90: @@
 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.
 The best way to achieve this is to join the OWASP threat modeling slack channel at https://owasp.slack.com/messages/C1CS3C6AF
 ==If I am not a threat modeler can I participate in your project?==

@@ Line 26: / Line 26: @@
 # Open discussion is promoted: all topics are open for discussion with just one rule: don't be a dick. If you feel information is lacking or missing, let us know via the OWASP Threat Model slack channel.
 # We come to an agreement: we discuss things mainly in google docs and on slack, if the project leaders feel a concensus is made, we will publish the content to our main website. All published content can be changed by submitting change requests on the Github repository that serves the website
 ==Licensing==

@@ Line 8: / Line 8: @@
 ==The OWASP Threat Model Project==
-This is a documentation project. We aim to centralise any and all information on threat modeling in this project.
+This is a documentation project. We provide information on threat modeling techniques for web and cloud, with a focus on current and emerging techniques.
 Most threat model methodologies answer one or more of the following questions:

@@ Line 10: / Line 10: @@
 This is a documentation project. We aim to centralise any and all information on threat modeling in this project.
-All threat model methodologies answer one or more of the following questions:
+Most threat model methodologies answer one or more of the following questions:
 # What are we building?
 # What can go wrong?
@@ Line 16: / Line 16: @@
 # Did we do a good enough job?
-This project will gather techniques, methodologies, tools and examples. We will assign one or more categories to these reflecting the four questions. This will allow people to easily find back information they are interested in.
+This project will gather techniques, methodologies, tools and examples. We will group these using the four questions. This will allow people to easily find advice they can use.
 Example: if you are looking for different diagramming techniques you will want to look for all the techniques answering question 1.

@@ Line 37: / Line 37: @@
 ==Licensing==
-'''All information in this project is free to use. In fact it is encouraged!!!'''
+'''All information in this project is free to use. In fact sharing is encouraged!!!'''
-'' Additionally, we also encourage you to contribute back to the project. We have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together.''
 The OWASP Threat Model Project information are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ 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.
@@ Line 44: / Line 45: @@
 <!-- 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;" |
 == Presentation ==

@@ Line 8: / Line 8: @@
 ==The OWASP Threat Model Project==
---description
+This is a documentation project. We aim to centralise any and all information on threat modeling in this project.
 '''Guiding principles:'''
@@ Line 110: / Line 120: @@
 = Road Map =
-* 2017 - 11: Release website with info that was agreed upon, add links to google docs for all open content
+* 2017 - 11: Release website with info that was agreed upon during the OWASP 2017 Summit in London, add links to google docs for all open content
 * 2017 - 12: Add all content from summit, contributor list and examples
 * 2018 - 01: Add contributor list, finish cheat sheets

@@ Line 6: / Line 6: @@
 {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
-==The OWASP Security Principles==
+==The OWASP Threat Model Project==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+--description
-Think about that, most web applications today have all their eggs in a single basket. The business logic, the identities, passwords, products, policy enforcement, security rules are all found in the same application database that makes up the typical website! It is little wonder then, that attacks on the database have been so completely devastating, since there is no separation of privilege!
+'''Guiding principles:'''
-The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.
+This project follows a number of principles that all contributions must adhere to:
 ==Description==
@@ Line 34: / Line 24: @@
 </span>
-To be the source of all information threat model related including but not limited to cheat sheets, examples, new techniques and processes
 ==Licensing==
@@ Line 60: / Line 42: @@
 </span>
-The end goal is to identify, cite, and document the fundamental principles of information security. Once this is well organised, I think it would be great to publish this through the [http://scriptogr.am/dennis-groves/post/owasp-press OWASP Press]. Of course, it will always remain freely available, and any money collected will go directly into the project to absorb costs with any remaining funds going to the OWASP Foundation.
 == Presentation ==
@@ Line 129: / Line 109: @@
+*
-= Road Map and Getting Involved =
+= Road Map =
 * 2017 - 11: Release website with info that was agreed upon, add links to google docs for all open content
 * 2017 - 12: Add all content from summit, contributor list and examples

@@ Line 111: / Line 111: @@
 =FAQs=
 ==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.
@@ Line 137: / Line 130: @@
 = Road Map and Getting Involved =
-* September: create website, October: add all cheat sheets / complete structure, November: add contributor list, history and examples, December: add all content from summit
+* 2017 - 11: Release website with info that was agreed upon, add links to google docs for all open content
-* Project links (if any) to external sites, While waiting for the project we have started the following discussions that will be start of the content provided: <nowiki>https://docs.google.com/document/d/1gaUnmmXc4pcmgeWytKKfEDazVEX9xfk22roz_aoryeA/edit</nowiki> and <nowiki>https://docs.google.com/document/d/1dV1xmKluj2repYujj9CeOZC0jmJ4az-r5JyJG7erVQc/edit</nowiki> Also content created during the OWASP Summit of 2017: <nowiki>https://owaspsummit.org/Working-Sessions/Threat-Model/index.html</nowiki>
+* 2017 - 12: Add all content from summit, contributor list and examples
+* 2018 - 01: Add contributor list, finish cheat sheets
+* 2018 - 02: Finish agile TM implementation suggestions for SCRUM and Kanban, start TM history
-<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
+* 2018 - 03: Start TM resources for tools, articles and books
 __NOTOC__ <headertabs></headertabs>

← Older revision		Revision as of 15:49, 6 November 2017
Line 71:		Line 71:

	* [mailto:steven.wierckx@owasp.org Steven Wierckx]		* [mailto:steven.wierckx@owasp.org Steven Wierckx]
		+	* [mailto:avi.douglen@owasp.org Avi Douglen]
	== Related Projects ==		== Related Projects ==