Skip to content

Commit 6e5fa2d

Browse files
authored
Merge branch 'main' into patch-19
2 parents 762b56c + 628ab07 commit 6e5fa2d

File tree

98 files changed

+1074
-388
lines changed

Some content is hidden

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

98 files changed

+1074
-388
lines changed

ATPDocs/deploy/remote-calls-sam.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.topic: how-to
1414
Microsoft Defender for Identity mapping for [potential lateral movement paths](/defender-for-identity/understand-lateral-movement-paths) relies on queries that identify local admins on specific machines. These queries are performed with the SAM-R protocol, using the Defender for Identity [Directory Service account](directory-service-accounts.md) you configured.
1515

1616
> [!NOTE]
17-
> This feature can potentially be exploited by an adversary to obtain the Net-NTLM hash of the DSA account due to a Windows limitation in the SAM-R calls that allows downgrading from Kerberos to NTLM.
17+
> This feature can potentially be exploited by an adversary to obtain the NTLM hash of the DSA account due to a Windows limitation in the SAM-R calls that allows downgrading from Kerberos to NTLM.
1818
> The new Defender for Identity sensor (version 3.x) is not affected by this issue as it uses different detection methods.
1919
>
2020
> It is recommended to use a [low privileged DSA account](directory-service-accounts.md#grant-required-dsa-permissions). You can also [contact support](../support.md) to open a case and request to completely disable the [Lateral Movement Paths](../security-assessment-riskiest-lmp.md) data collection capability.

ATPDocs/troubleshooting-known-issues.md

Lines changed: 3 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshooting known issues
33
description: Describes how you can troubleshoot issues in Microsoft Defender for Identity.
4-
ms.date: 09/02/2024
4+
ms.date: 05/08/2025
55
ms.topic: troubleshooting
66
---
77

@@ -117,31 +117,16 @@ The issue can be caused when the trusted root certification authorities certific
117117

118118
Run the following PowerShell cmdlet to verify that the required certificates are installed.
119119

120-
In the following example, use the "DigiCert Baltimore Root" certificate for all customers. In addition, use the "DigiCert Global Root G2" certificate for commercial customers or use the "DigiCert Global Root CA" certificate for US Government GCC High customers, as indicated.
120+
In the following example the "DigiCert Global Root G2" certificate is for commercial customers and the "DigiCert Global Root CA" certificate for US Government GCC High customers, as indicated.
121121

122122
```powershell
123-
# Certificate for all customers
124-
Get-ChildItem -Path "Cert:\LocalMachine\Root" | where { $_.Thumbprint -eq "D4DE20D05E66FC53FE1A50882C78DB2852CAE474"} | fl
125-
126123
# Certificate for commercial customers
127124
Get-ChildItem -Path "Cert:\LocalMachine\Root" | where { $_.Thumbprint -eq "df3c24f9bfd666761b268073fe06d1cc8d4f82a4"} | fl
128125
129126
# Certificate for US Government GCC High customers
130127
Get-ChildItem -Path "Cert:\LocalMachine\Root" | where { $_.Thumbprint -eq "a8985d3a65e5e5c4b2d7d66d40c6dd2fb19c5436"} | fl
131128
```
132129

133-
Output for certificate for all customers:
134-
135-
```Output
136-
Subject : CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
137-
Issuer : CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE
138-
Thumbprint : D4DE20D05E66FC53FE1A50882C78DB2852CAE474
139-
FriendlyName : DigiCert Baltimore Root
140-
NotBefore : 5/12/2000 11:46:00 AM
141-
NotAfter : 5/12/2025 4:59:00 PM
142-
Extensions : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid}
143-
```
144-
145130
Output for certificate for commercial customers certificate:
146131

147132
```Output
@@ -168,19 +153,14 @@ Extensions : {System.Security.Cryptography.Oid, System.Security.Cryptography.O
168153

169154
If you don't see the expected output, use the following steps:
170155

171-
1. Download the following certificates to the Server Core machine. For all customers, download the [Baltimore CyberTrust root](https://cacerts.digicert.com/BaltimoreCyberTrustRoot.crt) certificate.
172-
173-
In addition:
156+
1. Download the following certificates to the machine:
174157

175158
- For commercial customers, download the [DigiCert Global Root G2](https://cacerts.digicert.com/DigiCertGlobalRootG2.crt) certificate
176159
- For US Government GCC High customers, download the [DigiCert Global Root CA](https://cacerts.digicert.com/DigiCertGlobalRootCA.crt) certificate
177160

178161
1. Run the following PowerShell cmdlet to install the certificate.
179162

180163
```powershell
181-
# For all customers, install certificate
182-
Import-Certificate -FilePath "<PATH_TO_CERTIFICATE_FILE>\bc2025.crt" -CertStoreLocation Cert:\LocalMachine\Root
183-
184164
# For commercial customers, install certificate
185165
Import-Certificate -FilePath "<PATH_TO_CERTIFICATE_FILE>\DigiCertGlobalRootG2.crt" -CertStoreLocation Cert:\LocalMachine\Root
186166

ATPDocs/whats-new.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,12 @@ 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+
## May 2025
26+
27+
### New Health Issue
28+
29+
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
30+
2531
## April 2025
2632

2733
### Privileged Identity Tag Now Visible in Defender for Identity Inventory
@@ -47,7 +53,6 @@ For more information, see: [Integrations Defender for Identity and PAM services.
4753

4854
### New Service Account Discovery page
4955

50-
5156
Microsoft Defender for Identity now includes a Service Account Discovery capability, offering you centralized visibility into service accounts across your Active Directory environment.
5257

5358
This update provides:
@@ -60,11 +65,6 @@ This update provides:
6065

6166
For more information, see: [Investigate and protect Service Accounts | Microsoft Defender for Identity](service-account-discovery.md).
6267

63-
64-
### New Health Issue
65-
66-
New [health issue](health-alerts.md#network-configuration-mismatch-for-sensors-running-on-vmware) for cases where sensors running on VMware have network configuration mismatch.
67-
6868
### Enhanced Identity Inventory
6969

7070
The Identities page under *Assets* has been updated to provide better visibility and management of identities across your environment.

CloudAppSecurityDocs/anomaly-detection-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,14 +64,14 @@ Use this detection to control file uploads and downloads in real time with sessi
6464

6565
By enabling file sandboxing, files that according to their metadata and based on proprietary heuristics to be potentially risky, will also be sandbox scanned in a safe environment. The Sandbox scan may detect files that were not detected based on threat intelligence sources.
6666

67-
Defender for Cloud Apps supports malware detection for the following apps:
67+
Defender for Cloud Apps supports "File Sandboxing" malware detection for the following apps:
6868

6969
* Box
7070
* Dropbox
7171
* Google Workspace
7272

7373
> [!NOTE]
74-
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself.
74+
>* Proactively sandboxing will be done in third party applications (*Box*, *Dropbox* etc.). **In *OneDrive* and *SharePoint* files are being scanned and sandboxed as part of the service itself**.
7575
> * In *Box*, *Dropbox*, and *Google Workspace*, Defender for Cloud Apps doesn't automatically block the file, but blocking may be performed according to the app's capabilities and the app's configuration set by the customer.
7676
> * If you're unsure about whether a detected file is truly malware or a false positive, go to the Microsoft Security Intelligence page at [https://www.microsoft.com/wdsi/filesubmission](https://www.microsoft.com/wdsi/filesubmission) and submit the file for further analysis.
7777

CloudAppSecurityDocs/protect-salesforce.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,7 @@ This section provides instructions for connecting Microsoft Defender for Cloud
118118
* **Manage Users**
119119
* **[Query All Files](https://go.microsoft.com/fwlink/?linkid=2106480)**
120120
* **Modify Metadata Through Metadata API Functions**
121+
* **View Setup And Configuration**
121122

122123
If these checkboxes aren't selected, you may need to contact Salesforce to add them to your account.
123124

defender-endpoint/TOC.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,6 @@
4747
href: ios-whatsnew.md
4848
- name: Previous Defender for Endpoint releases (archive)
4949
href: whats-new-mde-archive.md
50-
- name: Minimum requirements
51-
href: minimum-requirements.md
5250
- name: Trial user guide - Defender for Endpoint
5351
href: defender-endpoint-trial-user-guide.md
5452
- name: Pilot and deploy Defender for Endpoint
@@ -178,6 +176,8 @@
178176
items:
179177
- name: Deploy Defender for Endpoint on macOS
180178
items:
179+
- name: Microsoft Defender for Endpoint Prerequisites on macOS
180+
href: microsoft-defender-endpoint-mac-prerequisites.md
181181
- name: Deployment with Microsoft Intune
182182
href: mac-install-with-intune.md
183183
- name: JAMF Pro-based deployment
@@ -311,7 +311,7 @@
311311
href: linux-resources.md
312312
- name: Mobile Threat Defense
313313
items:
314-
- name: Mobile Threat Defense Overview
314+
- name: Mobile Threat Defense overview
315315
href: mtd.md
316316
- name: Deploy
317317
items:

defender-endpoint/attack-surface-reduction.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ ms.service: defender-endpoint
55
ms.subservice: asr
66
ms.localizationpriority: medium
77
audience: ITPro
8-
author: denisebmsft
9-
ms.author: deniseb
8+
author: emmwalshh
9+
ms.author: ewalsh
1010
ms.reviewer: sugamar
1111
manager: deniseb
1212
ms.custom: admindeeplinkDEFENDER
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
- mde-asr
1818
search.appverid: met150
19-
ms.date: 03/28/2025
19+
ms.date: 05/09/2025
2020
---
2121

2222
# Attack surface reduction rules overview
@@ -98,7 +98,7 @@ Also, make sure [Microsoft Defender Antivirus and anti-malware updates](/windows
9898
- Minimum platform release requirement: `4.18.2008.9`
9999
- Minimum engine release requirement: `1.1.17400.5`
100100

101-
For more information and to get your updates, see [Update for Microsoft Defender anti-malware platform](https://support.microsoft.com/help/4052623/update-for-microsoft-defender-antimalware-platform).
101+
For more information and to get your updates, see [Update for Microsoft Defender anti-malware platform](/defender-endpoint/microsoft-defender-antivirus-updates).
102102

103103
### Cases where warn mode isn't supported
104104

@@ -134,6 +134,8 @@ You can set attack surface reduction rules for devices that are running any of t
134134

135135
- Windows 10 Pro, [version 1709](/windows/whats-new/whats-new-windows-10-version-1709) or later
136136
- Windows 10 Enterprise, [version 1709](/windows/whats-new/whats-new-windows-10-version-1709) or later
137+
- Windows 11 Pro, version 21H2 or later
138+
- Windows 11 Enterprise, version 21H2 or later
137139
- Windows Server, [version 1803 (Semi-Annual Channel)](/windows-server/get-started/whats-new-in-windows-server-1803) or later
138140
- Windows Server 2025
139141
- [Windows Server 2022](/windows-server/get-started/whats-new-in-windows-server-2022)

defender-endpoint/behavioral-blocking-containment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
- m365-security
1616
- tier2
1717
search.appverid: met150
18-
ms.date: 03/29/2025
18+
ms.date: 04/25/2025
1919
---
2020

2121
# Behavioral blocking and containment

defender-endpoint/client-behavioral-blocking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection:
1717
- m365-security
1818
- tier2
1919
search.appverid: met150
20-
ms.date: 07/22/2024
20+
ms.date: 04/25/2025
2121
---
2222

2323
# Client behavioral blocking

defender-endpoint/configure-cloud-block-timeout-period-microsoft-defender-antivirus.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure the Microsoft Defender Antivirus cloud block timeout period
3-
description: You can configure how long Microsoft Defender Antivirus will block a file from running while waiting for a cloud determination.
2+
title: Configure the Microsoft Defender Antivirus cloud block time-out period
3+
description: You can configure how long Microsoft Defender Antivirus blocks a file from running while waiting for a cloud determination.
44
ms.service: defender-endpoint
55
ms.localizationpriority: medium
66
author: emmwalshh
@@ -18,7 +18,7 @@ ms.collection:
1818
search.appverid: met150
1919
---
2020

21-
# Configure the cloud block timeout period
21+
# Configure the cloud block time out period
2222

2323
**Applies to:**
2424
- [Microsoft Defender XDR](/defender-xdr)
@@ -33,15 +33,15 @@ search.appverid: met150
3333

3434
When Microsoft Defender Antivirus finds a suspicious file, it can prevent the file from running while it queries the [Microsoft Defender Antivirus cloud service](cloud-protection-microsoft-defender-antivirus.md).
3535

36-
The default period that the file is [blocked](configure-block-at-first-sight-microsoft-defender-antivirus.md) is 10 seconds. If you're a security administrator, you can specify more time to wait before the file is allowed to run. Extending the cloud block timeout period can help ensure there is enough time to receive a proper determination from the Microsoft Defender Antivirus cloud service.
36+
The default period that the file is [blocked](configure-block-at-first-sight-microsoft-defender-antivirus.md) is 10 seconds. If you're a security administrator, you can specify more time to wait before the file is allowed to run. Extending the cloud block time out period can help ensure there's enough time to receive a proper determination from the Microsoft Defender Antivirus cloud service.
3737

38-
## Prerequisites to use the extended cloud block timeout
38+
## Prerequisites to use the extended cloud block time out
3939

40-
[Block at first sight](configure-block-at-first-sight-microsoft-defender-antivirus.md) and its prerequisites must be enabled before you can specify an extended timeout period.
40+
[Block at first sight](configure-block-at-first-sight-microsoft-defender-antivirus.md) and its prerequisites must be enabled before you can specify an extended time out period.
4141

42-
## Specify the extended timeout period using Microsoft Defender for Endpoint Security settings management
42+
## Specify the extended time out period using Microsoft Defender for Endpoint Security settings management
4343

44-
To specify the cloud block timeout period with Microsoft Defender for Endpoint Security settings management:
44+
To specify the cloud block time out period with Microsoft Defender for Endpoint Security settings management:
4545

4646
1. Go to the Microsoft Defender for Endpoint portal ([https://security.microsoft.com](https://security.microsoft.com)) and sign in.
4747
2. Select **Endpoints** > **Configuration management** > **Endpoint security policies**.
@@ -50,29 +50,29 @@ To specify the cloud block timeout period with Microsoft Defender for Endpoint S
5050
5. Under **Select Template** choose: "Microsoft Defender Antivirus".
5151
6. Select **Create policy**.
5252
7. Enter a name and description and select **Next**.
53-
8. From the **Defender** dropdown go to **Cloud Extended Timeout** and toggle it on.
53+
8. From the Defender dropdown, go to **Cloud Extended Timeout** and toggle it on.
5454
9. Specify the extended time, in seconds, from 1 second to 50 seconds. Whatever you specify is added to the default 10 seconds.
5555
10. Select **Next** and **Save** to finish configuring your policy.
5656

57-
## Specify the extended timeout period using Microsoft Intune
57+
## Specify the extended time out period using Microsoft Intune
5858

59-
You can specify the cloud block timeout period with an [endpoint security policy in Microsoft Intune](/mem/intune/protect/endpoint-security-policy).
59+
You can specify the cloud block time out period with an [endpoint security policy in Microsoft Intune](/mem/intune/protect/endpoint-security-policy).
6060

6161
1. Go to the Intune admin center ([https://intune.microsoft.com/](https://intune.microsoft.com/)) and sign in.
6262

6363
2. Select **Endpoint security**, and then under **Manage**, choose **Antivirus**.
6464

6565
3. Select (or create) an antivirus policy.
6666

67-
4. In the **Configuration settings** section, scroll down to **Cloud Extended Timeout** and specify the timeout, in seconds, from 0 to 50 seconds. Whatever you specify is added to the default 10 seconds.
67+
4. In the **Configuration settings** section, scroll down to **Cloud Extended Timeout** and specify the time out, in seconds, from 0 to 50 seconds. Whatever you specify is added to the default 10 seconds.
6868

6969
5. (This step is optional) Make any other changes to your antivirus policy. (Need help? See [Settings for Microsoft Defender Antivirus policy in Microsoft Intune](/mem/intune/protect/antivirus-microsoft-defender-settings-windows).)
7070

7171
6. Choose **Next**, and finish configuring your policy.
7272

73-
## Specify the extended timeout period using Group Policy
73+
## Specify the extended time out period using Group Policy
7474

75-
You can use Group Policy to specify an extended timeout for cloud checks.
75+
You can use Group Policy to specify an extended time out for cloud checks.
7676

7777
1. On your Group Policy management computer, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11))
7878

0 commit comments

Comments
 (0)