Skip to content

Commit dca2329

Browse files
authored
Merge pull request #1720 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/defender-docs (branch public)
2 parents e0b09d8 + 5d7981c commit dca2329

File tree

4 files changed

+29
-33
lines changed

4 files changed

+29
-33
lines changed

defender-endpoint/defender-endpoint-demonstration-smartscreen-url-reputation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
- demo
1515
ms.topic: article
1616
ms.subservice: asr
17-
ms.date: 01/15/2024
17+
ms.date: 10/28/2024
1818
---
1919

2020
# URL reputation demonstrations
@@ -71,7 +71,7 @@ Blocked from downloading because of its URL reputation
7171

7272
- [Download blocked due to URL reputation](https://demo.smartscreen.msft.net/download/malwaredemo/freevideo.exe)
7373

74-
Launching this link should render a message similar to the Malware page message.
74+
Launching this link should render a warning that the download was blocked as being unsafe by Microsoft Edge.
7575

7676
### Exploit page
7777

defender-endpoint/indicator-manage.md

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -15,20 +15,18 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: asr
1717
search.appverid: met150
18-
ms.date: 12/18/2020
18+
ms.date: 10/28/2024
1919
---
2020

2121
# Manage indicators
2222

2323
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2424

25-
2625
**Applies to:**
2726
- [Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
2827
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
2928
- [Microsoft Defender XDR](/defender-xdr)
3029

31-
3230
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://www.microsoft.com/WindowsForBusiness/windows-atp?ocid=docs-wdatp-automationexclusionlist-abovefoldlink)
3331
3432
1. In the navigation pane, select **Settings** \> **Endpoints** \> **Indicators** (under **Rules**).
@@ -55,29 +53,29 @@ Download the sample CSV to know the supported column attributes.
5553

5654
> [!NOTE]
5755
> Only 500 indicators can be uploaded for each batch.
58-
>
5956
> Attempting to import indicators with specific categories requires the string to be written in Pascal case convention and only accepts the category list available at the portal.
6057
6158
The following table shows the supported parameters.
6259

6360
| Parameter|Type|Description |
6461
| ---| ---| --- |
65-
| indicatorType|Enum|Type of the indicator. Possible values are: *FileSha1*, *FileSha256*, *IpAddress*, *DomainName*, and *Url*. **Required** |
66-
| indicatorValue|String|Identity of the [Indicator](api/ti-indicator.md) entity. **Required** |
67-
| action|Enum|The action that is taken if the indicator is discovered in the organization. Possible values are: *Allowed*, *Audit*, *BlockAndRemediate*, *Warn*, and *Block*. **Required** |
68-
| title|String|Indicator alert title. **Required** |
69-
| description|String| Description of the indicator. **Required** |
70-
| expirationTime|DateTimeOffset|The expiration time of the indicator in the following format YYYY-MM-DDTHH:MM:SS.0Z. The indicator gets deleted if the expiration time passes and whatever happens at the expiration time occurs at the seconds (SS) value. **Optional** |
71-
| severity|Enum|The severity of the indicator. Possible values are: *Informational*, *Low*, *Medium*, and *High*. **Optional** |
72-
| recommendedActions|String|TI indicator alert recommended actions. **Optional** |
73-
| rbacGroups|String|Comma-separated list of RBAC groups the indicator would be applied to. **Optional** |
74-
| category|String|Category of the alert. Examples include: Execution and credential access. **Optional** |
75-
| mitretechniques|String|MITRE techniques code/id (comma separated). For more information, see [Enterprise tactics](https://attack.mitre.org/tactics/enterprise/). **Optional** It's recommended to add a value in category when a MITRE technique. |
76-
| GenerateAlert|String|Whether the alert should be generated. Possible Values are: True or False. **Optional** |
62+
| indicatorType|Enum|Type of the indicator. Possible values are: `FileSha1`, `FileSha256`, `IpAddress`, `DomainName`, and `Url`. <br/> **Required** |
63+
| indicatorValue|String|Identity of the [Indicator](api/ti-indicator.md) entity. <br/> **Required** |
64+
| action|Enum|The action that is taken if the indicator is discovered in the organization. Possible values are: `Allowed`, `Audit`, `BlockAndRemediate`, `Warn`, and `Block`. <br/> **Required** |
65+
| title|String|Indicator alert title.<br/> **Required** |
66+
| description|String| Description of the indicator.<br/> **Required** |
67+
| expirationTime|DateTimeOffset|The expiration time of the indicator in the following format `YYYY-MM-DDTHH:MM:SS.0Z`. The indicator gets deleted if the expiration time passes and whatever happens at the expiration time occurs at the seconds (SS) value. <br/>**Optional** |
68+
| severity|Enum|The severity of the indicator. Possible values are: `Informational`, `Low`, `Medium`, and `High`. <br/>**Optional** |
69+
| recommendedActions|String|TI indicator alert recommended actions. <br/>**Optional** |
70+
| rbacGroups|String|Comma-separated list of RBAC groups the indicator would be applied to. <br/>**Optional** |
71+
| category|String|Category of the alert. Examples include: Execution and credential access. <br/>**Optional** |
72+
| mitretechniques|String|MITRE techniques code/id (comma separated). For more information, see [Enterprise tactics](https://attack.mitre.org/tactics/enterprise/). <br/> **Optional** <br/>It's recommended to add a value in category when a MITRE technique. |
73+
| GenerateAlert|String|Whether the alert should be generated. Possible Values are: `True` or `False`. <br/>**Optional** |
7774

7875
> [!NOTE]
79-
> Classless Inter-Domain Routing (CIDR) notation for IP addresses is not supported.
80-
For more information, see [Microsoft Defender for Endpoint alert categories are now aligned with MITRE ATT&CK!](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/microsoft-defender-atp-alert-categories-are-now-aligned-with/ba-p/732748).
76+
> Classless Inter-Domain Routing (CIDR) notation for IP addresses is not supported. For more information, see [Microsoft Defender for Endpoint alert categories are now aligned with MITRE ATT&CK!](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/microsoft-defender-atp-alert-categories-are-now-aligned-with/ba-p/732748).
77+
>
78+
> Network indicators do not support the action type, `BlockAndRemediate`. If a network indicator is set to `BlockAndRemediate`, it won't import.
8179
8280
Watch this video to learn how Microsoft Defender for Endpoint provides multiple ways to add and manage Indicators of compromise (IoCs).
8381
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4qLVw]
@@ -89,4 +87,5 @@ Watch this video to learn how Microsoft Defender for Endpoint provides multiple
8987
- [Create indicators for IPs and URLs/domains](indicator-ip-domain.md)
9088
- [Create indicators based on certificates](indicator-certificates.md)
9189
- [Exclusions for Microsoft Defender for Endpoint and Microsoft Defender Antivirus](defender-endpoint-antivirus-exclusions.md)
90+
9291
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

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

Lines changed: 10 additions & 13 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: 10/11/2024
18+
ms.date: 10/28/2024
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on macOS with Microsoft Intune
@@ -80,7 +80,7 @@ In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2
8080

8181
1. In the **Settings picker**, expand the **System Configuration** category, and then select **System Extensions** > **Allowed System Extensions:**
8282

83-
![Screenshot showing the Settings Picker](media/mac-install-with-intune/screenshot-2024-09-11-at-1.41.09pm.png)
83+
:::image type="content" alt-text="Screenshot showing the Settings Picker" source="media/mac-install-with-intune/screenshot-2024-09-11-at-1.41.09-pm.png" lightbox="media/mac-install-with-intune/screenshot-2024-09-11-at-1.41.09-pm.png":::
8484

8585
1. Close the Settings picker, and then select **+ Edit instance**.
8686

@@ -91,7 +91,7 @@ In the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2
9191
|`com.microsoft.wdav.epsext`|`UBF8T346G9`|
9292
|`com.microsoft.wdav.netext`|`UBF8T346G9`|
9393

94-
![Screenshot showing allowed system extensions](media/mac-install-with-intune/image003.png)
94+
:::image type="content" alt-text="Screenshot showing allowed system extensions" source="media/mac-install-with-intune/image003.png" lightbox="media/mac-install-with-intune/image003.png":::
9595

9696
1. On the **Assignments** tab, assign the profile to a group where the macOS devices or users are located.
9797

@@ -203,7 +203,7 @@ Download [notif.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-
203203

204204
To turn off notifications for the end users, you can change **Show NotificationCenter** from `true` to `false` in [notif.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/master/macos/mobileconfig/profiles/notif.mobileconfig).
205205

206-
:::image type="content" source="../defender-endpoint/media/image.png" alt-text="Screenshot showing notif.mobileconfig with ShowNotificationCenter set to True." lightbox="../defender-endpoint/media//image.png":::
206+
:::image type="content" source="../defender-endpoint/media/image.png" alt-text="Screenshot showing notif.mobileconfig with ShowNotificationCenter set to True.":::
207207

208208
To configure notifications:
209209

@@ -217,7 +217,7 @@ To configure notifications:
217217

218218
1. Select **Create**.
219219

220-
1. On the **Basics** tab, **Name** the profile. For example, `BackgroundServices-prod-macOS-Default-MDE`. Then select **Next**.
220+
1. On the **Basics** tab, **Name** the profile. For example, `Notify-prod-macOS-Default-MDE`. Then select **Next**.
221221

222222
1. On the **Configuration settings** tab, enter a **Custom configuration profile** name. For example, `Notif.mobileconfig`.
223223

@@ -233,7 +233,7 @@ To configure notifications:
233233

234234
This profile is used to allow Microsoft Defender for Endpoint on macOS to access the accessibility settings on Apple macOS High Sierra (10.13.6) and newer.
235235

236-
Download [accessibility.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/mobileconfig/profiles/accessibility.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
236+
Download [accessibility.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/refs/heads/master/macos/mobileconfig/profiles/accessibility.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
237237

238238
1. Under **Configuration profiles**, select **Create Profile**.
239239

@@ -262,7 +262,7 @@ Download [accessibility.mobileconfig](https://github.com/microsoft/mdatp-xplat/b
262262
> [!CAUTION]
263263
> macOS 14 (Sonoma) contains new privacy enhancements. Beginning with this version, by default, applications cannot access Bluetooth without explicit consent. Microsoft Defender for Endpoint uses it if you configure Bluetooth policies for Device Control.
264264
265-
Download [bluetooth.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/mobileconfig/profiles/bluetooth.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles) and use the same workflow as in [Step 6: Accessibility settings](#step-6-accessibility-settings) to enable Bluetooth access.
265+
Download [bluetooth.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/refs/heads/master/macos/mobileconfig/profiles/bluetooth.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles) and use the same workflow as in [Step 6: Accessibility settings](#step-6-accessibility-settings) to enable Bluetooth access.
266266

267267
> [!NOTE]
268268
> Bluetooth granted through Apple MDM Configuration Profile is not reflected in System Settings => Privacy & Security => Bluetooth.
@@ -277,10 +277,10 @@ This profile is used to update the Microsoft Defender for Endpoint on macOS via
277277

278278
For more information, see [Deploy updates for Microsoft Defender for Endpoint on macOS](mac-updates.md).
279279

280-
Download [AutoUpdate2.mobileconfig](https://github.com/microsoft/mdatp-xplat/blob/master/macos/settings/microsoft_auto_update/com.microsoft.autoupdate2.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
280+
Download [com.microsoft.autoupdate2.mobileconfig](https://raw.githubusercontent.com/microsoft/mdatp-xplat/refs/heads/master/macos/settings/microsoft_auto_update/com.microsoft.autoupdate2.mobileconfig) from [GitHub repository](https://github.com/microsoft/mdatp-xplat/tree/master/macos/mobileconfig/profiles).
281281

282282
> [!NOTE]
283-
> The sample `AutoUpdate2.mobileconfig` from the GitHub repository has it set to Current Channel (Production).
283+
> The sample `com.microsoft.autoupdate2.mobileconfig` from the GitHub repository has it set to Current Channel (Production).
284284
285285
1. Under **Configuration profiles**, select **Create Profile**.
286286

@@ -294,7 +294,7 @@ Download [AutoUpdate2.mobileconfig](https://github.com/microsoft/mdatp-xplat/blo
294294

295295
1. On the **Basics** tab, **Name** the profile. For example, `Autoupdate-prod-macOS-Default-MDE`. Then select **Next**.
296296

297-
1. On the **Configuration settings** tab, enter a **Custom configuration profile** name. For example, `Autoupdate.mobileconfig`.
297+
1. On the **Configuration settings** tab, enter a **Custom configuration profile** name. For example, `com.microsoft.autoupdate2.mobileconfig`.
298298

299299
1. Choose a **Deployment channel** and select **Next**.
300300

@@ -329,9 +329,6 @@ For more information about managing security settings, see:
329329
- [Manage Microsoft Defender for Endpoint on devices with Microsoft Intune](/mem/intune/protect/mde-security-integration?pivots=mdssc-ga)
330330
- [Manage security settings for Windows, macOS, and Linux natively in Defender for Endpoint](https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/manage-security-settings-for-windows-macos-and-linux-natively-in/ba-p/3870617)
331331

332-
> [!NOTE]
333-
> If the device is managed via Intune, the device won't register via Defender for Endpoint Security Settings Management in the [Microsoft Defender portal](https://security.microsoft.com). Only the policies set via Intune take effect.
334-
335332
#### **Set policies using Microsoft Intune**
336333

337334
You can manage the security settings for Microsoft Defender for Endpoint on macOS under **Setting Preferences** in Microsoft Intune.
File renamed without changes.

0 commit comments

Comments
 (0)