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 Threat Model Project"

From OWASP
Jump to: navigation, search
m (added roadmap)
(another batch of initial updates)
Line 6: Line 6:
 
{| 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;" |
 
| 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
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, 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, and project leaders should ensure that the description is meaningful.
 
−
</span>
 
−
 
 
−
Inevitably applications are designed with security principles architects knew about, security folks included. However, as this project demonstrates there are far more than just a 'few' principles, most of which never make it into the design.
 
−
 
 
−
For example, security design happens with perhaps a handful of principles:
 
−
 
 
−
* Least Privilege
 
−
* Perimeter Security
 
−
* Defence in Depth
 
−
 
 
−
However, we regularly see designs without '''separation of privilege'''!
 
  
−
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:
 +
# We are vendor, methodology and tool independent: we strive to have examples in as many methodologies and/or tools as possible
 +
# 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
  
 
==Description==
 
==Description==
Line 34: Line 24:
 
</span>
 
</span>
  
−
To be the source of all information threat model related including but not limited to cheat sheets, examples, new techniques and processes
+
.
−
 
 
−
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]'''
 
−
 
 
−
Over the course of my career, I have come across and collected a number of security ''aphorisms.'' These aphorisms constitute the fundamental principles of information security.
 
−
 
 
−
None of the ideas or truths are mine, and unfortunately, I did not collect the citations. Initially, I would like to identify the correct citations for each aphorism.
 
−
 
 
−
Additionally, many are re-statements of the same idea; thus, the 'collection of ideas' defines a fundamental principle. As such, I would also like to reverse engineer the principles from the aphorisms where appropriate, as well.
 
  
 
==Licensing==
 
==Licensing==
Line 60: Line 42:
 
</span>
 
</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.
+
.
−
 
 
−
This document should serve as a guide to technical architects and designers outlining the fundamental principles of security.
 
  
 
== Presentation ==
 
== 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 - 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
 
* 2017 - 12: Add all content from summit, contributor list and examples

Revision as of 16:29, 6 November 2017

OWASP Project Header.jpg

The OWASP Threat Model Project

--description

Guiding principles:

This project follows a number of principles that all contributions must adhere to:

  1. We are vendor, methodology and tool independent: we strive to have examples in as many methodologies and/or tools as possible
  2. 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.
  3. 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

Description

This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible.

.

Licensing

All information in this project is free to use. In fact it 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.

What is OWASP Security Principles Project?

Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important?

.

Presentation

None

Project Leader

Related Projects

Openhub

Quick Download

None

News and Events

  • [10 Nov 2017] Public release of the project

In Print

None

Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Threat_Model_Project&oldid=235098"