Skip to content

Commit 86fc259

Browse files
committed
Merge branch 'main' into pr/1892
2 parents 455ec13 + c09f72e commit 86fc259

File tree

74 files changed

+1200
-706
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

74 files changed

+1200
-706
lines changed

ATPDocs/whats-new.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,22 @@ For more information, see also:
2222

2323
For updates about versions and features released six months ago or earlier, see the [What's new archive for Microsoft Defender for Identity](whats-new-archive.md).
2424

25+
## December 2024
26+
27+
### New security posture assessment: Prevent Certificate Enrollment with arbitrary Application Policies (ESC15)
28+
29+
Defender for Identity has added the new **Prevent Certificate Enrollment with arbitrary Application Policies (ESC15)** recommendation in Microsoft Secure Score.
30+
31+
This recommendation directly addresses the recently published [CVE-2024-49019](https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2024-49019), which highlights security risks associated with vulnerable AD CS configurations. This security posture assessment lists all vulnerable certificate templates found in customer environments due to unpatched AD CS servers.
32+
33+
The new recommendation is added to other AD CS-related recommendations. Together, these assessments offer security posture reports that surface security issues and severe misconfigurations that post risks to the entire organization, together with related detections.
34+
35+
For more information, see:
36+
37+
- [Security assessment: Prevent Certificate Enrollment with arbitrary Application Policies (ESC15)](https://go.microsoft.com/fwlink/?linkid=2296922)
38+
39+
- [Microsoft Defender for Identity's security posture assessments](security-assessment.md)
40+
2541
## October 2024
2642

2743
### MDI is expanding coverage with new 10 Identity posture recommendations (preview)
@@ -532,6 +548,7 @@ This version includes improvements and bug fixes for cloud services and the Defe
532548

533549
- [What is Microsoft Defender for Identity?](what-is.md)
534550
- [Frequently asked questions](technical-faq.yml)
551+
535552
- [Defender for Identity prerequisites](prerequisites.md)
536553
- [Defender for Identity capacity planning](capacity-planning.md)
537554
- [Check out the Defender for Identity forum!](<https://aka.ms/MDIcommunity>)

CloudAppSecurityDocs/api-entities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Entities API
33
description: This article provides information about using the Entities API.
4-
ms.date: 01/29/2023
4+
ms.date: 11/28/2024
55
ms.topic: reference
66
---
77
# Entities API
@@ -32,7 +32,7 @@ The following table describes the supported filters:
3232
| entity | entity pk | eq, neq | Filter entities with specific entities pks. If a user is selected, this filter also returns all of the user's accounts. Example: `[{ "id": "entity-id", "inst": 0 }]` |
3333
| userGroups |string | eq, neq | Filter entities by their associated group IDs |
3434
| app | integer | eq, neq | Filter entities using services with the specified SaaS ID for example: 11770 |
35-
| instance | integer | eq, neq | Filter entities using services with the specified Appstances (SaaS ID and Instance ID), for example: 11770, 1059065 |
35+
| instance | integer | eq, neq | Filter entities using services with the specified app instances (SaaS ID and Instance ID). For example: 11770, 1059065 |
3636
| isExternal | boolean | eq | The entity's affiliation. Possible values include:<br /><br />**true**: External<br />**false**: Internal<br />**null**: No value |
3737
| domain | string | eq, neq, isset, isnotset | The entity's related domain |
3838
| organization | string | eq, neq, isset, isnotset | Filter entities with the specified organization unit |

CloudAppSecurityDocs/file-filters.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,15 @@ To provide data protection, Microsoft Defender for Cloud Apps gives you visibili
1111

1212
> [!IMPORTANT]
1313
> Starting **September 1, 2024**, we'll be phasing out the **Files** **page** from Microsoft Defender for Cloud Apps. Core functionalities of the Files page will be available on the **Cloud apps > Policies > Policy Management** page. We recommend using the Policy Management page to investigate files and to create, modify, and filter Information Protection policies and Malware files. For more information, see [File policies in Microsoft Defender for Cloud Apps](data-protection-policies.md).
14+
>
15+
16+
>[!NOTE]
17+
> **Query Size Limitation in Files Policy Filters and "Edit and Preview Results"**
18+
>
19+
> - When creating or editing a file policy, or when using the "Edit and preview results" option, there is a query size limitation. This limitation ensures optimal performance and prevents system overload.
20+
> - If your query exceeds the allowed size, you may need to refine your criteria or use other filters to fit within the acceptable limits. For example, if the policy involves "collaborators" criteria that includes the group "everyone" or "everyone except external users" it may cause a failure due to query size limitation.
21+
> - Please note that if the query exceeds the size limitation, the system will not specify which filter caused the failure.
22+
1423
## Enable file monitoring
1524

1625
To enable file monitoring for Defender for Cloud Apps, first turn on file monitoring in the **Settings** area. In the Microsoft Defender portal, select **Settings** > **Cloud Apps** > **Information Protection** > **Files** > **Enable file monitoring** > **Save**.

CloudAppSecurityDocs/protect-egnyte.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Protect your Egnyte environment (Preview) | Microsoft Defender for Cloud Apps
33
description: Learn how about connecting your Egnyte app to Defender for Cloud Apps using the API connector.
4-
ms.date: 12/05/2023
4+
ms.date: 12/12/2024
55
ms.topic: how-to
66
---
77
# How Defender for Cloud Apps helps protect your Egnyte environment
@@ -77,9 +77,9 @@ This section describes how to connect Microsoft Defender for Cloud Apps to your
7777
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**. Make sure the status of the connected App Connector is **Connected**.
7878

7979
>[!NOTE]
80-
>Microsoft recommends using a short lived access token. Egnyte doesn't currently support short lived tokens. We recommend our customers to refresh the access token every 6 months as a security best practice.
81-
>To refresh the access token, revoke the old token by following [Revoking an oAuth token](https://developers.egnyte.com/docs/read/Public_API_Authentication#Revoking-an-OAuth-Token).
82-
>Once the old token is revoked, reconnect the Egnyte connector by following the process documented above.
80+
>- Microsoft recommends using a short lived access token. Egnyte doesn't currently support short lived tokens. We recommend our customers to refresh the access token every 6 months as a security best practice. To refresh the access token, revoke the old token by following [Revoking an oAuth token](https://developers.egnyte.com/docs/read/Public_API_Authentication#Revoking-an-OAuth-Token). Once the old token is revoked, reconnect the Egnyte connector by following the process documented above.
81+
>
82+
>- Defender for Cloud Apps intentionally provides a lower rate limit than Egnyte's maximum to avoid exceeding the API constraints. For more infomration, see the relevant Egnyte documentation: [Rate limiting](https://developers.egnyte.com/docs/read/Best_Practices) | [Audit Reporting API v2](https://developers.egnyte.com/docs/read/Audit_Reporting_API_V2)
8383
8484
## Next steps
8585

CloudAppSecurityDocs/protect-servicenow.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Protect your ServiceNow environment | Microsoft Defender for Cloud Apps
33
description: Learn how about connecting your ServiceNow app to Defender for Cloud Apps using the API connector.
4-
ms.date: 12/26/2023
4+
ms.date: 12/12/2024
55
ms.topic: how-to
66
---
77

@@ -45,7 +45,8 @@ In Secure Score, select **Recommended actions** and filter by **Product** = **Se
4545

4646
For more information, see:
4747
- [Security posture management for SaaS apps](security-saas.md)
48-
- [Microsoft Secure Score](/microsoft-365/security/defender/microsoft-secure-score)
48+
- [Microsoft Secure Score](/microsoft-365/security/defender/microsoft-secure-score
49+
)
4950

5051
## Control ServiceNow with built-in policies and policy templates
5152

@@ -154,11 +155,11 @@ For more information, see the [ServiceNow product documentation](https://docs.se
154155
1. Establish an internal procedure to ensure that the connection remains alive. A couple of days before the expected expiration of the refresh token lifespan.
155156
Revoke to the old refresh token. We don't recommend keeping old keys for security reasons.
156157

157-
1. On the ServiceNow pane, search for System OAuth, and then select Manage Tokens.
158+
1. On the ServiceNow pane, search for **System OAuth**, and then select **Manage Tokens**.
158159

159160
1. Select the old token from the list according to the OAuth name and expiration date.
160161

161-
1. Select Revoke Access > Revoke.
162+
1. Select **Revoke Access > Revoke**.
162163
163164
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**.
164165

@@ -181,7 +182,7 @@ Revoke to the old refresh token. We don't recommend keeping old keys for securit
181182

182183
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**. Make sure the status of the connected App Connector is **Connected**.
183184

184-
After connecting ServiceNow, you'll receive events for seven days prior to connection.
185+
After connecting ServiceNow, you'll receive events for 1 hour prior to connection.
185186

186187
### Legacy ServiceNow connection
187188

@@ -210,7 +211,7 @@ To connect ServiceNow with Defender for Cloud Apps, you must have admin-level pe
210211

211212
1. Select **Connect**.
212213
1. In the Microsoft Defender Portal, select **Settings**. Then choose **Cloud Apps**. Under **Connected apps**, select **App Connectors**. Make sure the status of the connected App Connector is **Connected**.
213-
After connecting ServiceNow, you'll receive events for seven days prior to connection.
214+
After connecting ServiceNow, you'll receive events for one hour prior to connection.
214215

215216
If you have any problems connecting the app, see [Troubleshooting App Connectors](troubleshooting-api-connectors-using-error-messages.md).
216217

defender-business/mdb-onboard-devices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ audience: Admin
99
ms.topic: overview
1010
ms.service: defender-business
1111
ms.localizationpriority: medium
12-
ms.date: 06/19/2024
12+
ms.date: 12/12/2024
1313
ms.reviewer: efratka, nehabha, muktaagarwal
1414
f1.keywords: NOCSH
1515
ms.collection:
@@ -274,7 +274,7 @@ After a device is enrolled in Intune, you can add it to a device group. [Learn m
274274
## Servers
275275

276276
> [!NOTE]
277-
> If you're planning to onboard an instance of Windows Server or Linux Server, you'll need an additional license, such as [Microsoft Defender for Business servers](get-defender-business.md#how-to-get-microsoft-defender-for-business-servers). Alternately, you could use [Microsoft Defender for Servers Plan 1 or Plan 2](/azure/defender-for-cloud/plan-defender-for-servers). To learn more, see [What happens if I have a mix of Microsoft endpoint security subscriptions](mdb-faq.yml#what-happens-if-i-have-a-mix-of-microsoft-endpoint-security-subscriptions)?
277+
> If you're planning to onboard an instance of Windows Server or Linux Server, you'll need an additional license, such as [Microsoft Defender for Business servers](get-defender-business.md#how-to-get-microsoft-defender-for-business-servers).
278278
279279
Choose the operating system for your server:
280280

defender-endpoint/TOC.yml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -137,9 +137,10 @@
137137
- name: Migrating devices to streamlined method
138138
href: migrate-devices-streamlined.md
139139

140-
- name: Onboarding Windows Client
140+
- name: Onboard client devices
141+
href: onboard-client.md
141142
items:
142-
- name: Onboarding Windows Client overview
143+
- name: Onboarding Windows client overview
143144
href: onboard-windows-client.md
144145
- name: Defender for Endpoint plug-in for WSL
145146
href: mde-plugin-wsl.md
@@ -158,7 +159,8 @@
158159
- name: Onboard previous versions of Windows
159160
href: onboard-downlevel.md
160161

161-
- name: Onboarding Windows Server
162+
- name: Onboard server devices
163+
href: onboard-server.md
162164
items:
163165
- name: Onboarding Windows Server overview
164166
href: onboard-windows-server.md

defender-endpoint/android-configure.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,8 @@ For more information about how to set up Defender for Endpoint on Android and Co
3737

3838
> [!NOTE]
3939
> Defender for Endpoint on Android only supports creating custom indicators for IP addresses and URLs/domains.
40+
>
41+
> Also, alerts for custom indicators are currently not supported for Defender for Endpoint on Android.
4042
4143
Defender for Endpoint on Android enables admins to configure custom indicators to support Android devices as well. For more information on how to configure custom indicators, see [Overview of indicators](indicators-overview.md).
4244

defender-endpoint/behavior-monitor-macos.md

Lines changed: 83 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: Behavior Monitoring in Microsoft Defender Antivirus on macOS
33
description: Behavior Monitoring in Microsoft Defender Antivirus on macOS
4-
author: YongRhee-MSFT
5-
ms.author: yongrhee
4+
author: denisebmsft
5+
ms.author: deniseb
66
manager: deniseb
77
ms.service: defender-endpoint
88
ms.topic: overview
9-
ms.date: 05/29/2024
9+
ms.date: 12/11/2024
1010
ms.subservice: ngp
1111
audience: ITPro
1212
ms.collection:
@@ -35,26 +35,26 @@ f1.keywords: NOCSH
3535
> [!IMPORTANT]
3636
> Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
3737
38-
## Prerequisites
38+
## Overview of behavior monitoring
3939

40-
- Device is onboarded to Microsoft Defender for Endpoint.
41-
- [Preview features](/defender-endpoint/preview) is enabled in the Microsoft XDR portal ([https://security.microsoft.com](https://security.microsoft.com)).
42-
- Device must be in the [Beta channel](/defender-endpoint/mac-updates) (formerly InsiderFast).
43-
- Minimal Microsoft Defender for Endpoint version number must be Beta (Insiders-Fast): 101.24042.0002 or newer. Version number refers to the **app_version** (also known as **Platform update**).
44-
- Ensure that Real-Time Protection (RTP) is enabled.
45-
- Ensure [cloud-delivered protection](/defender-endpoint/mac-preferences) is enabled.
46-
- Device must be explicitly enrolled into the preview.
40+
Behavior monitoring monitors process behavior to detect and analyze potential threats based on the behavior of the applications, daemons, and files within the system. As behavior monitoring observes how the software behaves in real-time, it can adapt quickly to new and evolving threats and block them.
4741

48-
## Overview
42+
## Prerequisites
4943

50-
Behavior monitoring monitors process behavior to detect and analyze potential threats based on the behavior of the applications, daemons, and files within the system. As behavior monitoring observes how the software behaves in real-time, it can adapt quickly to new and evolving threats and block them.
44+
- The device must be onboarded to Microsoft Defender for Endpoint.
45+
- [Preview features](/defender-endpoint/preview) must be enabled in the [Microsoft Defender portal](https://security.microsoft.com).
46+
- The device must be in the [Beta channel](/defender-endpoint/mac-updates) (formerly `InsiderFast`).
47+
- The minimum Microsoft Defender for Endpoint version number must be Beta (Insiders-Fast): [101.24042.0002](/defender-endpoint/mac-whatsnew#may-2024-build-101240420008---release-version-2012404280) or newer. The version number refers to the `app_version` (also known as **Platform update**).
48+
- Real-time protection (RTP) must be enabled.
49+
- [Cloud-delivered protection](/defender-endpoint/mac-preferences) must be enabled.
50+
- The device must be explicitly enrolled in the preview program.
5151

52-
## Deployment instructions
52+
## Deployment instructions for behavior monitoring
5353

5454
To deploy behavior monitoring in Microsoft Defender for Endpoint on macOS, you must change the behavior monitoring policy using one of the following methods:
5555

5656
- [Intune](#intune-deployment)
57-
- [JamF or other 3<sup>rd</sup> party MDM](#via-jamf-deployment)
57+
- [JamF or other non-Microsoft MDM](#jamf-deployment)
5858
- [Manually](#manual-deployment)
5959

6060
The following sections describe each of these methods in detail.
@@ -148,7 +148,7 @@ The following sections describe each of these methods in detail.
148148

149149
8. Select **Manage** > **Assignments**. In the **Include** tab, select **Assign to All Users & All devices or to a Device Group or User Group.**
150150

151-
#### Via JamF deployment
151+
#### JamF deployment
152152

153153
1. Copy the following XML to create a _.plist_ file and save it as **Save as BehaviorMonitoring_for_MDE_on_macOS.plist**
154154

@@ -209,19 +209,82 @@ For more information, see: [Resources for Microsoft Defender for Endpoint on mac
209209

210210
See [Behavior Monitoring demonstration](demonstration-behavior-monitoring.md).
211211

212-
### Verifying Behavior Monitoring detection
212+
### Verifying behavior monitoring detections
213213

214214
The existing Microsoft Defender for Endpoint on macOS command line interface can be used to review behavior monitoring details and artifacts.
215215

216216
```bash
217+
217218
sudo mdatp threat list
219+
218220
```
219221

220222
### Frequently Asked Questions (FAQ)
221223

222224
#### What if I see an increase in cpu utilization or memory utilization?
223225

224-
Disable Behavior Monitoring and see if the issue goes away.
226+
Disable behavior monitoring and see if the issue goes away.
227+
228+
- If the issue doesn't go away, it isn't related to behavior monitoring.
229+
- If the issue goes away, download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer), and then contact Microsoft support.
230+
231+
## Network real-time inspection for macOS
232+
233+
> [!IMPORTANT]
234+
> Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
235+
236+
The network real-time inspection (NRI) for macOS feature enhances real-time protection (RTP) by using [behavior monitoring](behavior-monitor-macos.md) in concert with file, process, and other events to detect suspicious activity. Behavior monitoring triggers both telemetry and sample submissions on suspicious files for Microsoft to analyze from the cloud protection backend, and is delivered to the client device, resulting in a removal of the threat.
237+
238+
### Is there an impact on performance?
239+
240+
NRI should have a low impact on network performance. Instead of holding the connection and blocking, NRI makes a copy of the packet as it crosses the network, and NRI performs an asynchronous inspection.
225241

226-
- If the issue doesn't go away, it is not related to Behavior Monitoring.
227-
- If the issue goes away, take an aka.ms/xMDEClientAnalyzer and contact Microsoft support.
242+
> [!NOTE]
243+
> When network real-time inspection (NRI) for macOS is enabled, you might see a slight increase in memory utilization.
244+
245+
### Requirements for NRI for macOS
246+
247+
- The device must be onboarded to Microsoft Defender for Endpoint.
248+
- Preview features must be turned on in the [Microsoft Defender portal](https://security.microsoft.com).
249+
- The device must be in the Beta channel (formerly `InsiderFast`).
250+
- The minimum version number for Defender for Endpoint version number must be Beta (Insiders-Fast): [101.24092.0004](/defender-endpoint/mac-whatsnew#oct-2024-build-101240920004---release-version-2012409240) or newer. The version number refers to the `app version` (also known as Platform update).
251+
- Real-time protection must be enabled.
252+
- Behavior monitoring must be enabled.
253+
- Cloud-delivered protection must be enabled.
254+
- The device must be explicitly enrolled into the preview.
255+
256+
### Deployment instructions for NRI for macOS
257+
258+
1. E-mail us at `[email protected]` with information about your Microsoft Defender for Endpoint OrgID where you would like to have network real-time inspection (NRI) for macOS enabled.
259+
260+
> [!IMPORTANT]
261+
> In order to evaluate NRI for macOS, send email to `[email protected]`. Include your Defender for Endpoint Org ID. We're enabling this feature on a per-request basis for each tenant.
262+
263+
2. Enable behavior monitoring if it's not already enabled:
264+
265+
```Bash
266+
267+
sudo mdatp config behavior-monitoring --value enabled
268+
269+
```
270+
271+
3. Enable network protection in block mode:
272+
273+
```Bash
274+
275+
sudo mdatp config network-protection enforcement-level --value block
276+
277+
```
278+
279+
1. Enable network real-time inspection (NRI):
280+
281+
```Bash
282+
283+
sudo mdatp network-protection remote-settings-override set --value "{\"enableNriMpengineMetadata\" : true}"
284+
285+
286+
```
287+
288+
> [!NOTE]
289+
> While in Public Preview, since the setting is set via a command line, network real-time inspection (NRI) will not persist reboots. You will need to re-enable it.
290+

0 commit comments

Comments
 (0)