Skip to content

Commit

Permalink
Update dm.rst
Browse files Browse the repository at this point in the history
Feedback Updates
  • Loading branch information
blackwidow0616 authored Feb 13, 2024
1 parent f69093f commit 45e5ae2
Showing 1 changed file with 17 additions and 9 deletions.
26 changes: 17 additions & 9 deletions docs/components/dm.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,23 +2,25 @@
Defensive Measures
==================

This section outlines the key components that have been identified for the Defensive Measures dimension as well as maturity levels within the components. These components and
levels form the basis for assessing how threat informed an organization’s Defensive program is. This assessment can be conducted using the companion spreadsheet published with
this white paper.
This section outlines the key components that have been identified for the Defensive Measures dimension as well as maturity levels within the components. These components and levels form the basis for assessing how threat informed an organization’s Defensive program is. This assessment can be conducted using the companion spreadsheet published with this white paper.

Foundational Security [#f1]_
----------------------------

1. None
2. Ad Hoc patching, limited asset inventory, basic security measures
3. Routine, automated patching, full asset inventory, cyber hygiene best-practices implemented [#f2]_
4. Prioritized [#f3]_ automated patching [#f4]_ , full asset inventory mapped to business operations and threats, hygiene best-practices implemented
5. Threat-prioritized design and maintenance of all aspects of cybersecurity
The degree to which threat informs and prioritizes preventative security measures.

1. None
2. Ad Hoc patching, limited asset inventory, basic security measures
3. Several mitigations and security controls [#f2]_ connected to relevant threats implemented, key attack surfaces and critical assets identified
4. Knowledge of threat informs a risk management process to prioritize a set of mitigations and controls
5. Prioritized [#f3]_ automated patching [#f4]_, attack surfaces understood, full asset inventory mapped to business operations and threats, hygiene best-practices implemented


Data Collection
----------------

Is the right data being collected based on the needs identified from analysis of threat intelligence?

1. None
2. Minimal visibility (e.g., single network sensor at network boundary)
3. Compliant with best practices for network and devices (e.g., logs collected from each device according to the manufacturer’s recommendations)
Expand All @@ -29,6 +31,8 @@ Data Collection
Detection Engineering
------------------------

How much are detection analytics designed, tested, and tuned to optimize precision, recall, and robustness for relevant malicious behaviors?

1. None
2. Import rules / analytics from open repository
3. Prioritize and tune imported rules / analytics from repository
Expand All @@ -39,16 +43,20 @@ Detection Engineering
Incident Response
------------------

How automated, strategic, and effective are responsive measures against top-priority threats?

1. None
2. Ad Hoc, Manual, Reactive
3. Playbook-enabled, partially automated
4. Informed by knowledge of threat actor (e.g., initial detection leads to follow-on investigation to detect other malicious actions expected in the campaign based on CTI)
4. Informed by knowledge of threat actor (e.g., initial detection leads to follow-on investigation to detect other malicious actions expected in the campaign based on CTI) Proactive hunts are conducted driven by threat information rather than only alerts from existing analytics.
5. Strategic, holistic, optimized to deter future events (e.g., with an understanding of the full campaign and the adversary’s likely reaction to defensive response, the defenders take decisive and coordinated actions that effectively evict the adversary such that it is not easy for them to return)


Deception Operations [#f8]_
---------------------------------

How extensive and effective are deception operations to enable defensive objectives and the collection of new threat intelligence?

1. None
2. Sandboxing of suspicious executables (e.g., email attachment detonation before delivery)
3. 1 to several Honey* (pot, token, document…) deployed and monitored, enabling detection of malicious use and early warning
Expand Down

0 comments on commit 45e5ae2

Please sign in to comment.