Skip to content

Commit 66afd1a

Browse files
Merge pull request #530 from YongRhee-MSFT/docs-editor/behavior-monitor-macos-1716573192
Update behavior-monitor-macos.md
2 parents d472f82 + fa5a511 commit 66afd1a

File tree

1 file changed

+16
-11
lines changed

1 file changed

+16
-11
lines changed

defender-endpoint/behavior-monitor-macos.md

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,12 @@
11
---
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-
62
title: Behavior Monitoring in Microsoft Defender Antivirus on macOS
73
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
106
manager: deniseb
117
ms.service: defender-endpoint
128
ms.topic: overview
13-
ms.date: 05/08/2024
9+
ms.date: 05/29/2024
1410
ms.subservice: ngp
1511
audience: ITPro
1612
ms.collection:
@@ -139,11 +135,17 @@ The following sections describe each of these methods in detail.
139135
```
140136

141137
2. Open **Devices** > **Configuration profiles**.
138+
142139
3. Select **Create profile** and select **New Policy**.
140+
143141
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+
145145
6. Enter `com.microsoft.wdav` as the **custom configuration profile name**.
146+
146147
7. Open the configuration profile and upload the `com.microsoft.wdav.xml` file and select **OK**.
148+
147149
8. Select **Manage** > **Assignments**. In the **Include** tab, select **Assign to All Users & All devices or to a Device Group or User Group.**
148150

149151
#### Via JamF deployment
@@ -163,7 +165,7 @@ The following sections describe each of these methods in detail.
163165
<key>features</key>
164166
<dict>
165167
<key>behaviorMonitoring</key>
166-
string>enabled</string>
168+
<string>enabled</string>
167169
<key>behaviorMonitoringConfigurations</key>
168170
<dict>
169171
<key>blockExecution</key>
@@ -203,6 +205,9 @@ sudo mdatp config behavior-monitoring --value disabled
203205

204206
For more information, see: [Resources for Microsoft Defender for Endpoint on macOS](/defender-endpoint/mac-resources).
205207

208+
### To test behavior monitoring (prevention/block) detection
209+
210+
See [Behavior Monitoring demonstration](demonstration-behavior-monitoring.md).
206211

207212
### Verifying Behavior Monitoring detection
208213

@@ -211,11 +216,11 @@ The existing Microsoft Defender for Endpoint on macOS command line interface can
211216
```bash
212217
sudo mdatp threat list
213218
```
214-
For more information on how to test for a behavior monitoring (prevention/block) detection, see [Behavior Monitoring demonstration](demonstration-behavior-monitoring.md).
215-
216219
### Frequently Asked Questions (FAQ):
217220

218221
#### What if I see an increase in cpu utilization or memory utilization?
222+
219223
Disable Behavior Monitoring and see if the issue goes away.
224+
220225
- If the issue doesn't go away, it is not related to Behavior Monitoring.
221226
- If the issue goes away, take an aka.ms/xMDEClientAnalyzer and contact Microsoft support.

0 commit comments

Comments
 (0)