Skip to content

Commit 33a0c1c

Browse files
authored
Merge branch 'main' into addsi
2 parents 98f864b + 802967b commit 33a0c1c

23 files changed

+376
-90
lines changed

defender-endpoint/configure-advanced-scan-types-microsoft-defender-antivirus.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.custom: nextgen
99
ms.reviewer: pahuijbr
1010
manager: deniseb
1111
ms.subservice: ngp
12-
ms.date: 05/30/2024
12+
ms.date: 07/10/2024
1313
ms.collection:
1414
- m365-security
1515
- tier2
@@ -64,7 +64,7 @@ For details on configuring Microsoft Configuration Manager (current branch), see
6464
|Scan [reparse points](/windows/win32/fileio/reparse-points) <br/> **Scan** \> **Turn on reparse point scanning**|Disabled|Not available <br/>See [Reparse points](/windows/win32/fileio/reparse-points)|
6565
|Scan mapped network drives<br/>**Scan** \> **Run full scan on mapped network drives**|Disabled|`-DisableScanningMappedNetworkDrivesForFullScan`|
6666
|Scan archive files (such as .zip or .rar files). <br/>**Scan** \> **Scan archive files**|Enabled|`-DisableArchiveScanning` <br/><br/>The [extensions exclusion list](configure-extension-file-exclusions-microsoft-defender-antivirus.md) will take precedence over this setting.|
67-
|Scan files on the network <br/>**Scan** \> **Scan network files**|Enabled|`-DisableScanningNetworkFiles`|
67+
|Scan files on the network <br/>**Scan** \> **Scan network files**|Disabled|`-DisableScanningNetworkFiles`|
6868
|Scan packed executables<br/>**Scan** \> **Scan packed executables**|Enabled|Not available <br/><br/>Scan packed executables were removed from the following templates:<br/>- Administrative Templates (.admx) for Windows 11 2022 Update (22H2)<br/>- Administrative Templates (.admx) for Windows 11 October 2021 Update (21H2)|
6969
|Scan removable drives during full scans only<br/>**Scan** \> **Scan removable drives**|Disabled|`-DisableRemovableDriveScanning`|
7070
|Specify the level of subfolders within an archive folder to scan <p>**Scan** \> **Specify the maximum depth to scan archive files**|0|Not available|

defender-endpoint/configure-device-connectivity.md

Lines changed: 16 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.reviewer: pahuijbr
1515
search.appverid: MET150
1616
audience: ITPro
17-
ms.date: 06/14/2024
17+
ms.date: 06/11/2024
1818
---
1919

2020
# Onboarding devices using streamlined connectivity for Microsoft Defender for Endpoint
@@ -27,44 +27,26 @@ ms.date: 06/14/2024
2727
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
2828
- [Microsoft Defender XDR](/defender-xdr)
2929

30-
The Microsoft Defender for Endpoint service might require the use of proxy configurations to report diagnostic data and communicate data to the service. Prior to the availability of the streamlined connectivity method, other URLs were required and Defender for Endpoint static IP ranges weren't supported. For more information on preparing your environment, see [STEP 1: Configure your network environment to ensure connectivity with Defender for Endpoint service](configure-environment.md).
30+
The Defender for Endpoint client might require the use of proxied connections to relevant cloud services. This article describes the streamlined device connectivity method, the prerequisites and provides additional information for verifying connectivity using the new destination(s).
3131

32-
This article describes the streamlined device connectivity method and how to onboard new devices to use a simpler deployment and management of Defender for Endpoint cloud connectivity services. For more information on migrating previously onboarded devices, see [Migrating devices to streamlined connectivity](migrate-devices-streamlined.md).
32+
To simplify network configuration and management, you now have the option of onboarding new devices to Defender for Endpoint using a reduced URL set or static IP ranges. For more information on migrating previously onboarded devices, see [Migrating devices to streamlined connectivity](migrate-devices-streamlined.md).
3333

