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/attack-surface-reduction-rules-reference.md
+6-1Lines changed: 6 additions & 1 deletion
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
- m365-security
16
16
- tier2
17
17
- mde-asr
18
-
ms.date: 11/10/2024
18
+
ms.date: 11/18/2024
19
19
search.appverid: met150
20
20
---
21
21
@@ -330,6 +330,11 @@ By default the state of this rule is set to block. In most cases, many processes
330
330
331
331
Enabling this rule doesn't provide additional protection if you have LSA protection enabled since the ASR rule and LSA protection work similarly. However, when LSA protection cannot be enabled, this rule can be configured to provide equivalent protection against malware that target `lsass.exe`.
332
332
333
+
> [!TIP]
334
+
> 1. ASR audit events don't generate toast notifications. However, since the LSASS ASR rule produces large volume of audit events, almost all of which are safe to ignore when the rule is enabled in block mode, you can choose to skip the audit mode evaluation and proceed to block mode deployment, beginning with a small set of devices and gradually expanding to cover the rest.
335
+
> 2. The rule is designed to suppress block reports/toasts for friendly processes. It is also designed to drop reports for duplicate blocks. As such, the rule is well suited to be enabled in block mode, irrespective of whether toast notifications are enabled or disabled.
336
+
> 3. ASR in warn mode is designed to present users with a block toast notification that includes an "Unblock" button. Due to the "safe to ignore" nature of LSASS ASR blocks and their large volume, WARN mode is not advisable for this rule (irrespective of whether toast notifications are enabled or disabled).
337
+
333
338
> [!NOTE]
334
339
> In this scenario, the ASR rule is classified as "not applicable" in Defender for Endpoint settings in the Microsoft Defender portal.
335
340
> The *Block credential stealing from the Windows local security authority subsystem* ASR rule doesn't support WARN mode.
Copy file name to clipboardExpand all lines: defender-endpoint/mac-whatsnew.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
@@ -6,7 +6,7 @@ author: deniseb
6
6
ms.author: deniseb
7
7
manager: deniseb
8
8
ms.localizationpriority: medium
9
-
ms.date: 10/30/2024
9
+
ms.date: 11/18/2024
10
10
audience: ITPro
11
11
ms.collection:
12
12
- m365-security
@@ -41,7 +41,7 @@ For more information on Microsoft Defender for Endpoint on other operating syste
41
41
42
42
- In macOS Sonoma 14.3.1, Apple made a change to the [handling of Bluetooth devices](https://developer.apple.com/forums/thread/738748) that impacts Defender for Endpoint device control's ability to intercept and block access to Bluetooth devices. At this time, the recommended mitigation is to use a version of macOS earlier than 14.3.1.
43
43
44
-
- In macOS Sequoia (version 15.0), if you have Network Protection enabled, you might see crashes of the network extension (NetExt). This issue results in intermittent network connectivity issues for end users. Please upgrade to macOS Sequoia version 15.0.1 or newer.
44
+
- In macOS Sequoia (version 15.0), if you have Network Protection enabled, you might see crashes of the network extension (NetExt). This issue results in intermittent network connectivity issues for end users. Please upgrade to macOS Sequoia version 15.1 or newer.
Copy file name to clipboardExpand all lines: defender-endpoint/machines-view-overview.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,6 +136,7 @@ The available device properties to use as filters vary based on the device inven
136
136
|**Device subtype**|<ul><li>**All devices**</li><li>**IoT/OT**</li></ul>|The subtype value assigned to the device. Enter a value or select an available value (for example, **Video conference**).|
137
137
|**Device type**|<ul><li>**All devices**</li><li>**IoT/OT**</li></ul>|The type value assigned to the device. Enter a value or select an available value (for example, **Audio and Video**).|
138
138
|**Device value**|All|The assigned value of the device. The available values are **High** and **Low**.|
139
+
|**Discovery sources**|All|The source reporting on the device.|
139
140
|**Exclusion state**|All|The available values are **Not excluded** and **Excluded**. For more information, see [Exclude devices](exclude-devices.md).|
140
141
|**Exposure level**|All|The exposure level of the device based on pending security recommendations. The available values are: <ul><li>**High**</li><li>**Medium**</li><li>**Low**: Devices are less vulnerable to exploitation.</li><li>**No data available**: Possible causes for this value include: <ul><li>The device is inactive (stopped reporting for more than 30 days).</li><li>The OS on the device isn't supported. For more information, see [minimum requirements for Microsoft Defender for Endpoint](minimum-requirements.md).</li><li>The agent software on the device is stale (unlikely).</li></ul></li></ul>|
141
142
|**First seen**|All tabs except **Network devices**|How long ago the device was first seen on the network or when it was first reported by the Microsoft Defender for Endpoint sensor. The available values are **Last 7 days** or **Over 7 days ago**.|
@@ -178,6 +179,7 @@ You can sort the entries by clicking on an available column header. Select :::im
178
179
-**OS version**<sup\*</sup>
179
180
-**Sensor health state**<sup\*</sup>
180
181
-**Onboarding status**<sup\*</sup>
182
+
-**Discovery sources**
181
183
-**First seen**
182
184
-**Last device update**<sup\*</sup>
183
185
-**Tags**<sup\*</sup>
@@ -204,6 +206,7 @@ You can sort the entries by clicking on an available column header. Select :::im
204
206
-**Criticality level**<sup\*</sup>
205
207
-**Sensor health state**<sup\*</sup>
206
208
-**Onboarding status**<sup\*</sup>
209
+
-**Discovery sources**
207
210
-**Last device update**<sup\*</sup>
208
211
-**First seen**
209
212
-**Tags**<sup\*</sup>
@@ -219,6 +222,7 @@ You can sort the entries by clicking on an available column header. Select :::im
219
222
-**Vendor**<sup>\*</sup>
220
223
-**Model**<sup>\*</sup>
221
224
-**Name**<sup>\*</sup>
225
+
-**Discovery sources**
222
226
-**Domain**
223
227
-**Device type**
224
228
-**Device subtype**
@@ -241,6 +245,7 @@ You can sort the entries by clicking on an available column header. Select :::im
241
245
-**Model**<sup>\*</sup>
242
246
-**Risk level**<sup>\*</sup>
243
247
-**Exposure level**<sup>\*</sup>
248
+
-**Discovery sources**
244
249
-**OS distribution**<sup>\*</sup>
245
250
-**OS version**<sup>\*</sup>
246
251
-**First seen**
@@ -253,6 +258,7 @@ You can sort the entries by clicking on an available column header. Select :::im
Copy file name to clipboardExpand all lines: defender-endpoint/troubleshoot-collect-support-log.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
@@ -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/07/2024
17
+
ms.date: 11/18/2024
18
18
---
19
19
20
20
# Collect support logs in Microsoft Defender for Endpoint using live response
@@ -37,7 +37,7 @@ This article provides instructions on how to run the tool via Live Response on W
37
37
- If you require additional logs related to Microsoft Defender Antivirus, then use `..\Tools\MDELiveAnalyzerAV.ps1`.
38
38
- If you require [Microsoft Endpoint Data Loss Prevention](/purview/endpoint-dlp-learn-about) related logs, then use `..\Tools\MDELiveAnalyzerDLP.ps1`.
39
39
- If you require network and [Windows Filter Platform](/windows-hardware/drivers/network/windows-filtering-platform-architecture-overview) related logs, then use `..\Tools\MDELiveAnalyzerNet.ps1`.
40
-
- If you require [Process Monitor](/sysinternals/downloads/procmon) logs, then use `..\Tools\MDELiveAnalyzerDLP.ps1`.
40
+
- If you require [Process Monitor](/sysinternals/downloads/procmon) logs, then use `..\Tools\MDELiveAnalyzerAppCompat.ps1`.
41
41
42
42
2. Initiate a [Live Response session](live-response.md#initiate-a-live-response-session-on-a-device) on the machine you need to investigate.
Copy file name to clipboardExpand all lines: defender-office-365/how-policies-and-protections-are-combined.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,8 @@ There are two major factors that determine which policy is applied to a message:
68
68
69
69
<sup>\*</sup> Defender for Office 365 only.
70
70
71
-
The priority order matters if you have the same recipient intentionally or unintentionally included in multiple policies, because *only* the first policy of that type (anti-spam, anti-malware, anti-phishing, etc.) is applied to that recipient, regardless of how many other policies that the recipient is included in. There's never a merging or combining of the settings in multiple policies for the recipient. The recipient is unaffected by the settings of the remaining policies of that type.
71
+
> [!IMPORTANT]
72
+
> The priority order matters if you have the same recipient intentionally or unintentionally included in multiple policies, because *only* the first policy of that type (anti-spam, anti-malware, anti-phishing, etc.) is applied to that recipient, regardless of how many other policies that the recipient is included in. There's never a merging or combining of the settings in multiple policies for the recipient. The recipient is unaffected by the settings of the remaining policies of that type.
72
73
73
74
For example, the group named "Contoso Executives" is included in the following policies:
For the Microsoft Defender XDR security portal to start enforcing the permissions and assignments configured in your new [custom roles](create-custom-rbac-roles.md) or [imported roles](import-rbac-roles.md), you must activate the Microsoft Defender XDR Unified RBAC model for some or all of your workloads.
34
36
@@ -54,20 +56,19 @@ You can activate your workloads in two ways from the Permissions and roles page:
54
56
:::image type="content" source="/defender/media/defender/m365-defender-rbac-activate-workloads1.png" alt-text="Screenshot of the activate workloads page" lightbox="/defender/media/defender/m365-defender-rbac-activate-workloads1.png":::
55
57
56
58
1.**Activate workloads**
57
-
- Select **Activate workloads** on the banner above the list of roles to go directly to the **Activate workloads** screen.
58
-
- You must activate each workload one by one. Once you select the individual toggle, you activate (or deactivate) that workload.
59
59
60
-
:::image type="content" source="/defender/media/defender/defender-rbac-select-workload.png" alt-text="Screenshot of the choose workloads to activate screen":::
60
+
- Select **Activate workloads** on the banner above the list of roles to go directly to the **Activate workloads** screen.
61
+
- You must activate each workload one by one. Once you select the individual toggle, you activate (or deactivate) that workload.
62
+
63
+
:::image type="content" source="/defender/media/defender/defender-activate-workloads.png" alt-text="Screenshot of the choose workloads to activate screen.":::
61
64
62
65
> [!NOTE]
63
66
> The **Activate workloads** button is only available when there is it at least one workload that's not active for Microsoft Defender XDR Unified RBAC.
64
-
>
65
67
> Microsoft Defender for Cloud is active by default with Microsoft Defender XDR Unified RBAC.
66
-
>
67
-
> Defender XDR Unified RBAC is automatically active for Secure Score access. Once a custom role with one of the permissions is created, it has an immediate impact on assigned users. There is no need to activate it.
68
+
> Defender XDR Unified RBAC is automatically active for Exposure Management access. Once a custom role with one of the Exposure Management permissions is created, it has an immediate impact on assigned users. There is no need to activate it.
68
69
>
69
70
> To activate Exchange Online permissions in Microsoft Defender XDR Unified RBAC, Defender for Office 365 permissions must be active.
70
-
71
+
71
72
2.**Workload settings**
72
73
- Select **Workload settings**.
73
74
- This brings you to the Microsoft Defender XDR **Permission and roles** page.
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-security-copilot.md
+24-15Lines changed: 24 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Microsoft Copilot for Security in advanced hunting
3
-
description: Learn how Microsoft Copilot for Security advanced hunting (NL2KQL) plugin can generate a KQL query for you.
2
+
title: Microsoft Security Copilot in advanced hunting
3
+
description: Learn how Microsoft Security Copilot advanced hunting (NL2KQL) plugin can generate a KQL query for you.
4
4
search.appverid: met150
5
5
ms.service: defender-xdr
6
6
ms.subservice: adv-hunting
@@ -27,22 +27,30 @@ appliesto:
27
27
- Microsoft Sentinel in the Microsoft Defender portal
28
28
---
29
29
30
-
# Microsoft Copilot for Security in advanced hunting
30
+
# Microsoft Security Copilot in advanced hunting
31
31
32
-
[Microsoft Copilot for Security in Microsoft Defender](security-copilot-in-microsoft-365-defender.md) comes with a query assistant capability in advanced hunting.
33
32
34
-
Threat hunters or security analysts who aren't yet familiar with or have yet to learn KQL can make a request or ask a question in natural language (for instance, *Get all alerts involving user admin123*). Copilot for Security then generates a KQL query that corresponds to the request using the advanced hunting data schema.
33
+
**Applies to:**
34
+
35
+
- Microsoft Defender
36
+
- Microsoft Defender XDR
37
+
38
+
## Security Copilot in advanced hunting
39
+
40
+
[Microsoft Security Copilot in Microsoft Defender](security-copilot-in-microsoft-365-defender.md) comes with a query assistant capability in advanced hunting.
41
+
42
+
Threat hunters or security analysts who aren't yet familiar with or have yet to learn KQL can make a request or ask a question in natural language (for instance, *Get all alerts involving user admin123*). Security Copilot then generates a KQL query that corresponds to the request using the advanced hunting data schema.
35
43
36
44
This feature reduces the time it takes to write a hunting query from scratch so that threat hunters and security analysts can focus on hunting and investigating threats.
37
45
38
-
Users with access to Copilot for Security have access to this capability in advanced hunting.
46
+
Users with access to Security Copilot have access to this capability in advanced hunting.
39
47
40
48
> [!NOTE]
41
-
> The advanced hunting capability is also available in the Copilot for Security standalone experience through the Microsoft Defender XDR plugin. Know more about [preinstalled plugins in Copilot for Security](/security-copilot/manage-plugins#preinstalled-plugins).
49
+
> The advanced hunting capability is also available in the Security Copilot standalone experience through the Microsoft Defender XDR plugin. Know more about [preinstalled plugins in Security Copilot](/security-copilot/manage-plugins#preinstalled-plugins).
42
50
43
51
## Try your first request
44
52
45
-
1. Open the **advanced hunting** page from the navigation bar in the Microsoft Defender portal. The Copilot for Security side pane for advanced hunting appears at the right hand side.
53
+
1. Open the **advanced hunting** page from the navigation bar in Microsoft Defender XDR. The Security Copilot side pane for advanced hunting appears at the right hand side.
46
54
47
55
:::image type="content" source="/defender/media/advanced-hunting-security-copilot-pane.png" alt-text="Screenshot of the Copilot pane in advanced hunting." lightbox="/defender/media/advanced-hunting-security-copilot-pane-big.png":::
48
56
@@ -51,11 +59,11 @@ Users with access to Copilot for Security have access to this capability in adva
51
59
52
60
53
61
54
-
:::image type="content" source="/defender/media/advanced-hunting-security-copilot-query.png" alt-text="Screenshot that shows prompt bar in the Copilot for Security for advanced hunting." lightbox="/defender/media/advanced-hunting-security-copilot-query-big.png":::
62
+
:::image type="content" source="/defender/media/advanced-hunting-security-copilot-query.png" alt-text="Screenshot that shows prompt bar in the Security Copilot for advanced hunting." lightbox="/defender/media/advanced-hunting-security-copilot-query-big.png":::
55
63
56
64
1. Copilot generates a KQL query from your text instruction or question. While Copilot is generating, you can cancel the query generation by selecting **Stop generating**.
57
65
58
-

66
+

59
67
60
68
61
69
1. Review the generated query. You can then choose to run the query by selecting **Add and run**.
@@ -66,7 +74,7 @@ Users with access to Copilot for Security have access to this capability in adva
66
74
67
75
If you need to make further tweaks, select **Add to editor**.
68
76
69
-

77
+

70
78
71
79
The generated query appears in the query editor as the last query, where you can edit it before running using the regular **Run query** above the query editor.
72
80
@@ -75,23 +83,24 @@ Users with access to Copilot for Security have access to this capability in adva
75
83
76
84
77
85
> [!TIP]
78
-
> Providing feedback is an important way to let the Copilot for Security team know how well the query assistant was able to help in generating a useful KQL query. Feel free to articulate what could have made the query better, what adjustments you had to make before running the generated KQL query, or share the KQL query that you eventually used.
86
+
> Providing feedback is an important way to let the Security Copilot team know how well the query assistant was able to help in generating a useful KQL query. Feel free to articulate what could have made the query better, what adjustments you had to make before running the generated KQL query, or share the KQL query that you eventually used.
79
87
80
88
81
-
In the [Microsoft Defender portal](advanced-hunting-microsoft-defender.md), you can prompt Copilot for Security to generate advanced hunting queries for both Defender XDR and Microsoft Sentinel tables. Not all Microsoft Sentinel tables are currently supported, but support for these tables can be expected in the future.
89
+
> [!NOTE]
90
+
> In the [unified Microsoft Defender portal](advanced-hunting-microsoft-defender.md), you can prompt Security Copilot to generate advanced hunting queries for both Defender XDR and Microsoft Sentinel tables. Not all Microsoft Sentinel tables are currently supported, but support for these tables can be expected in the future.
82
91
83
92
## Query sessions
84
93
85
94
You can start your first session anytime by asking a question in the Copilot side pane in advanced hunting. Your session contains the requests you made using your user account. Closing the side pane or refreshing the advanced hunting page doesn't discard the session. You can still access the generated queries should you need them.
86
95
87
96
Select the chat bubble icon (**New chat**) to discard the current session.
88
97
89
-

98
+

90
99
91
100
## Modify settings
92
101
93
102
Select the ellipses in the Copilot side pane to choose whether or not to automatically add and run the generated query in advanced hunting.
94
103
95
-

104
+

96
105
97
106
Deselecting the **Run generated query automatically** setting gives you the option of running the generated query automatically (**Add and run**) or adding the generated query to the query editor for further modification (**Add to editor**).
0 commit comments