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 Cyber Defense Matrix"

From OWASP
Jump to: navigation, search
(→‎The OWASP Security Principles)
m (→‎Project Leader: Removed defunct mailing lists. Replaced links to point to LinkedIn page that people can follow instead for updates.)
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
=Main=
+
= Main =
 +
{{#widget:PayPal Donation
 +
|target=_blank
 +
|budget=OWASP_Cyber_Defense_Matrix
 +
}} 
 +
 
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
 
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
−
 
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
{| 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;" |
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
==Introduction to the Cyber Defense Matrix==
−
<span style="color:#ff0000">
+
Imagine going into a grocery store to shop for Thanksgiving dinner, but instead of seeing nice, orderly aisles, you see a massive pile of food in the middle of the grocery store. Finding the ingredients that you need to make dinner is going to be extremely hard because there’s no organizational system helping you understand where things are. The disorganization makes it very difficult to find what you need and compare competing products.
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
−
</span>
 
  
−
==The OWASP Security Principles==
+
The cybersecurity vendor marketplace is like this disorganized grocery store. A proof of this assertion can be seen by looking at the vendor hall at any major security conference. The cacophony of sounds from vendors hawking their wares, the confusing language of the vendor’s marketecture, and the lack of any semblance of organization (aside from biggest to smallest) does not help buyers understand what they need or where to find it.
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
Because the cybersecurity community does not use consistent terminology to describe what we need, there is much confusion about what many vendor products actually do. Instead of a clear articulation of a product's capabilities, we are bombarded with overused, trendy jargon that usually leaves us wondering if the product can really solve any of our woes. Some organizations even organize themselves according to the jargon. We need to stop letting marketing pitches dictate our terminology and not lose sight of the more bland descriptors that actually tell us what something does.
−
<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>
 
−
- 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:
+
The Cyber Defense Matrix helps us understand what we need organized through a logical construct so that when we go into the security vendor marketplace, we can quickly discern what products solve what problems and be informed on what is the core function of a given product. In addition, the Cyber Defense Matrix provides a mechanism to ensure that we have capabilities across the entire spectrum of options to help secure our environments.
  
−
* Least Privilege
+
Although the Cyber Defense Matrix was initially created to help organize security technologies, many other use cases have been discovered to help build, manage, and operate a security program. This project intends to capture these use cases and their implementations to help security practitioners mature their security programs.
−
* Perimeter Security
 
−
* Defence in Depth
 
  
−
However, we regularly see designs without '''separation of privilege'''!
+
==Structure of the Cyber Defense Matrix==
  
−
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 basic construct of the Cyber Defense Matrix starts with two dimensions. The first dimension captures the five operational functions of the NIST Cybersecurity Framework:
−
 
+
{| class="wikitable"
−
The aim of this project, is to identify and describe a minimum functional set of principles that must be present in a secure design.
+
!IDENTIFY
−
 
+
!PROTECT
−
==Description==
+
!DETECT
−
 
+
!RESPOND
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
!RECOVER
−
<span style="color:#ff0000">
+
|}
−
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.
+
The second dimension captures five assets classes that we try to secure:
−
</span>
+
{| class="wikitable"
−
 
+
!DEVICES
−
'''Although this is a sample template, the project is real! [http://owasp.github.io/Security-Principles Please contribute to this project.]
+
|-
−
'''
+
!APPLICATIONS
−
 
+
|-
−
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.
+
!NETWORKS
−
 
+
|-
−
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.
+
!DATA
−
 
+
|-
−
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.
+
!USERS
−
 
+
|}
−
==Licensing==
+
When these two dimensions are put into a grid, we arrive at with a five-by-five matrix that we call the “Cyber Defense Matrix.”
 +
<div style="width:100%;border:0,margin:0;">[[File:Cyber Defense Matrix.png|center]]</div>
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
There is one more important piece of this matrix.  At bottom of the grid, we show a continuum that characterizes the degree of dependency on technology, people, and process as we progress through the five operational functions of the NIST Cybersecurity Framework.  TECHNOLOGY plays a much greater role in IDENTIFY and PROTECT. As we move to DETECT, RESPOND, and RECOVER, our dependency on TECHNOLOGY diminishes and our dependency on PEOPLE grows. Throughout all five operational functions, there's a consistent level of dependency on PROCESS. This continuum helps us understand where we might have imbalances in our reliance on PEOPLE, PROCESS, and TECHNOLOGY when trying to tackle our cybersecurity challenges.
−
<span style="color:#ff0000">
 
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.
 
−
</span>
 
  
−
'''The OWASP Security Principles are free to use. In fact it is encouraged!!!
+
We believe that this matrix is a realistic model describes a broad range of cybersecurity practices. In this website, you will find several insights on the Cyber Defense Matrix and examples of how to leverage it to address the challenges that we face in cybersecurity.
−
'' Additionally, I also encourage you to contribute back to the project. I 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 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.
+
If you discover a new use of the Cyber Defense Matrix, we would love to hear about it. Likewise, if you find a problem with the matrix in that it doesn't seem to properly describe something that we do in cybersecurity, please point that out, and we'll either adjust the matrix or clarify how that perceived discrepancy can be addressed or explained through the matrix.
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- 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;" |
+
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
−
 
 
−
== What is OWASP Security Principles Project? ==
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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?
 
−
</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.
+
== Presentations and Other Media ==
  
−
== Presentation ==
+
[https://bit.ly/cyberdefensematrix Cyber Defense Matrix Presentation at RSA Conference 2016]
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
[https://bit.ly/cyberdefensematrixreloaded Cyber Defense Matrix Reloaded Presentation at RSA Conference 2019]
−
<span style="color:#ff0000">
 
−
This is where you can link to slide presentations related to your project.
 
−
</span>
 
−
 
 
−
 
 
−
AppSec USA 2013 [https://github.com/OWASP/Security-Principles/tree/master/Presentations/AppSec%20NYC%202013]
 
  
 
== Project Leader ==
 
== Project Leader ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [https://twitter.com/sounilyu Sounil Yu (@sounilyu)]
−
<span style="color:#ff0000">
 
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
−
</span>
 
  
−
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+
== FAQs ==
 +
* TBD
  
 +
== Things To Do ==
 +
* Document structure of the Cyber Defense Matrix
 +
* Map vendors to the Cyber Defense Matrix
 +
* Map NIST NICE NCWF skillsets to the Cyber Defense Matrix
 +
* Define attributes that can support measurement of efficacy of capability
 +
* Define Design Patterns and Business Constraints aligned against the Cyber Defense Matrix
 +
* Capture anecdotal and empirical measurements of capability degradation rates
 +
* Incorporate and document new use cases as they are discovered
  
 
== Related Projects ==
 
== Related Projects ==
 +
* TBD
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
== Licensing ==
−
<span style="color:#ff0000">
+
The Cyber Defense Matrix, originally created by Sounil Yu, is licensed under the http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.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.
−
This is where you can link to other OWASP Projects that are similar to yours.  
 
−
</span>
 
−
 
 
−
* [[OWASP_CISO_Survey]]
 
−
 
 
−
== Openhub ==
 
−
 
 
−
* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
 
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
−
| valign="top" style="padding-left:25px;width:200px;" |
+
| valign="top" style="padding-left:25px;width:200px;" |
−
 
 
−
== Quick Download ==
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you can link to your repository.
 
−
</span>
 
−
 
 
−
The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.
 
  
−
However, if you like you may also download the master repository from the following links:
+
== MAILING LIST ==
−
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
+
* [https://www.linkedin.com/company/cyber-defense-matrix/ CLICK TO JOIN]
−
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
 
  
 
== News and Events ==
 
== News and Events ==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
* [01 May 2017] Project created
−
<span style="color:#ff0000">
+
* [20 April 2019] Added links to 2019 briefing at RSA
−
This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project.
 
−
</span>
 
−
 
 
−
* [20 Nov 2013] News 2
 
−
* [30 Sep 2013] News 1
 
−
 
 
−
== In Print ==
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
This is where you place links to where your project product can be downloaded or purchased, in the case of a book.
 
−
</span>
 
−
 
 
−
This project can be purchased as a print on demand book from Lulu.com
 
  
 
==Classifications==
 
==Classifications==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
{| width="200" cellpadding="2"
−
<span style="color:#ff0000">
 
−
Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running.
 
−
</span>
 
−
 
 
−
  {| width="200" cellpadding="2"
 
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
+
   | rowspan="2" align="center" valign="top" width="50%" | [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
−
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]   
+
   | align="center" valign="top" width="50%" | [[File:Owasp-builders-small.png|link=]]   
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
+
   | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]  
+
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]  
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]   
+
   | colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]   
 
   |}
 
   |}
  
 
|}
 
|}
  
−
=FAQs=
+
= FAQs =
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
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.'
 
−
</span>
 
−
 
 
−
 
 
−
==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.
 
−
 
 
−
==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==
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
 
−
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
 
−
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
−
</span>
 
−
 
 
−
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
 
−
 
 
−
The first contributors to the project were:
 
−
 
 
−
* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
 
−
* [https://github.com/sublimino Andrew Martin]
 
−
* [https://github.com/Lambdanaut Josh Thomas]
 
−
* '''YOUR NAME BELONGS HERE'''
 
−
 
 
−
= Road Map and Getting Involved =
 
−
 
 
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
−
<span style="color:#ff0000">
 
−
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
 
−
</span> 
 
−
 
 
−
<span style="color:#ff0000">
 
−
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
 
−
</span>
 
−
 
 
−
As of October 2013, the priorities are:
 
−
* Finish the referencing for each principle.
 
−
* Update the Project Template.
 
−
* Use the OWASP Press to develop a book.
 
−
* Finish and publish the book on Lulu.
 
−
 
 
−
Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!
 
−
You do not have to be a security expert in order to contribute.
 
−
Some of the ways you can help:
 
−
* Helping find references to some of the principles.
 
−
* Project administration support.
 
−
* Wiki editing support.
 
−
* Writing support for the book.
 
−
 
 
−
=Project About=
 
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
== How can I participate in your project? ==
−
<span style="color:#ff0000">
+
Everyone is invited to collaborate on this project. Contact the Project Leaders. The project needs different skills and expertise and different times during its development. Currently, we are looking for help in the following areas:
−
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
 
−
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
−
</span>
 
  
−
{{:Projects/OWASP_Example_Project_About_Page}}
+
* Documenting new use cases
 +
* Creating a system to capture everything that is mapped to the Cyber Defense Matrix. This includes:
 +
** Mapping of vendors
 +
** Mapping of NIST NICE NCWF skillsets
 +
** Mapping of measurements and metrics
  
 +
= Events and Opportunities to Get Involved =
  
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
 
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
−
__NOTOC__ <headertabs />  
+
__NOTOC__ <headertabs></headertabs>  
  
−
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]   
 +
[[Category:OWASP_Builders]]  
 +
[[Category:OWASP_Defenders]]   
 +
[[Category:OWASP_Document]]

Latest revision as of 02:48, 11 October 2019

OWASP Project Header.jpg

Introduction to the Cyber Defense Matrix

Imagine going into a grocery store to shop for Thanksgiving dinner, but instead of seeing nice, orderly aisles, you see a massive pile of food in the middle of the grocery store. Finding the ingredients that you need to make dinner is going to be extremely hard because there’s no organizational system helping you understand where things are. The disorganization makes it very difficult to find what you need and compare competing products.

The cybersecurity vendor marketplace is like this disorganized grocery store. A proof of this assertion can be seen by looking at the vendor hall at any major security conference. The cacophony of sounds from vendors hawking their wares, the confusing language of the vendor’s marketecture, and the lack of any semblance of organization (aside from biggest to smallest) does not help buyers understand what they need or where to find it.

Because the cybersecurity community does not use consistent terminology to describe what we need, there is much confusion about what many vendor products actually do. Instead of a clear articulation of a product's capabilities, we are bombarded with overused, trendy jargon that usually leaves us wondering if the product can really solve any of our woes. Some organizations even organize themselves according to the jargon. We need to stop letting marketing pitches dictate our terminology and not lose sight of the more bland descriptors that actually tell us what something does.

The Cyber Defense Matrix helps us understand what we need organized through a logical construct so that when we go into the security vendor marketplace, we can quickly discern what products solve what problems and be informed on what is the core function of a given product. In addition, the Cyber Defense Matrix provides a mechanism to ensure that we have capabilities across the entire spectrum of options to help secure our environments.

Although the Cyber Defense Matrix was initially created to help organize security technologies, many other use cases have been discovered to help build, manage, and operate a security program. This project intends to capture these use cases and their implementations to help security practitioners mature their security programs.

Structure of the Cyber Defense Matrix

The basic construct of the Cyber Defense Matrix starts with two dimensions. The first dimension captures the five operational functions of the NIST Cybersecurity Framework:

IDENTIFY PROTECT DETECT RESPOND RECOVER

The second dimension captures five assets classes that we try to secure:

DEVICES
APPLICATIONS
NETWORKS
DATA
USERS

When these two dimensions are put into a grid, we arrive at with a five-by-five matrix that we call the “Cyber Defense Matrix.”

Cyber Defense Matrix.png

There is one more important piece of this matrix.  At bottom of the grid, we show a continuum that characterizes the degree of dependency on technology, people, and process as we progress through the five operational functions of the NIST Cybersecurity Framework.  TECHNOLOGY plays a much greater role in IDENTIFY and PROTECT. As we move to DETECT, RESPOND, and RECOVER, our dependency on TECHNOLOGY diminishes and our dependency on PEOPLE grows. Throughout all five operational functions, there's a consistent level of dependency on PROCESS. This continuum helps us understand where we might have imbalances in our reliance on PEOPLE, PROCESS, and TECHNOLOGY when trying to tackle our cybersecurity challenges.

We believe that this matrix is a realistic model describes a broad range of cybersecurity practices. In this website, you will find several insights on the Cyber Defense Matrix and examples of how to leverage it to address the challenges that we face in cybersecurity.

If you discover a new use of the Cyber Defense Matrix, we would love to hear about it. Likewise, if you find a problem with the matrix in that it doesn't seem to properly describe something that we do in cybersecurity, please point that out, and we'll either adjust the matrix or clarify how that perceived discrepancy can be addressed or explained through the matrix.

Presentations and Other Media

Cyber Defense Matrix Presentation at RSA Conference 2016

Cyber Defense Matrix Reloaded Presentation at RSA Conference 2019

Project Leader

FAQs

  • TBD

Things To Do

  • Document structure of the Cyber Defense Matrix
  • Map vendors to the Cyber Defense Matrix
  • Map NIST NICE NCWF skillsets to the Cyber Defense Matrix
  • Define attributes that can support measurement of efficacy of capability
  • Define Design Patterns and Business Constraints aligned against the Cyber Defense Matrix
  • Capture anecdotal and empirical measurements of capability degradation rates
  • Incorporate and document new use cases as they are discovered

Related Projects

  • TBD

Licensing

The Cyber Defense Matrix, originally created by Sounil Yu, is licensed under the http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.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.

MAILING LIST

News and Events

  • [01 May 2017] Project created
  • [20 April 2019] Added links to 2019 briefing at RSA

Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

How can I participate in your project?

Everyone is invited to collaborate on this project. Contact the Project Leaders. The project needs different skills and expertise and different times during its development. Currently, we are looking for help in the following areas:

  • Documenting new use cases
  • Creating a system to capture everything that is mapped to the Cyber Defense Matrix. This includes:
    • Mapping of vendors
    • Mapping of NIST NICE NCWF skillsets
    • Mapping of measurements and metrics
Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Cyber_Defense_Matrix&oldid=255403"