Skip to content

Commit 3df89ae

Browse files
committed
updated mitigations
1 parent cb6e682 commit 3df89ae

File tree

2 files changed

+5
-8
lines changed

2 files changed

+5
-8
lines changed

defender-endpoint/threat-analytics-analyst-reports.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -108,11 +108,9 @@ Microsoft Sentinel has powerful hunting search and query tools to hunt for secur
108108

109109
## Apply additional mitigations
110110

111-
Threat analytics dynamically tracks the [status of security updates](threat-analytics.md#endpoints-exposure-know-the-deployment-status-of-security-updates) and [secure configurations](threat-analytics.md#recommended-actions-review-list-of-mitigations-and-the-status-of-your-devices). These types of information are available as charts and tables in the **Endpoints exposures** and **Recommended actions** tabs.
111+
Threat analytics dynamically tracks the status of certain [security updates](threat-analytics.md#endpoints-exposure-know-the-deployment-status-of-security-updates) and [secure configurations](threat-analytics.md#recommended-actions-review-list-of-mitigations-and-the-status-of-your-devices). These types of information are available as charts and tables in the **Endpoints exposures** and **Recommended actions** tabs, and are repeatable recommendations that apply to this threat and might apply to other threats, too.
112112

113-
In addition to these tracked recommendations, the analyst report could also discuss mitigations that are *not* dynamically monitored because they’re specific to just the threat or situation being discussed in the report. [Microsoft Secure Score](/defender-xdr/microsoft-secure-score) and [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management) are looking at incorporating recommendations that are repeatable and applicable to the most customers.
114-
115-
Here are some examples of important mitigations that aren’t dynamically tracked:
113+
In addition to these tracked recommendations, the analyst report could also discuss mitigations that are *not* dynamically monitored because they’re specific to just the threat or situation being discussed in the report. Here are some examples of important mitigations that aren’t dynamically tracked:
116114

117115
- Block emails with _.lnk_ attachments or other suspicious file types
118116
- Randomize local administrator passwords

defender-xdr/threat-analytics-analyst-reports.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -110,11 +110,9 @@ Microsoft Sentinel has powerful hunting search and query tools to hunt for secur
110110

111111
## Apply additional mitigations
112112

113-
Threat analytics dynamically tracks the [status of security updates](threat-analytics.md#endpoints-exposure-know-the-deployment-status-of-security-updates) and [secure configurations](threat-analytics.md#recommended-actions-review-list-of-mitigations-and-the-status-of-your-devices). These types of information are available as charts and tables in the **Endpoints exposures** and **Recommended actions** tabs.
113+
Threat analytics dynamically tracks the status of certain [security updates](threat-analytics.md#endpoints-exposure-know-the-deployment-status-of-security-updates) and [secure configurations](threat-analytics.md#recommended-actions-review-list-of-mitigations-and-the-status-of-your-devices). These types of information are available as charts and tables in the **Endpoints exposures** and **Recommended actions** tabs, and are repeatable recommendations that apply to this threat and might apply to other threats, too.
114114

115-
In addition to these tracked recommendations, the analyst report could also discuss mitigations that are *not* dynamically monitored because they’re specific to just the threat or situation being discussed in the report. [Microsoft Secure Score](microsoft-secure-score.md) and [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management) are looking at incorporating recommendations that are repeatable and applicable to the most customers.
116-
117-
Here are some examples of important mitigations that aren’t dynamically tracked:
115+
In addition to these tracked recommendations, the analyst report could also discuss mitigations that are *not* dynamically monitored because they’re specific to just the threat or situation being discussed in the report. Here are some examples of important mitigations that aren’t dynamically tracked:
118116

119117
- Block emails with _.lnk_ attachments or other suspicious file types
120118
- Randomize local administrator passwords
@@ -128,4 +126,5 @@ While you can use the **Endpoints exposures** and **Recommended actions** tabs t
128126
- [Threat analytics overview](threat-analytics.md)
129127
- [Proactively find threats with advanced hunting](advanced-hunting-overview.md)
130128
- [Custom detection rules](custom-detection-rules.md)
129+
131130
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

0 commit comments

Comments
 (0)