Skip to content

Commit 98955e8

Browse files
authored
Merge pull request #2454 from MicrosoftDocs/main
Published main to live, Wednesday 10:30 AM PST, 01/15
2 parents 37b7eaa + 402a654 commit 98955e8

File tree

6 files changed

+24
-14
lines changed

6 files changed

+24
-14
lines changed

defender-endpoint/manage-alerts.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: conceptual
1515
ms.subservice: edr
1616
search.appverid: met150
17-
ms.date: 12/18/2020
17+
ms.date: 01/15/2025
1818
---
1919

2020
# Manage Microsoft Defender for Endpoint alerts
@@ -38,6 +38,7 @@ Selecting an alert in either of those places brings up the **Alert management pa
3838
:::image type="content" source="media/atp-alerts-selected.png" alt-text="The Alert management pane and the Alerts queue" lightbox="media/atp-alerts-selected.png":::
3939

4040
Watch this video to learn how to use the new Microsoft Defender for Endpoint alert page.
41+
4142
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=8a9c08a6-558c-47a8-a336-d748acbdaa80]
4243
4344
## Link to another incident
@@ -99,6 +100,9 @@ Create custom rules to control when alerts are suppressed, or resolved. You can
99100

100101
6. Click **Save**.
101102

103+
> [!NOTE]
104+
> Alert suppression is not compatible for custom detections. Make sure to fine-tune your custom detections to avoid [false positives](/defender-endpoint/defender-endpoint-false-positives-negatives).
105+
102106
#### View the list of suppression rules
103107

104108
1. In the navigation pane, select **Settings** \> **Endpoints** \> **Rules** \> **Alert suppression**.

