OWASP Cyber Defense Matrix

=Main=



{| 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
An in-depth breakdown of security capabilities using the Cyber Defense Matrix. - A mapping of security vendors to the Cyber Defense Matrix. - Metrics that capture the efficacy, longevity, and other qualities of the various capabilities represented in the Cyber Defense Matrix - Assorted use cases for the Cyber Defense Matrix 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
 * Defense 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
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
The OWASP Security Principles 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.


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is OWASP Security Principles Project?
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
RSA Slides

Project Leader

 * Sounil Yu
 * Tom Brennan

Related Projects

 * OWASP_CISO_Survey

Openhub

 * OWASP Project Openhub


 * valign="top" style="padding-left:25px;width:200px;" |

MAILING LIST

 * CLICK TO JOIN

News and Events

 * [01 May 2017] Project updated
 * [26 June 2017] Update

Classifications

 * }

=FAQs=

Coming Soon..

How can I participate in your project?
Join the mailing list, say hello!

If I am not a programmer can I participate in your project?
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =

Contributors
Everyone is invited to collaborate on this project. = Road Map and Getting Involved = April 5th 2017 project announced publicly at the OWASP NYC Chapter Meeting call for DATA is OPEN

June 2017 - Project Submitted and Approved by OWASP Foundation, page online

July 2017 - Planning for BlackHat/Defcon Face to Face Meet-Up

Aug 2017 - 

Sept 2017 - AppSecUSA Project Summit

=Project About=