You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/evaluate-exploit-protection.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
- tier2
16
16
- mde-asr
17
17
search.appverid: met150
18
-
ms.date: 11/21/2024
18
+
ms.date: 02/03/2025
19
19
---
20
20
21
21
# Evaluate exploit protection
@@ -89,6 +89,8 @@ For Adobe Reader use the following ASR rule:
89
89
90
90
• [Block Adobe Reader from creating child processes](attack-surface-reduction-rules-reference.md#block-adobe-reader-from-creating-child-processes)
91
91
92
+
[Google Chrome ](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/security/faq.md#Can-I-use-EMET-to-help-protect-Chrome-against-attack-on-Microsoft-Windows)no longer recommends enabling Exploit Protection (EMET) because it's redundant or superseded with built-in attack mitigations.
93
+
92
94
## Application compatibility list
93
95
94
96
The following table lists specific products that have compatibility issues with the mitigations that are included in exploit protection. You must disable specific incompatible mitigations if you want to protect the product by using exploit protection. Be aware that this list takes into consideration the default settings for the latest versions of the product. Compatibility issues can introduced when you apply certain add-ins or other components to the standard software.
@@ -102,7 +104,7 @@ The following table lists specific products that have compatibility issues with
102
104
| Certain AMD (ATI) video drivers | System ASLR=AlwaysOn |
103
105
| DropBox | EAF |
104
106
| Excel Power Query, Power View, Power Map and PowerPivot | EAF |
105
-
| Google Chrome | EAF+ |
107
+
| Google Chrome ([no longer recommended](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/security/faq.md#Can-I-use-EMET-to-help-protect-Chrome-against-attack-on-Microsoft-Windows))| EAF+ |
106
108
| Immidio Flex+ | EAF |
107
109
| Microsoft Office Web Components (OWC) | System DEP=AlwaysOn |
Hardware-enforced stack protection only works on chipsets with support for hardware shadow stacks, Intel's Control-flow Enforcement Technology (CET) or AMD shadow stacks.
441
441
442
+
If you're running applications based on the .Net Framework, hardware-enforced stack protection is compatible with .Net Framework 7 (opt-in), or newer. If you're using an application with an older version (earlier than .Net Framework 7), expect stability issues (crashes or hangs) and/or performance issues (high cpu or memory leaks). These stability issues could also occur when either in audit mode and/or when targeting only compatible modules.
443
+
442
444
### Configuration options
443
445
444
446
**Audit only** - You can enable this mitigation in audit mode in order to measure the potential compatibility impact on an application. Audit events can then be viewed either in the event viewer or using Advanced Hunting in [Defender for Endpoint](/defender-xdr/advanced-hunting-overview).
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-deployment-on-sap.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 01/06/2025
18
+
ms.date: 02/04/2025
19
19
ms.custom:
20
20
- partner-contribution
21
21
---
@@ -262,7 +262,7 @@ sudo mdatp diagnostic create
262
262
263
263
-[Troubleshoot cloud connectivity issues for Microsoft Defender for Endpoint on Linux](linux-support-connectivity.md#run-the-connectivity-test)
264
264
265
-
-[Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md#troubleshoot-performance-issues-using-microsoft-defender-for-endpoint-client-analyzer)
265
+
-[Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md)
Copy file name to clipboardExpand all lines: defender-endpoint/troubleshoot-collect-support-log.md
+1-9Lines changed: 1 addition & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.collection:
14
14
ms.topic: troubleshooting
15
15
ms.subservice: edr
16
16
search.appverid: met150
17
-
ms.date: 11/18/2024
17
+
ms.date: 02/03/2025
18
18
---
19
19
20
20
# Collect support logs in Microsoft Defender for Endpoint using live response
@@ -69,14 +69,6 @@ This article provides instructions on how to run the tool via Live Response on W
69
69
70
70
- The latest preview version of MDEClientAnalyzer can be downloaded here: <https://aka.ms/MDEClientAnalyzerPreview>.
71
71
72
-
- If you can't allow the machine to reach the above URL, then upload `MDEClientAnalyzerPreview.zip` file to the library before running the LiveAnalyzer script:
- For more information on gathering data locally on a machine in case the machine isn't communicating with Microsoft Defender for Endpoint cloud services, or doesn't appear in Microsoft Defender for Endpoint portal as expected, see [Verify client connectivity to Microsoft Defender for Endpoint service URLs](verify-connectivity.md).
81
73
82
74
- As described in [Live response command examples](live-response-command-examples.md), you might want to use the `&` symbol at the end of the command to collect logs as a background action:
| - | Fixed inaccuracy in BeyondTrust Remote Support | 22-Jan-25 |
56
56
| 68411 | Fixed inaccurate detections in WebM Project libwebp by excluding razer file path | 22-Jan-25 |
57
57
| 77999 | Defender Vulnerability Management doesn't currently support these four ESET vulnerabilities: <br/>- CVE-2020-11446<br/>- CVE-2023-5594<br/>- CVE-2023-3160<br/>- CVE-2024-7400 | 22-Jan-25 |
58
-
58
+
| - | Updated existing normalization rule for Adobe Acrobat Reader to detect raw names with 'neopackage'| 22-Jan-25 |
59
+
| 70377 | Fixed incorrect detections in Microsoft Teams by excluding incorrect Raw Product Names Vida | 22-Jan-25 |
60
+
| 74420 | Fixed incorrect detections in Toggl Track by excluding incorrect Raw Product Names WeChat | 22-Jan-25 |
61
+
| 75694 | Fixed incorrect detections in McAfee by excluding incorrect Raw Product Names Drive Encryption | 22-Jan-25 |
62
+
| 71402 | Fixed incorrect detections in Smoothwall by excluding incorrect Raw Product Names Smoothwall Unified Client | 22-Jan-25 |
63
+
| 76607 | Fixed inaccuracy in Dell BeyondCompare by excluding incorrect Raw Product Names Scooter Software | 22-Jan-25 |
64
+
| - | Added normalization rule for Microsoft Visual Studio 2015 to improve detection logic | 22-Jan-25 |
65
+
| 79328 | Fixed incorrect detections in Microsoft Monitoring Agent by excluding incorrect Raw Product Names MDOP MBAM | 22-Jan-25 |
66
+
| 83419 | Added Microsoft Defender Vulnerability Management support to Sinclair MakeMeAdmin | 22-Jan-25 |
67
+
| 84540 | Fixed incorrect detections in Apple Xcode by excluding incorrect Raw Product Names ProtoPie and RocketSim | 22-Jan-25 |
68
+
| - | Fixed incorrect detections in Apache Tomcat by excluding incorrect Raw Product Names Commons Logging | 22-Jan-25 |
69
+
| 61679 | Defender Vulnerability Management doesn't currently support ESRI portal for Arcgis | 22-Jan-25 |
70
+
| - | Defender Vulnerability Management doesn't currently support Citrix Virtual Apps & Desktops | 22-Jan-25 |
59
71
60
72
## November 2024
61
73
@@ -72,8 +84,6 @@ The following tables present the relevant vulnerability information organized by
72
84
| Inaccuracy report ID | Description | Fix date |
73
85
|---|---|---|
74
86
| - | Fixed inaccuracy in Microsoft LibDB & NSS vulnerabilities | 03-Oct-24 |
75
-
| 70377 | Fixed incorrect detections in Microsoft Teams by excluding Vida from the Teams normalization rule | 09-Oct-24 |
76
-
| 74420 | Fixed incorrect detections in Toggl Track by excluding WeChat from the Toggl Track normalization rule | 09-Oct-24 |
Copy file name to clipboardExpand all lines: defender-xdr/incident-queue.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ms.topic: conceptual
18
18
search.appverid:
19
19
- MOE150
20
20
- MET150
21
-
ms.date: 01/10/2025
21
+
ms.date: 01/27/2025
22
22
appliesto:
23
23
- Microsoft Defender XDR
24
24
- Microsoft Sentinel in the Microsoft Defender portal
@@ -107,7 +107,7 @@ The **Filters** list above the list of incidents shows the currently applied fil
107
107
108
108
From the default incident queue, you can select **Add filter** to see the **Add filter** drop-down, from which you specify filters to apply to the incidents queue to limit the set of incidents shown. Here's an example.
109
109
110
-
:::image type="content" source="/defender/media/incidents-queue/fig1-newfilters.png" alt-text="The Filters pane for the incident queue in the Microsoft Defender portal.":::
110
+
:::image type="content" source="/defender/media/incidents-queue/incidents-all-filters.png" alt-text="The Filters pane for the incident queue in the Microsoft Defender portal.":::
111
111
112
112
Select the filters you want to use, then select **Add** at the bottom of the list to make them available.
113
113
@@ -134,8 +134,9 @@ This table lists the filter names that are available.
134
134
|**Classification**| Specify the set of classifications of the related alerts. |
135
135
|**Automated investigation state**| Specify the status of automated investigation. |
136
136
|**Associated threat**| Specify a named threat. |
137
-
|**Alert policies**| Specify an alert policy title. |
138
-
|**Alert subscription IDs**| Specify an alert based on a subscription ID. |
137
+
|**Policy/policy rule**| Filter incidents based on policy or policy rule. |
138
+
|**Product names**| Filter incidents based on product name. |
139
+
|**Data stream**| Filter incidents based on the location or workload. |
139
140
140
141
> [!NOTE]
141
142
> If you have provisioned access to Microsoft Purview Insider Risk Management, you can view and manage insider risk management alerts and hunt for insider risk management events in the Microsoft Defender portal. For more information, see [Investigate insider risk threats in the Microsoft Defender portal](irm-investigate-alerts-defender.md).
> This article describes security alerts in Microsoft Defender XDR. However, you can use activity alerts to send email notifications to yourself or other admins when users perform specific activities in Microsoft 365. For more information, see [Create activity alerts - Microsoft Purview | Microsoft Docs](/Microsoft-365/compliance/create-activity-alerts).
34
32
@@ -38,15 +36,15 @@ In Microsoft Defender XDR, related alerts are aggregated together to form [incid
38
36
39
37
The **Alerts queue** shows the current set of alerts. You get to the alerts queue from **Incidents & alerts > Alerts** on the quick launch of the [Microsoft Defender portal](https://go.microsoft.com/fwlink/p/?linkid=2077139).
40
38
41
-
:::image type="content" source="/defender/media/investigate-alerts/alerts-ss-alerts-queue.png" alt-text="The Alerts section in the Microsoft Defender portal" lightbox="/defender/media/investigate-alerts/alerts-ss-alerts-queue.png":::
39
+
:::image type="content" source="/defender/media/investigate-alerts/alerts-page-defender-small.png" alt-text="The Alerts section in the Microsoft Defender portal" lightbox="/defender/media/investigate-alerts/alerts-page-defender.png":::
42
40
43
41
Alerts from different Microsoft security solutions like Microsoft Defender for Endpoint, Defender for Office 365, Microsoft Sentinel, Defender for Cloud, Defender for Identity, Defender for Cloud Apps, Defender XDR, App Governance, Microsoft Entra ID Protection, and Microsoft Data Loss Prevention appear here.
44
42
45
43
By default, the alerts queue in the Microsoft Defender portal displays the new and in progress alerts from the last seven days. The most recent alert is at the top of the list so you can see it first.
46
44
47
-
From the default alerts queue, you can select **Filter** to see a **Filter** pane, from which you can specify a subset of the alerts. Here's an example.
45
+
From the default alerts queue, you can select **Filter** to see all available filters from which you can specify a subset of the alerts. Here's an example.
48
46
49
-
:::image type="content" source="/defender/media/investigate-alerts/alerts-ss-alerts-filter.png" alt-text="The Filters section in the Microsoft Defender portal." lightbox="/defender/media/investigate-alerts/alerts-ss-alerts-filter.png":::
47
+
:::image type="content" source="/defender/media/investigate-alerts/alerts-all-filters.png" alt-text="All the filters available in the Alerts queue in the Microsoft Defender portal":::
50
48
51
49
You can filter alerts according to these criteria:
52
50
@@ -55,10 +53,12 @@ You can filter alerts according to these criteria:
55
53
- Categories
56
54
- Service/detection sources
57
55
- Tags
58
-
- Policy
56
+
- Policy/Policy rule
57
+
- Alert type
58
+
- Product name
59
59
- Entities (the impacted assets)
60
60
- Automated investigation state
61
-
-Alert subscription IDs
61
+
-Data stream (workload or location)
62
62
63
63
> [!NOTE]
64
64
> Microsoft Defender XDR customers can now filter incidents with alerts where a compromised device communicated with operational technology (OT) devices connected to the enterprise network through the [device discovery integration of Microsoft Defender for IoT and Microsoft Defender for Endpoint](/defender-endpoint/device-discovery#device-discovery-integration). To filter these incidents, select **Any** in the Service/detection sources, then select **Microsoft Defender for IoT** in the Product name or see [Investigate incidents and alerts in Microsoft Defender for IoT in the Defender portal](/defender-for-iot/investigate-threats/). You can also use device groups to filter for site-specific alerts. For more information about Defender for IoT prerequisites, see [Get started with enterprise IoT monitoring in Microsoft Defender XDR](/azure/defender-for-iot/organizations/eiot-defender-for-endpoint/).
@@ -73,6 +73,17 @@ An alert can have system tags and/or custom tags with certain color backgrounds.
73
73
> [!TIP]
74
74
> Microsoft's Security Exposure Management, based on predefined classifications, automatically tags devices, identities, and cloud resources as a **critical asset**. This out-of-the-box capability ensures the protection of an organization's valuable and most important assets. It also helps security operations teams to prioritize investigation and remediation. Know more about [critical asset management](/security-exposure-management/critical-asset-management).
75
75
76
+
> [!IMPORTANT]
77
+
> Some information in this article relates to a prereleased product, which may be substantially modified before it’s commercially released. Microsoft makes no warranties expressed or implied, with respect to the information provided here.
78
+
79
+
You can search for alerts using a custom date and time range or by using the search bar to search for specific alerts. To search for alerts within a specific date or time range, select **Custom range** in the date picker and then specify the start and end dates and times.
80
+
81
+
:::image type="content" source="/defender/media/investigate-alerts/alerts-custom-range.png" alt-text="Highlighting the custom range option in the date and time picker in the Alerts queue.":::
82
+
83
+
To search for specific alerts, enter the search term in the search bar. You can search for alerts based on the alert title or alert ID.
84
+
85
+
:::image type="content" source="/defender/media/investigate-alerts/alerts-search-bar-small.png" alt-text="Highlighting the search bar in the Alerts queue" lightbox="/defender/media/investigate-alerts/alerts-search-bar.png":::
86
+
76
87
## Required roles for Defender for Office 365 alerts
77
88
78
89
You'll need to have any of the following roles to access Microsoft Defender for Office 365 alerts:
Copy file name to clipboardExpand all lines: defender-xdr/prerequisites.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.topic: conceptual
16
16
search.appverid:
17
17
- MOE150
18
18
- MET150
19
-
ms.date: 07/18/2024
19
+
ms.date: 02/04/2025
20
20
appliesto:
21
21
- Microsoft Defender XDR
22
22
---
@@ -31,7 +31,7 @@ Learn about licensing and other requirements for provisioning and using [Microso
31
31
32
32
Microsoft Defender XDR natively correlates Microsoft security products' signals, providing security operations teams a single pane of glass to detect, investigate, respond, and protect your assets. These signals are dependent on the license that you have and the access provisioned to you.
33
33
34
-
Any of the these licenses gives you access to Microsoft Defender XDR features via the Microsoft Defender portal without additional cost:
34
+
Any of these licenses give you access to Microsoft Defender XDR features via the Microsoft Defender portal without any additional cost:
35
35
36
36
- Microsoft 365 E5 or A5
37
37
- Microsoft 365 E3 with the Microsoft 365 E5 Security add-on
0 commit comments