defender-endpoint/run-analyzer-linux.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,8 @@ The XMDE Client Analyzer tool can be downloaded as a [binary](https://go.microso
4444

4545
Download and extract the XMDE Client Analyzer. You can use either the binary or Python version, as follows:
4646

47-
- [Binary version of the Client Analyzer](/defender-endpoint/run-analyzer-macos-linux)
48-
- [Python version of the Client Analyzer](/defender-endpoint/run-analyzer-macos-linux)
47+
- [Binary version of the Client Analyzer](run-analyzer-linux.md#run-the-binary-version-of-the-client-analyzer)
48+
- [Python version of the Client Analyzer](run-analyzer-linux.md#run-the-python-based-client-analyzer)
4949

5050
Due to the limited commands available in live response, the steps detailed must be executed in a bash script. By splitting the installation and execution portion of these commands, it's possible to run the install script once, and run the execution script multiple times.
5151

@@ -54,7 +54,7 @@ Due to the limited commands available in live response, the steps detailed must
5454
5555
#### Binary client analyzer install script
5656

57-
The following script performs the first six steps of the [Running the Binary version of the Client Analyzer](/defender-endpoint/run-analyzer-macos-linux). When complete, the XMDE Client Analyzer binary is available from the `/tmp/XMDEClientAnalyzerBinary/ClientAnalyzer` directory.
57+
The following script performs the first six steps of the [Running the Binary version of the Client Analyzer](run-analyzer-linux.md#details). When complete, the XMDE Client Analyzer binary is available from the `/tmp/XMDEClientAnalyzerBinary/ClientAnalyzer` directory.
5858

5959
1. Create a bash file `InstallXMDEClientAnalyzer.sh` and paste the following content into it.
6060

@@ -80,7 +80,7 @@ The following script performs the first six steps of the [Running the Binary ver
8080

8181
#### Python client analyzer install script
8282

83-
The following script performs the first six steps of the [Running the Python version of the Client Analyzer](/defender-endpoint/run-analyzer-macos-linux). When complete, the XMDE Client Analyzer Python scripts are available from the `/tmp/XMDEClientAnalyzer` directory.
83+
The following script performs the first six steps of the [Running the Python version of the Client Analyzer](run-analyzer-linux.md#run-the-python-based-client-analyzer). When complete, the XMDE Client Analyzer Python scripts are available from the `/tmp/XMDEClientAnalyzer` directory.
8484

8585
1. Create a bash file `InstallXMDEClientAnalyzer.sh` and paste the following content into it.
8686

defender-endpoint/supported-capabilities-by-platform.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The following table gives information about the supported Microsoft Defender for
3636
|---|:---:|:---:|:---:|:---:|
3737
|**Prevention**|||||
3838
|[Attack Surface Reduction](attack-surface-reduction.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
39-
|Device Control|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|
39+
|[Device Control](device-control-overview.md)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|
4040
|[Firewall](host-firewall-reporting.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
4141
|[Network Protection](network-protection.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <sup>[2]</sup>|
4242
|[Next-generation protection](next-generation-protection.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
@@ -50,7 +50,7 @@ The following table gives information about the supported Microsoft Defender for
5050
|[EDR Block](edr-in-block-mode.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
5151
|[Passive Mode](microsoft-defender-antivirus-compatibility.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
5252
|Sense detection sensor|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
53-
|Endpoint & network device discovery|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <sup>[5]</sup>|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
53+
|[Endpoint & network device discovery](device-discovery.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <sup>[5]</sup>|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
5454
|[Vulnerability management](/defender-vulnerability-management/defender-vulnerability-management)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <sup>[6]</sup>|
5555
||||||
5656
|**Response** | | | ||

defender-office-365/mdo-sec-ops-guide.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,10 @@ Incident queue management and the responsible personas are described in the foll
7171

7272
### Manage false positive and false negative detections
7373

74+
> [!TIP]
75+
> - For a quick overview on how to manage false positives, check out this short video: <https://youtu.be/yuduVj6wvsw>
76+
> - For a quick overview on how to get started with false negative investigations, check out this short video: <https://youtu.be/sFMAI8MeDKQ>
77+
7478
In Defender for Office 365, you manage false positives (good mail marked as bad) and false negatives (bad mail allowed) in the following locations:
7579

7680
- The [Submissions page (admin submissions)](submissions-admin.md).
@@ -133,6 +137,9 @@ Campaign Views reveals malware and phishing attacks against your organization. F
133137

134138
## Ad-hoc activities
135139

140+
> [!TIP]
141+
> For a quick overview on how to investigate email messages in Microsoft Defender for Office 365, check out this short video: <https://youtu.be/5hA7VfaMvqs>.
142+
136143
### Manual investigation and removal of email
137144

138145
|Activity|Cadence|Description|Persona|

exposure-management/microsoft-security-exposure-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Security Exposure Management is aimed at:
2424
- Security and compliance admins responsible for maintaining and improving organizational security posture.
2525
- Security operations (SecOps) and partner teams who need visibility into data and workloads across organizational silos to effectively detect, investigate, and mitigate security threats.
2626
- Security architects responsible for solving systematic issues in overall security posture.
27-
- Chief Security Information Officers (CISOs) and security decision makers who need insights into organizational attack surfaces and exposure in order to understand security risk within organizational risk frameworks.
27+
- Chief Information Security Officers (CISOs) and security decision makers who need insights into organizational attack surfaces and exposure in order to understand security risk within organizational risk frameworks.
2828

2929
## What can I do with Security Exposure Management?
3030

exposure-management/security-recommendations.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,17 +26,16 @@ This article describes how to work with security recommendations in [Microsoft S
2626

2727
1. Sort the recommendations by any of the headings or filter them based on your task needs. Sorting includes all of the headers:
2828
- **Name** - Name.
29-
- **Compliance state** - Compliant or not compliant.
29+
- **State** - Compliant or not compliant.
3030
- **Impact** - High, low, or medium impact.
31+
- **Workload** - Which workload the recommendations relate to.
32+
- **Domain** - Device, apps, data, or identity.
3133
- **Last calculated** - Last time the recommendation was calculated.
3234
- **Last state change** - Last time the recommendation state changed.
3335
- **Related initiatives** - The number of related initiatives.
3436
- **Related metrics** - The number of related metrics.
35-
- **Source** - The assessment standard source.
36-
- **Workload** - Which workload the recommendations relate to.
37-
- **Domain** - Device, apps, data, or identity.
38-
39-
1. Filter recommendations by state, source, impact, workload, and domain.
37+
38+
1. Filter recommendations by state, impact, workload, and domain.
4039

4140
1. Select a recommendation to view and review details.
4241

0 commit comments

Comments
 (0)