34-
To simplify network configuration and management, you now have the option of onboarding devices to Defender for Endpoint using a reduced URL set or static IP ranges. See the [streamlined URL list](https://aka.ms/MDE-streamlined-urls).
34+
The Defender for Endpoint-recognized simplified domain: `*.endpoint.security.microsoft.com` consolidates connectivity to the following core Defender for Endpoint services:
3535

36-
The Defender for Endpoint-recognized simplified domain: `*.endpoint.security.microsoft.com` replaces the following core Defender for Endpoint services:
36+
- Cloud-delivered protection
37+
- Malware sample submission storage
38+
- Auto-IR sample storage
39+
- Defender for Endpoint command & control
40+
- Defender for Endpoint cyber and diagnostic data
3741

38-
- Cloud Protection/MAPS
39-
- Malware Sample Submission Storage
40-
- Auto-IR Sample Storage
41-
- Defender for Endpoint Command & Control
42-
- EDR Cyberdata
42+
For more information on preparing your environment and the updated list of destinations, see [STEP 1: Configure your network environment to ensure connectivity with Defender for Endpoint service](configure-environment.md).
4343

4444
To support network devices without hostname resolution or wildcard support, you can alternatively configure connectivity using dedicated Defender for Endpoint static IP ranges. For more information, see [Configure connectivity using static IP ranges](#option-2-configure-connectivity-using-static-ip-ranges).
4545

4646
> [!NOTE]
4747
> - The streamlined connectivity method will **not change how Microsoft Defender for Endpoint functions on a device nor will it change the end-user experience**. Only the URLs or IPs that a device uses to connect to the service will change.
4848
> - There currently is no plan to deprecate the old, consolidated service URLs. Devices onboarded with "standard" connectivity will continue to function. It is important to ensure connectivity to `*.endpoint.security.microsoft.com` is and remains possible, as future services will require it. This new URL is included in all required URL lists.
49-
50-
## Consolidated services
51-
52-
The following Defender for Endpoint URLs consolidated under the simplified domain should no longer be required for connectivity if `*.endpoint.security.microsoft.com` is allowed and devices are onboarded using the streamlined onboarding package. You need to maintain connectivity with other required services not consolidated that are relevant to your organization (for example, CRL, SmartScreen/Network Protection, and Windows Update).
53-
54-
For the updated list of required URLs, see [STEP 1: Configure your network environment to ensure connectivity with Defender for Endpoint service](configure-environment.md).
55-
56-
> [!IMPORTANT]
57-
> If you are configuring using IP ranges, you will need to separately configure the EDR cyberdata service. This service is not consolidated on an IP level.
58-
59-
| Category | Consolidated URLs |
60-
|------------|---------------|
61-
| MAPS: cloud-delivered protection | `*.wdcp.microsoft.com` <br/>`*.wd.microsoft.com` |
62-
| Cloud protection & <br/>security intelligence updates for macOS and Linux | `unitedstates.x.cp.wd.microsoft.com` <br/>`europe.x.cp.wd.microsoft.com` <br/>`unitedkingdom.x.cp.wd.microsoft.com`<br/> `x.cp.wd.microsoft.com` <br/>`https://www.microsoft.com/security/encyclopedia/adlpackages.aspx` |
63-
| Malware Sample Submission Storage | `ussus1eastprod.blob.core.windows.net` <br/>`ussus2eastprod.blob.core.windows.net` <br/>`ussus3eastprod.blob.core.windows.net` <br/>`ussus4eastprod.blob.core.windows.net` <br/>`wsus1eastprod.blob.core.windows.net` <br/>`wsus2eastprod.blob.core.windows.net` <br/>`ussus1westprod.blob.core.windows.net` <br/>`ussus2westprod.blob.core.windows.net` <br/>`ussus3westprod.blob.core.windows.net` <br/>`ussus4westprod.blob.core.windows.net` <br/>`wsus1westprod.blob.core.windows.net`<br/>`wsus2westprod.blob.core.windows.net` <br/>`usseu1northprod.blob.core.windows.net` <br/>`wseu1northprod.blob.core.windows.net` <br/>`usseu1westprod.blob.core.windows.net` <br/>`wseu1westprod.blob.core.windows.net` <br/>`ussuk1southprod.blob.core.windows.net` <br/>`wsuk1southprod.blob.core.windows.net` <br/>`ussuk1westprod.blob.core.windows.net` <br/>`wsuk1westprod.blob.core.windows.net` |
64-
| Defender for Endpoint Auto-IR Sample Storage | `automatedirstrprdcus.blob.core.windows.net` <br/>`automatedirstrprdeus.blob.core.windows.net` <br/>`automatedirstrprdcus3.blob.core.windows.net` <br/>`automatedirstrprdeus3.blob.core.windows.net` <br/>`automatedirstrprdneu.blob.core.windows.net` <br/>`automatedirstrprdweu.blob.core.windows.net` <br/>`automatedirstrprdneu3.blob.core.windows.net` <br/>`automatedirstrprdweu3.blob.core.windows.net` <br/>`automatedirstrprduks.blob.core.windows.net` <br/>`automatedirstrprdukw.blob.core.windows.net` |
65-
| Defender for Endpoint Command and Control | `winatp-gw-cus.microsoft.com` <br/>`winatp-gw-eus.microsoft.com` <br/>`winatp-gw-cus3.microsoft.com` <br/>`winatp-gw-eus3.microsoft.com` <br/>`winatp-gw-neu.microsoft.com` <br/>`winatp-gw-weu.microsoft.com` <br/>`winatp-gw-neu3.microsoft.com` <br/>`winatp-gw-weu3.microsoft.com` <br/>`winatp-gw-uks.microsoft.com` <br/>`winatp-gw-ukw.microsoft.com` |
66-
| EDR Cyberdata | `events.data.microsoft.com` <br/>`us-v20.events.data.microsoft.com` <br/> `eu-v20.events.data.microsoft.com` <br/>`uk-v20.events.data.microsoft.com` |
67-
49+
> - Connections to the service leverage certificate pinning and TLS. It is not supported to "break and inspect" traffic. In addition, connections are initiated from a device context, not a user context. Enforcing proxy (user) authentication will disallow (break) connectivity in most cases.
6850
6951
## Before you begin
7052

@@ -140,9 +122,9 @@ Streamlined connectivity allows you to use the following option to configure clo
140122

141123
#### Option 1: Configure connectivity using the simplified domain
142124

143-
Configure your environment to allow connections with the simplified Defender for Endpoint domain: `*.endpoint.security.microsoft.com`. For more information, see [Configure your network environment to ensure connectivity with Defender for Endpoint service](configure-environment.md).
125+
Configure your environment to allow connections to the simplified Defender for Endpoint domain: `*.endpoint.security.microsoft.com`. For more information, see [Configure your network environment to ensure connectivity with Defender for Endpoint service](configure-environment.md).
144126

145-
You must maintain connectivity with remaining required services listed under the [updated list](https://aka.ms/MDE-streamlined-urls). For example, Certification Revocation List, Windows update, SmartScreen.
127+
You must maintain connectivity with remaining required services listed under the [updated list](https://aka.ms/MDE-streamlined-urls). For example, the certification revocation list, Windows Update, SmartScreen services may also need to be accessible dependent on your current networking infrastructure and patching approach.
146128

147129
#### Option 2: Configure connectivity using static IP ranges
148130

@@ -160,11 +142,10 @@ In order to stay up to date on IP ranges, it's recommended to refer to the follo
160142

161143
| Service tag name | Defender for Endpoint services included |
162144
|:---|:---|
163-
| MicrosoftDefenderForEndpoint | MAPS, Malware Sample Submission Storage, Auto-IR Sample Storage, Command and Control. |
164-
| OneDsCollector | EDR Cyberdata <br/><br/> Note: The traffic under this service tag isn't limited to Defender for Endpoint and can include diagnostic data traffic for other Microsoft services. |
165-
166-
The following table lists the current static IP ranges covered by the MicrosoftDefenderForEndpoint service tag. For latest list, refer to the Azure service tags.
145+
| MicrosoftDefenderForEndpoint | Cloud-delivered protection, malware sample submission storage, Auto-IR sample storage, Defender for Endpoint command and control. |
146+
| OneDsCollector | Defender for Endpoint cyber and diagnostic data <br/><br/> Note: The traffic under this service tag isn't limited to Defender for Endpoint and can include diagnostic data traffic for other Microsoft services. |
167147

148+
The following table lists the current static IP ranges covered by the MicrosoftDefenderForEndpoint service tag. For latest list, refer to the [Azure service tags](/azure/virtual-network/service-tags-overview) documentation.
168149

169150
|Geo|IP Ranges|
170151
|------|-------|

defender-endpoint/microsoft-defender-endpoint-linux.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 07/05/2024
18+
ms.date: 07/11/2024
1919
---
2020

2121
# Microsoft Defender for Endpoint on Linux
@@ -102,7 +102,11 @@ In general you need to take the following steps:
102102
- Fedora 33-38
103103

104104
- Rocky 8.7 and higher
105+
- Rocky 9.2 and higher
106+
105107
- Alma 8.4 and higher
108+
- Alma 9.2 and higher
109+
106110
- Mariner 2
107111

108112
> [!NOTE]

defender-endpoint/supported-capabilities-by-platform.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.collection:
1313
ms.topic: conceptual
1414
ms.subservice: onboard
1515
search.appverid: met150
16-
ms.date: 08/26/2022
16+
ms.date: 07/11/2024
1717
---
1818

1919
# Supported Microsoft Defender for Endpoint capabilities by platform
@@ -50,26 +50,28 @@ The following table gives information about the supported Microsoft Defender for
5050
|[EDR Block](edr-in-block-mode.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
5151
|[Passive Mode](microsoft-defender-antivirus-compatibility.md)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
5252
|Sense detection sensor|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
53-
|Endpoint & network device discovery|![Yes.](media/svg/check-yes.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
53+
|Endpoint & network device discovery|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg) <sup>[5]</sup>|![No](media/svg/check-no.svg)|![No](media/svg/check-no.svg)|
5454
|[Vulnerability management](/defender-vulnerability-management/defender-vulnerability-management)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|![Yes.](media/svg/check-yes.svg)|
5555
||||||
5656
|**Response** | | | ||
5757
|[Automated Investigation & Response (AIR)](automated-investigations.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![No](media/svg/check-no.svg) | ![No](media/svg/check-no.svg) |
5858
|[Device response capabilities: collect investigation package ](respond-machine-alerts.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) <sup>[3]</sup> | ![Yes.](media/svg/check-yes.svg) <sup>[3]</sup> |
59-
|[Device response capabilities: run AV scan](respond-machine-alerts.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) |
59+
|[Device response capabilities: run antivirus scan](respond-machine-alerts.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) |
6060
|[Device isolation](respond-machine-alerts.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) |
6161
|File response capabilities: collect file, deep analysis, block file, stop, and quarantine processes | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![No](media/svg/check-no.svg) | ![No](media/svg/check-no.svg) |
6262
|[Live Response](live-response.md) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) | ![Yes.](media/svg/check-yes.svg) |
6363

64-
<sup>[1]</sup> Refers to the modern, unified solution for Windows Server 2012 R2 and 2016. For more information, see [Onboard Windows Servers to the Defender for Endpoint service](configure-server-endpoints.md).
64+
<sup>[1]</sup> Refers to the modern, unified solution for Windows Server 2012 R2 and Windows Server 2016. For more information, see [Onboard Windows Servers to the Defender for Endpoint service](configure-server-endpoints.md).
6565

6666
<sup>[2]</sup> Feature is currently in preview ([Microsoft Defender for Endpoint preview features](/defender-xdr/preview))
6767

6868
<sup>[3]</sup> Response capabilities using Live Response [2]
6969

7070
<sup>[4]</sup> Collect file only, using Live Response [2]
7171

72+
<sup>[5]</sup> Endpoint & network device discovery is supported on Windows Server 2019 or later, Windows 10, and Windows 11
73+
7274
> [!NOTE]
73-
> Windows 7, 8.1, Windows Server 2008 R2 include support for the EDR sensor, and AV using System Center Endpoint Protection (SCEP).
75+
> Windows 7, 8.1, Windows Server 2008 R2 include support for the EDR sensor, and antivirus using System Center Endpoint Protection (SCEP).
7476
7577
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/whats-new-in-microsoft-defender-endpoint.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ For more information on Microsoft Defender for Endpoint on specific operating sy
5252

5353
## July 2024
5454

55-
- (GA) Learning hub resources, including Microsoft Defender XDR Ninja training, learning paths, and training modules have moved from the Microsoft Defender portal to [learn.microsoft.com](https://go.microsoft.com/fwlink/?linkid=2273118). Browse the [list of learning paths](/training/browse/?products=m365-ems-cloud-app-security%2Cdefender-for-cloud-apps%2Cdefender-identity%2Cm365-information-protection%2Cm365-threat-protection%2Cmdatp%2Cdefender-office365&expanded=m365%2Coffice-365), and filter by product, role, level, and subject.
55+
- (GA) Learning hub resources have moved from the Microsoft Defender portal to [learn.microsoft.com](https://go.microsoft.com/fwlink/?linkid=2273118). Access Microsoft Defender XDR Ninja training, learning paths, training modules and more. Browse the [list of learning paths](/training/browse/?products=m365-ems-cloud-app-security%2Cdefender-for-cloud-apps%2Cdefender-identity%2Cm365-information-protection%2Cm365-threat-protection%2Cmdatp%2Cdefender-office365&expanded=m365%2Coffice-365), and filter by product, role, level, and subject.
56+
5657

5758
## June 2024
5859

defender-office-365/attack-simulation-training-end-user-notifications.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.collection:
1212
- tier2
1313
description: Admins can learn how to create end-user notification email messages for Attack simulation training in Microsoft Defender for Office 365 Plan 2.
1414
search.appverid: met150
15-
ms.date: 3/11/2024
15+
ms.date: 06/14/2024
1616
appliesto:
1717
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 2</a>
1818
---
@@ -147,6 +147,9 @@ On the details flyout from the **Tenant notifications** tab only, select **Edit
147147

148148
- **Use from default**: Select an available template to start with. You can modify the text and layout in the editing area. To reset the notification back to the default text and layout of the template, select **Reset to default**.
149149

150+
> [!TIP]
151+
> To add images, copy (CTRL+C) and paste (CTRL+V) the image into the editor on the **Text** tab. The editor automatically converts the image to Base64 as part of the HTML code.
152+
150153
- **Code** tab: You can view and modify the HTML code directly.
151154

152155
You can preview the results by selecting **Preview email** at the top of the page.

0 commit comments

Comments
 (0)