OWASP Threat Model Project

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved

The OWASP Security Principles 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. 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! The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design. 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. 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! 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 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? 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 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 None Project Leader Steven Wierckx Related Projects OWASP Threat Dragon OWASP Cloud Security Project Openhub OWASP Project Openhub

Quick Download None News and Events [10 Nov 2017] Public release of the project In Print None Classifications

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

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.

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?

Yes, you can certainly participate in the project if you are not a threat modeler. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and people who want to learn about threat modeling.

Contributors

The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project contributors is found here.

The first contributors to the project were:

• September: create website, October: add all cheat sheets / complete structure, November: add contributor list, history and examples, December: add all content from summit
• 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: https://docs.google.com/document/d/1gaUnmmXc4pcmgeWytKKfEDazVEX9xfk22roz_aoryeA/edit and https://docs.google.com/document/d/1dV1xmKluj2repYujj9CeOZC0jmJ4az-r5JyJG7erVQc/edit Also content created during the OWASP Summit of 2017: https://owaspsummit.org/Working-Sessions/Threat-Model/index.html