Skip to content

Commit e9899c1

Browse files
authored
Merge pull request #3492 from MicrosoftDocs/main
[AutoPublish] main to live - 04/16 04:28 PDT | 04/16 16:58 IST
2 parents a72c623 + b0ff4ee commit e9899c1

23 files changed

+216
-217
lines changed

defender-endpoint/mac-device-control-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 04/30/2024
18+
ms.date: 04/16/2025
1919
---
2020

2121
# macOS Device Control policies frequently asked questions (FAQ)

defender-endpoint/mac-device-control-jamf.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 02/25/2025
18+
ms.date: 04/16/2025
1919
---
2020

2121
# Deploy and manage Device Control using JAMF
@@ -46,7 +46,7 @@ Before you begin, confirm your subscription. To access and use device control, y
4646

4747
### Step 1: Creating a JSON policy
4848

49-
Device Control on Mac is defined through a JSON policy. This policy should have the appropriate groups, rules, and settings defined to tailor specific customer conditions. For example, some enterprise organizations might need to block all removable media devices entirely, while others might have specific exceptions for a vendor or serial number. Microsoft has a [local GitHub repository](https://github.com/microsoft/mdatp-devicecontrol/tree/main/macOS/policy/samples"https://github.com/microsoft/mdatp-devicecontrol/tree/main/macos/policy/samples") that you can use to build your policies.
49+
Device Control on macOS is defined through a JSON policy. This policy should have the appropriate groups, rules, and settings defined to tailor specific customer conditions. For example, some enterprise organizations might need to block all removable media devices entirely, while others might have specific exceptions for a vendor or serial number. Microsoft has a [local GitHub repository](https://github.com/microsoft/mdatp-devicecontrol/tree/main/macOS/policy/samples"https://github.com/microsoft/mdatp-devicecontrol/tree/main/macos/policy/samples") that you can use to build your policies.
5050

5151
For more information about settings, rules, and groups, see [Device Control for macOS](mac-device-control-overview.md).
5252

defender-endpoint/mac-device-control-overview.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 01/31/2025
18+
ms.date: 04/16/2025
1919
---
2020

2121
# Device Control for macOS
@@ -33,7 +33,7 @@ ms.date: 01/31/2025
3333
3434
## Requirements
3535

36-
Device control for Mac has the following prerequisites:
36+
Device control for macOS has the following prerequisites:
3737

3838
- Defender for Endpoint or Defender for Business licenses (can be a trial subscription)
3939
- Minimum OS version: macOS 11 or higher
@@ -112,8 +112,8 @@ Device control for macOS has similar capabilities to Device control for Windows,
112112

113113
- macOS doesn't have a centralized Device Manager or view of devices. Access is granted/denied to applications that interact with devices. This is why on macOS there are a richer set of [access types](#access-types). For example, a `portableDevice` policy can deny or allow `download_photos_from_device`.
114114

115-
- To stay consistent with Windows, there are `generic_read`,`generic_write` , and `generic_execute` access types. Policies with generic access types don't need to be changed if/when more specific access types are added in the future. The best practice is to use generic access types unless there's a specific need to deny/allow a more specific operation.
116-
- Creating a `deny` policy using generic access types is the best way to attempt to completely block all operations for that type of device (for example, Android phones), but there might still be gaps if the operation is performed using an application that isn't supported by macOS device control.
115+
- To stay consistent with Windows, there are `generic_read`, `generic_write`, and `generic_execute` access types. Policies with generic access types don't need to be changed if/when more specific access types are added in the future. The best practice is to use generic access types unless there's a specific need to deny/allow a more specific operation.
116+
- Creating a `deny` policy using generic access types is the best way to attempt to completely block all operations for that type of device (for example, Android phones), but there might still be gaps if the operation is performed using an application that isn't supported by macOS device control.
117117

118118

119119
### Settings
@@ -201,7 +201,7 @@ The following table lists the properties you can use in entry:
201201
| Property name | Description | Options |
202202
|:---|:---|:---|
203203
| `$type` | The type of enforcement | See table below for supported enforcements |
204-
| `options` | $type specific value to use | An array of options for the entry. May be omitted if not options are desired. |
204+
| `options` | $type specific value to use | An array of options for the entry. Might be omitted if not options are desired. |
205205

206206
#### Enforcement type
207207

@@ -258,7 +258,7 @@ v2_full_disk_access : "approved"
258258
- `active` - feature version, you should see ["v2"]. (Device Control is enabled, but not configured.)
259259
- [] - Device Control isn't configured on this machine.
260260
- ["v1"] - You are on a preview version of Device Control. Migrate to version 2 using this guide. v1 is considered obsolete and not described in this documentation.
261-
- ["v1", "v2"] - You have both v1 and v2 enabled. Offboard from v1.
261+
- ["v1," "v2"] - You have both v1 and v2 enabled. Offboard from v1.
262262
- `v1_configured` - v1 configuration is applied
263263
- `v1_enforcement_level` - when v1 is enabled
264264
- `v2_configured` - v2 configuration is applied

defender-endpoint/mac-exclusions.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure and validate exclusions for Microsoft Defender for Endpoint on Mac
3-
description: Provide and validate exclusions for Microsoft Defender for Endpoint on Mac. Exclusions can be set for files, folders, and processes.
2+
title: Configure and validate exclusions for Microsoft Defender for Endpoint on macOS
3+
description: Provide and validate exclusions for Microsoft Defender for Endpoint on macOS. Exclusions can be set for files, folders, and processes.
44
ms.service: defender-endpoint
55
author: emmwalshh
66
ms.author: ewalsh
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 06/14/2024
18+
ms.date: 04/16/2025
1919
---
2020

2121
# Configure and validate exclusions for Microsoft Defender for Endpoint on macOS
@@ -32,20 +32,20 @@ ms.date: 06/14/2024
3232
This article provides information on how to define exclusions that apply to on-demand scans, and real-time protection and monitoring.
3333

3434
> [!IMPORTANT]
35-
> The exclusions described in this article don't apply to other Defender for Endpoint on Mac capabilities, including endpoint detection and response (EDR). Files that you exclude using the methods described in this article can still trigger EDR alerts and other detections.
35+
> The exclusions described in this article don't apply to other Defender for Endpoint on macOS capabilities, including endpoint detection and response (EDR). Files that you exclude using the methods described in this article can still trigger EDR alerts and other detections.
3636
37-
You can exclude certain files, folders, processes, and process-opened files from Defender for Endpoint on Mac scans.
37+
You can exclude certain files, folders, processes, and process-opened files from Defender for Endpoint on macOS scans.
3838

39-
Exclusions can be useful to avoid incorrect detections on files or software that are unique or customized to your organization. They can also be useful for mitigating performance issues caused by Defender for Endpoint on Mac.
39+
Exclusions can be useful to avoid incorrect detections on files or software that are unique or customized to your organization. They can also be useful for mitigating performance issues caused by Defender for Endpoint on macOS.
4040

4141
To narrow down which process and/or path and/or extension you need to exclude, use [real-time-protection-statistics](mac-support-perf.md).
4242

4343
> [!WARNING]
44-
> Defining exclusions lowers the protection offered by Defender for Endpoint on Mac. You should always evaluate the risks that are associated with implementing exclusions, and you should only exclude files that you're confident aren't malicious.
44+
> Defining exclusions lowers the protection offered by Defender for Endpoint on macOS. You should always evaluate the risks that are associated with implementing exclusions, and you should only exclude files that you're confident aren't malicious.
4545
4646
## Supported exclusion types
4747

48-
The following table shows the exclusion types supported by Defender for Endpoint on Mac.
48+
The following table shows the exclusion types supported by Defender for Endpoint on macOS.
4949

5050
Exclusion|Definition|Examples
5151
---|---|---
@@ -66,15 +66,15 @@ File, folder, and process exclusions support the following wildcards:
6666
>
6767
> The product attempts to resolve firm links when evaluating exclusions. Firm link resolution doesn't work when the exclusion contains wildcards or the target file (on the `Data` volume) doesn't exist.
6868
69-
## Best practices for adding antimalware exclusions for Microsoft Defender for Endpoint on macOS.
69+
## Best practices for adding anti-malware exclusions for Microsoft Defender for Endpoint on macOS
7070

7171
1. Write down why an exclusion was added to a central location where only SecOps and/or Security Administrator have access. For example, list the submitter, date, app name, reason, and exclusion information.
7272

7373
1. Make sure to have an expiration date* for the exclusions
7474

7575
*except for apps that the ISV stated that there's no other tweaking that could be done to prevent the false positive or higher cpu utilization from occurring.
7676

77-
1. Avoid migrating non-Microsoft antimalware exclusions since they might no longer be applicable nor applicable to Microsoft Defender for Endpoint on macOS.
77+
1. Avoid migrating non-Microsoft anti-malware exclusions since they might no longer be applicable nor applicable to Microsoft Defender for Endpoint on macOS.
7878

7979
1. Order of exclusions to consider top (more secure) to bottom (least secure):
8080

@@ -141,7 +141,7 @@ In the following Bash snippet, replace `test.txt` with a file that conforms to y
141141
curl -o test.txt https://secure.eicar.org/eicar.com.txt
142142
```
143143

144-
If Defender for Endpoint on Mac reports malware, then the rule isn't working. If there's no report of malware, and the downloaded file exists, then the exclusion is working. You can open the file to confirm that the contents are the same as what is described on the [EICAR test file website](https://www.eicar.org/download-anti-malware-testfile/).
144+
If Defender for Endpoint on macOS reports malware, then the rule isn't working. If there's no report of malware, and the downloaded file exists, then the exclusion is working. You can open the file to confirm that the contents are the same as what is described on the [EICAR test file website](https://www.eicar.org/download-anti-malware-testfile/).
145145

146146
If you don't have Internet access, you can create your own EICAR test file. Write the EICAR string to a new text file with the following Bash command:
147147

defender-endpoint/mac-health-status.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Troubleshoot agent health issues with Defender for Endpoint on Mac
2+
title: Troubleshoot agent health issues with Defender for Endpoint on macOS
33
description: Investigate macOS Defender agent health issues
44
author: emmwalshh
55
ms.author: ewalsh
@@ -10,7 +10,7 @@ audience: ITPro
1010
ms.service: defender-endpoint
1111
ms.subservice: macos
1212
ms.topic: troubleshooting-general
13-
ms.date: 03/04/2025
13+
ms.date: 04/16/2025
1414
ms.collection:
1515
- m365-security
1616
- tier3
@@ -86,8 +86,8 @@ You can run `mdatp health --help` on recent versions to list all supported featu
8686

8787
## See also
8888

89-
- [What's new in Microsoft Defender for Endpoint on Mac](mac-whatsnew.md)
90-
- [Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md)
89+
- [What's new in Microsoft Defender for Endpoint on macOS](mac-whatsnew.md)
90+
- [Microsoft Defender for Endpoint on macOS](microsoft-defender-endpoint-mac.md)
9191

9292
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
9393

defender-endpoint/mac-install-manually.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: admindeeplinkDEFENDER
1616
ms.topic: conceptual
1717
ms.subservice: macos
1818
search.appverid: met150
19-
ms.date: 04/30/2024
19+
ms.date: 04/16/2025
2020
---
2121

2222
# Manual deployment for Microsoft Defender for Endpoint on macOS
@@ -123,9 +123,9 @@ To complete this process, you must have admin privileges on the device.
123123

124124
:::image type="content" source="media/security-privacy-window-updated.png" alt-text="Screenshot that shows the security and privacy window.":::
125125

126-
13. Repeat steps 11 and 12 for all system extensions distributed with Microsoft Defender for Endpoint on Mac.
126+
13. Repeat steps 11 and 12 for all system extensions distributed with Microsoft Defender for Endpoint on macOS.
127127

128-
14. As part of the Endpoint Detection and Response capabilities, Microsoft Defender for Endpoint on Mac inspects socket traffic and reports this information to the Microsoft Defender portal. When prompted to grant Microsoft Defender for Endpoint permissions to filter network traffic, select **Allow**.
128+
14. As part of the Endpoint Detection and Response capabilities, Microsoft Defender for Endpoint on macOS inspects socket traffic and reports this information to the Microsoft Defender portal. When prompted to grant Microsoft Defender for Endpoint permissions to filter network traffic, select **Allow**.
129129

130130
:::image type="content" source="media/monterey-install-4.png" alt-text="Screenshot that shows the system extension security preferences2":::
131131

@@ -179,7 +179,7 @@ You can view applications permitted to run in background in System Settings => s
179179

180180
:::image type="content" source="media/background-items.png" alt-text="Screenshot that shows background items":::
181181

182-
Make sure all Microsoft Defender and Microsoft Corporation items are enabled. If they are disabled, then macOS won't start Microsoft Defender after a machine restart.
182+
Make sure all Microsoft Defender and Microsoft Corporation items are enabled. If they're disabled, then macOS won't start Microsoft Defender after a machine restart.
183183

184184
## Bluetooth permissions
185185

@@ -261,15 +261,15 @@ See [Uninstalling](mac-resources.md#uninstalling) for details on how to remove M
261261
> [!TIP]
262262
>
263263
> - Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: [Microsoft Defender for Endpoint Tech Community](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/bd-p/MicrosoftDefenderATP).
264-
> - If you have any feedback that you'll like to share, submit it by opening Microsoft Defender Endpoint on Mac on your device and navigate to **Help** \> **Send feedback**.
264+
> - If you have any feedback that you like to share, submit it by opening Microsoft Defender Endpoint on macOS on your device and navigate to **Help** \> **Send feedback**.
265265
266266
## Recommended content
267267

268-
- [Learn how to install, configure, update, and use Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md).
268+
- [Learn how to install, configure, update, and use Microsoft Defender for Endpoint on macOS](microsoft-defender-endpoint-mac.md).
269269
- [Learn how to set up the Microsoft Defender for Endpoint on macOS policies in Jamf](mac-jamfpro-policies.md).
270270
- [Learn how to deploy Microsoft Defender for Endpoint on macOS with Jamf Pro](mac-install-with-jamf.md).
271271
- [Learn how to troubleshoot license issues in Microsoft Defender for Endpoint on Mac](mac-support-license.md).
272-
- [Learn how to use resources for Microsoft Defender for Endpoint on Mac, including how to uninstall it, how to collect diagnostic logs, CLI commands, and known issues with the product](mac-resources.md).
273-
- [Learn how to configure Microsoft Defender for Endpoint on Mac in enterprise organizations](mac-preferences.md).
274-
- [Learn how to install Microsoft Defender for Endpoint on Mac on other management solutions](mac-install-with-other-mdm.md).
272+
- [Learn how to use resources for Microsoft Defender for Endpoint on macOS, including how to uninstall it, how to collect diagnostic logs, CLI commands, and known issues with the product](mac-resources.md).
273+
- [Learn how to configure Microsoft Defender for Endpoint on macOS in enterprise organizations](mac-preferences.md).
274+
- [Learn how to install Microsoft Defender for Endpoint on macOS on other management solutions](mac-install-with-other-mdm.md).
275275
- [Learn how to detect and block Potentially Unwanted Applications (PUA) using Microsoft Defender for Endpoint on macOS](mac-pua.md).

defender-endpoint/mac-install-with-intune.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Intune-based deployment for Microsoft Defender for Endpoint on Mac
3-
description: Install Microsoft Defender for Endpoint on Mac, using Microsoft Intune.
2+
title: Intune-based deployment for Microsoft Defender for Endpoint on macOS
3+
description: Install Microsoft Defender for Endpoint on macOS, using Microsoft Intune.
44
ms.service: defender-endpoint
55
author: emmwalshh
66
ms.author: ewalsh
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: macos
1717
search.appverid: met150
18-
ms.date: 12/02/2024
18+
ms.date: 04/16/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on macOS with Microsoft Intune
@@ -35,14 +35,14 @@ Before you get started, see [the main Microsoft Defender for Endpoint on macOS p
3535

3636
## Overview
3737

38-
The following table summarizes the steps to deploy and manage Microsoft Defender for Endpoint on Macs via Microsoft Intune. See the following table for more detailed steps:
38+
The following table summarizes the steps to deploy and manage Microsoft Defender for Endpoint on macOS via Microsoft Intune. See the following table for more detailed steps:
3939

4040
|Step |Sample file name |Bundle identifier |
4141
|---------|---------|---------|
4242
|Approve system extension|`sysext.mobileconfig`|N/A|
4343
|Network extension policy|`netfilter.mobileconfig`|N/A|
4444
|Full Disk Access|`fulldisk.mobileconfig`|`com.microsoft.wdav.epsext`|
45-
|Microsoft Defender for Endpoint configuration settings <br/><br/>If you're planning to run non-Microsoft antivirus on Mac, set `passiveMode` to `true`.|`MDE_MDAV_and_exclusion_settings_Preferences.xml`|`com.microsoft.wdav`|
45+
|Microsoft Defender for Endpoint configuration settings <br/><br/>If you're planning to run non-Microsoft antivirus on macOS, set `passiveMode` to `true`.|`MDE_MDAV_and_exclusion_settings_Preferences.xml`|`com.microsoft.wdav`|
4646
|Background services|`background_services.mobileconfig`|N/A|
4747
|Configure Microsoft Defender for Endpoint notifications|`notif.mobileconfig`|`com.microsoft.wdav.tray`|
4848
|Accessibility settings|`accessibility.mobileconfig`|`com.microsoft.dlp.daemon`|
@@ -104,7 +104,7 @@ As part of the Endpoint Detection and Response capabilities, Microsoft Defender
104104
Download [netfilter.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/master/macos/mobileconfig/profiles/netfilter.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
105105

106106
> [!IMPORTANT]
107-
> Only one `.mobileconfig` (plist) for Network Filter is supported. Adding multiple Network Filters leads to network connectivity issues on Mac. This issue isn't specific to Defender for Endpoint on macOS.
107+
> Only one `.mobileconfig` (plist) for Network Filter is supported. Adding multiple Network Filters leads to network connectivity issues on macOS. This issue isn't specific to Defender for Endpoint on macOS.
108108
109109
To configure your network filter:
110110

@@ -375,7 +375,7 @@ To set Device Control for Microsoft Defender for Endpoint on macOS, follow the s
375375

376376
To set Purview's Data Loss Prevention (DLP) for endpoint on macOS, follow the steps in [Onboard and offboard macOS devices into Compliance solutions using Microsoft Intune](/purview/device-onboarding-offboarding-macos-intune-mde).
377377

378-
### Step 13: Check status of PList (.mobileconfig)
378+
### Step 13: Check status of PList (.Mobileconfig)
379379

380380
After completing the profile configuration, you'll be able to review the status of the policies.
381381

@@ -387,7 +387,7 @@ Once the Intune changes are propagated to the enrolled devices, you can see them
387387

388388
#### Client device setup
389389

390-
A standard [Company Portal installation](/mem/intune/user-help/enroll-your-device-in-intune-macos-cp) is sufficient for a mac device.
390+
A standard [Company Portal installation](/mem/intune/user-help/enroll-your-device-in-intune-macos-cp) is sufficient for a Mac device.
391391

392392
1. Confirm device management.
393393

0 commit comments

Comments
 (0)