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/behavior-monitor-macos.md
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,12 @@
1
1
---
2
-
# Required metadata
3
-
# For more information, see https://review.learn.microsoft.com/en-us/help/platform/learn-editor-add-metadata?branch=main
4
-
# For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main
5
-
6
2
title: Behavior Monitoring in Microsoft Defender Antivirus on macOS
7
3
description: Behavior Monitoring in Microsoft Defender Antivirus on macOS
8
-
author: YongRhee-MSFT # GitHub alias
9
-
ms.author: yongrhee # Microsoft alias
4
+
author: YongRhee-MSFT # GitHub alias
5
+
ms.author: yongrhee # Microsoft alias
10
6
manager: deniseb
11
7
ms.service: defender-endpoint
12
8
ms.topic: overview
13
-
ms.date: 05/08/2024
9
+
ms.date: 05/29/2024
14
10
ms.subservice: ngp
15
11
audience: ITPro
16
12
ms.collection:
@@ -139,11 +135,17 @@ The following sections describe each of these methods in detail.
139
135
```
140
136
141
137
2. Open **Devices** > **Configuration profiles**.
138
+
142
139
3. Select **Create profile** and select **New Policy**.
140
+
143
141
4. Give the profile a name. Change **Platform=macOS** to **Profile type=Templates** and choose **Custom** in the template name section. Select **Configure**.
144
-
5. Go to the plist file you saved earlier and save it as com.microsoft.wdav.xml.
142
+
143
+
5. Go to the plist file you saved earlier and save it as `com.microsoft.wdav.xml`.
144
+
145
145
6. Enter `com.microsoft.wdav` as the **custom configuration profile name**.
146
+
146
147
7. Open the configuration profile and upload the `com.microsoft.wdav.xml` file and select **OK**.
148
+
147
149
8. Select **Manage** > **Assignments**. In the **Include** tab, select **Assign to All Users & All devices or to a Device Group or User Group.**
148
150
149
151
#### Via JamF deployment
@@ -163,7 +165,7 @@ The following sections describe each of these methods in detail.
For more information, see: [Resources for Microsoft Defender for Endpoint on macOS](/defender-endpoint/mac-resources).
205
207
208
+
### To test behavior monitoring (prevention/block) detection
209
+
210
+
See [Behavior Monitoring demonstration](demonstration-behavior-monitoring.md).
206
211
207
212
### Verifying Behavior Monitoring detection
208
213
@@ -211,11 +216,11 @@ The existing Microsoft Defender for Endpoint on macOS command line interface can
211
216
```bash
212
217
sudo mdatp threat list
213
218
```
214
-
For more information on how to test for a behavior monitoring (prevention/block) detection, see [Behavior Monitoring demonstration](demonstration-behavior-monitoring.md).
215
-
216
219
### Frequently Asked Questions (FAQ):
217
220
218
221
#### What if I see an increase in cpu utilization or memory utilization?
222
+
219
223
Disable Behavior Monitoring and see if the issue goes away.
224
+
220
225
- If the issue doesn't go away, it is not related to Behavior Monitoring.
221
226
- If the issue goes away, take an aka.ms/xMDEClientAnalyzer and contact Microsoft support.
Copy file name to clipboardExpand all lines: defender-endpoint/mac-support-perf.md
+26-26Lines changed: 26 additions & 26 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: conceptual
15
15
ms.subservice: macos
16
16
search.appverid: met150
17
-
ms.date: 03/20/2024
17
+
ms.date: 05/29/2024
18
18
---
19
19
20
20
# Troubleshoot performance issues for Microsoft Defender for Endpoint on macOS
@@ -27,7 +27,6 @@ ms.date: 03/20/2024
27
27
-[Microsoft Defender for Endpoint Plan 1 and Plan 2](microsoft-defender-endpoint.md)
28
28
-[Microsoft Defender for Individuals](https://www.microsoft.com/microsoft-365/microsoft-defender-for-individuals)
29
29
30
-
31
30
> Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-exposedapis-abovefoldlink)
32
31
33
32
This article provides some general steps that can be used to narrow down performance issues related to Defender for Endpoint on macOS.
@@ -41,7 +40,7 @@ Depending on the applications that you're running and your device characteristic
41
40
42
41
**Applies to:**
43
42
44
-
- Only performance issues related to Microsoft Defender Antivirus (`wdavdaemon_unpriviliged`).
43
+
- Only performance issues related to Microsoft Defender Antivirus (`wdavdaemon_unprivileged`).
45
44
46
45
Real-time protection (RTP) is a feature of Defender for Endpoint on macOS that continuously monitors and protects your device against threats. It consists of file and process monitoring and other heuristics.
47
46
@@ -50,7 +49,10 @@ Prerequisites:
50
49
- Microsoft Defender for Endpoint version (Platform Update) 100.90.70 or newer
51
50
- If you have [Tamper protection](tamperprotection-macos.md) turned on in block mode, use [Troubleshooting mode](mac-troubleshoot-mode.md) to capture real-time-protection-statistics. Otherwise, you will get null results.
52
51
53
-
To troubleshoot and mitigate such issues, follow these steps:
52
+
> [!TIP]
53
+
> As a general best practice, it is recommended to update the [Microsoft Defender for Endpoint agent to latest available version](linux-whatsnew.md) and confirming that the issue still persists before investigating further.
54
+
55
+
To troubleshoot and mitigate performance issues, follow these steps:
54
56
55
57
1. Disable real-time protection by using one of the methods in the following table, and then observe whether performance improves. This approach helps narrow down whether Microsoft Defender for Endpoint on macOS is contributing to the performance issues.
56
58
@@ -59,51 +61,53 @@ To troubleshoot and mitigate such issues, follow these steps:
59
61
| Device isn't managed by organization |**User interface**: Open Microsoft Defender for Endpoint on macOS and navigate to **Manage settings**. |
60
62
| Device isn't managed by organization |**Terminal**: In Terminal, run the following command: `mdatp config real-time-protection --value disabled`|
61
63
| Device is managed by organization | See [Set preferences for Microsoft Defender for Endpoint on macOS](mac-preferences.md). |
62
-
64
+
63
65
If the performance problem persists while real-time protection is off, the origin of the problem could be the endpoint detection and response component. In this case, contact customer support for further instructions and mitigation.
64
-
66
+
65
67
2. Open Finder and navigate to **Applications** > **Utilities**. Open **Activity Monitor** and analyze which applications are using the resources on your system. Typical examples include software updaters and compilers.
66
68
67
69
3. This feature requires real-time protection to be enabled. To check the status of real-time protection, run the following command:
68
70
69
71
```bash
70
72
mdatp health --field real_time_protection_enabled
71
73
```
72
-
74
+
73
75
Verify that the **real_time_protection_enabled** entry is *true*. Otherwise, run the following command to enable it:
74
-
76
+
75
77
```bash
76
78
mdatp config real-time-protection --value enabled
77
79
```
78
-
80
+
79
81
```output
80
82
Configuration property updated
81
83
```
82
-
83
-
4. To find the applications that are triggering the most scans, you can use real-time statistics gathered by Defender for Endpoint on macOS. Run the following command:
84
+
85
+
4. To find the applications that are triggering the most scans, you can use real-time statistics gathered by Defender for Endpoint on macOS. Run the following command to enable it:
> Before proceeding to capture the data, make sure that the high cpu utilization is occurring in the wdavdaemon_unprivileged by either running top or opening `activity monitor`.
88
93
89
-
This feature requires real-time protection to be enabled. To check the status of real-time protection, run the following command:
94
+
5. To output to a json file, run the following command:
> Using `--output json` (note the double dash) ensures that the output format is ready for parsing. The output of this command will show all processes and their associated scan activity.
102
+
6. On your Mac system, download the sample Python parser `high_cpu_parser.py` using the command:
97
103
98
-
5. On your Mac system, download the sample Python parser `high_cpu_parser.py` using the command:
@@ -115,7 +119,7 @@ To troubleshoot and mitigate such issues, follow these steps:
115
119
0s
116
120
```
117
121
118
-
6. Type the following commands:
122
+
7. Type the following commands:
119
123
120
124
```bash
121
125
chmod +x high_cpu_parser.py
@@ -141,12 +145,12 @@ To troubleshoot and mitigate such issues, follow these steps:
141
145
125 CrashPlanService 164
142
146
```
143
147
144
-
7. To improve the performance of Defender for Endpoint on Mac, locate the one with the highest number under the **Total files scanned** row, and then add an exclusion for it. For more information, see [Configure and validate exclusions for Defender for Endpoint on macOS](mac-exclusions.md).
148
+
8. To improve the performance of Defender for Endpoint on Mac, locate the one with the highest number under the **Total files scanned** row, and then add an exclusion for it. For more information, see [Configure and validate exclusions for Defender for Endpoint on macOS](mac-exclusions.md).
145
149
146
150
> [!NOTE]
147
151
> The application stores statistics in memory and only keeps track of file activity since it was started and real-time protection was enabled. Processes that were launched before or during periods when real time protection was off are not counted. Additionally, only events which triggered scans are counted.
148
152
149
-
7. Configure Microsoft Defender for Endpoint on macOS with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection.
153
+
9. Configure Microsoft Defender for Endpoint on macOS with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection.
150
154
151
155
See [Configure and validate exclusions for Microsoft Defender for Endpoint on macOS](mac-exclusions.md).
152
156
@@ -157,8 +161,4 @@ The Microsoft Defender for Endpoint Client Analyzer (MDECA) can collect traces,
157
161
To run the client analyzer for troubleshooting performance issues, see [Run the client analyzer on macOS and Linux](run-analyzer-macos-linux.md).
158
162
159
163
> [!NOTE]
160
-
>
161
-
> - The Microsoft Defender for Endpoint Client Analyzer tool is regularly used by Microsoft Customer Support Services (CSS) to collect information such as (but not limited to) IP addresses, PC names that will help troubleshoot issues you may be experiencing with Microsoft Defender for Endpoint. For more information about our privacy statement, see [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
162
-
> - As a general best practice, it is recommended to update the [Microsoft Defender for Endpoint agent to latest available version](linux-whatsnew.md) and confirming that the issue still persists before investigating further.
163
-
164
-
164
+
> The Microsoft Defender for Endpoint Client Analyzer tool is regularly used by Microsoft Customer Support Services (CSS) to collect information such as (but not limited to) IP addresses, PC names that will help troubleshoot issues you may be experiencing with Microsoft Defender for Endpoint. For more information about our privacy statement, see [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
-**Tag**: Select **All** or the specified user tag (including Priority account). For more information, see [User tags](user-tags-about.md).
94
+
-**Tag**: Leave the value **All** or remove it, double-click in the empty box, and then select **Priority account**. For more information about user tags, see [User tags](user-tags-about.md).
95
95
96
96
When you're finished configuring the filters, select **Apply**, **Cancel**, or :::image type="icon" source="media/m365-cc-sc-clear-filters-icon.png" border="false"::: **Clear filters**.
97
97
@@ -992,7 +992,7 @@ For each chart, the details table below the chart shows the following informatio
992
992
Select :::image type="icon" source="media/m365-cc-sc-filter-icon.png" border="false"::: **Filter** to modify the report by selecting one or more of the following values in the flyout that opens:
993
993
994
994
-**Date (UTC)****Start date** and **End date**
995
-
-**Tag**: Select **All** or the specified user tag (including Priority account). For more information, see [User tags](user-tags-about.md).
995
+
-**Tag**: Leave the value **All** or remove it, double-click in the empty box, and then select **Priority account**. For more information about user tags, see [User tags](user-tags-about.md).
996
996
997
997
When you're finished configuring the filters, select **Apply**, **Cancel**, or :::image type="icon" source="media/m365-cc-sc-clear-filters-icon.png" border="false"::: **Clear filters**.
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-microsoft-defender.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,13 +112,16 @@ For editable queries, more options are available:
112
112
113
113
To help discover threats and anomalous behaviors in your environment, you can create custom detection policies.
114
114
115
-
For analytics rules that apply to data ingested through the connected Microsoft Sentinel workspace, select **Manage rules > Create analytics rule**.
115
+
For analytics rules that apply to data ingested through the connected Microsoft Sentinel workspace, select **Manage rules > Create analytics rule**.
116
116
117
117
:::image type="content" source="/defender/media/advanced-hunting-unified-rules.png" alt-text="Screenshot of the options to create custom analytics or detections in the Microsoft Defender portal" lightbox="/defender/media/advanced-hunting-unified-rules.png":::
118
118
119
119
The **Analytics rule wizard** appears. Fill up the required details as described in [Analytics rule wizard—General tab](/azure/sentinel/detect-threats-custom#analytics-rule-wizardgeneral-tab).
120
120
121
-
For custom detection rules that apply to Microsoft Defender XDR data, select **Manage rules > Create custom detection**. Read [Create and manage custom detection rules](custom-detection-rules.md) for more information.
121
+
You can also create custom detection rules that query data from both Microsoft Sentinel and Defender XDR tables. Select **Manage rules > Create custom detection**. Read [Create and manage custom detection rules](custom-detection-rules.md) for more information.
122
+
123
+
If your Defender XDR data is ingested into Microsoft Sentinel, you have the option to choose between **Create custom detection** and **Create analytics rule**.
124
+
122
125
123
126
## Explore results
124
127
@@ -143,11 +146,14 @@ For Microsoft Defender XDR data, you can take further action by selecting the ch
143
146
144
147
- The `IdentityInfo table` from [Microsoft Sentinel](/azure/sentinel/ueba-reference#identityinfo-table) isn't available, as the `IdentityInfo` table remains as is in Defender XDR. Microsoft Sentinel features like analytics rules that query this table aren't impacted as they're querying the Log Analytics workspace directly.
145
148
- The Microsoft Sentinel `SecurityAlert` table is replaced by `AlertInfo` and `AlertEvidence` tables, which both contain all the data on alerts. While SecurityAlert isn't available in the schema tab, you can still use it in queries using the advanced hunting editor. This provision is made so as not to break existing queries from Microsoft Sentinel that use this table.
146
-
- Guided hunting mode is supported for Defender XDR data only.
147
-
- Custom detections, links to incidents, and take actions capabilities are supported for Defender XDR data only.
149
+
- Guided hunting mode, links to incidents, and take actions capabilities are supported for Defender XDR data only.
150
+
- Custom detections have the following limitations:
151
+
- Custom detections are not available for KQL queries that do not include Defender XDR data.
152
+
- Near real-time detection frequency is not available for detections that include Microsoft Sentinel data.
153
+
- Custom functions that were created and saved in Microsoft Sentinel are not supported.
154
+
- Defining entities from Sentinel data is not yet supported in custom detections.
148
155
- Bookmarks aren't supported in the advanced hunting experience. They're supported in the **Microsoft Sentinel > Threat management > Hunting** feature.
149
156
- If you're streaming Defender XDR tables to Log Analytics, there might be a difference between the`Timestamp` and `TimeGenerated` columns. In case the data arrives to Log Analytics after 48 hours, it's being overridden upon ingestion to `now()`. Therefore, to get the actual time the event happened, we recommend relying on the `Timestamp` column.
150
-
- The Microsoft Graph API for running an advanced hunting query doesn't support querying data from Microsoft Sentinel yet.
151
157
- When prompting [Copilot for Security](advanced-hunting-security-copilot.md) for advanced hunting queries, you might find that not all Microsoft Sentinel tables are currently supported. However, support for these tables can be expected in the future.
For more information, see [remediation actions](m365d-remediation-actions.md) in Microsoft Defender XDR.
73
73
74
-
### Automated response actions for SAP with Microsoft Sentinel (Preview)
74
+
### Automated response actions for SAP with Microsoft Sentinel
75
75
76
76
If you're using the [unified security operations platform](microsoft-sentinel-onboard.md) and you deployed the Microsoft Sentinel solution for SAP applications, you can also deploy automatic attack disruption for SAP.
0 commit comments