Skip to content

Commit cce555d

Browse files
authored
Merge branch 'main' into patch-2
2 parents 60019e8 + 52acd42 commit cce555d

File tree

5 files changed

+35
-28
lines changed

5 files changed

+35
-28
lines changed

defender-endpoint/defender-endpoint-false-positives-negatives.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -212,9 +212,11 @@ To define exclusions across Microsoft Defender for Endpoint, perform the followi
212212

213213
- [Create "allow" indicators for Microsoft Defender for Endpoint](#indicators-for-defender-for-endpoint)
214214
- [Define exclusions for Microsoft Defender Antivirus](#exclusions-for-microsoft-defender-antivirus)
215+
- For Attack Surface Reduction Rule exclusions [Configure attack surface reduction per-rule exclusions](/defender-endpoint/attack-surface-reduction-rules-deployment-test#configure-attack-surface-reduction-per-rule-exclusions) or you can leverage [ASR rule only exclusions](/defender-endpoint/enable-attack-surface-reduction#exclude-files-and-folders-from-attack-surface-reduction-rules)
215216

216217
> [!NOTE]
217218
> Microsoft Defender Antivirus exclusions apply only to antivirus protection, not across other Microsoft Defender for Endpoint capabilities. To exclude files broadly, use [custom indicators](indicators-overview.md) for Microsoft Defender for Endpoint and exclusions for Microsoft Defender Antivirus.
219+
> ASR Rules can leverage ASR Rule Exclusions - where the exclusions apply to all ASR Rules; ASR per Rule Exclusions; Defender AV exclusions; as well as allow indicators defined in Custom Indicators.
218220

219221
The procedures in this section describe how to define indicators and exclusions.
220222

defender-endpoint/evaluate-mdav-using-gp.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -180,13 +180,13 @@ Disable local administrator AV settings such as exclusions, and enforce the poli
180180
| --- | --- |
181181
| Prevent users and apps from accessing dangerous websites | Enabled, Block |
182182
| This settings controls whether Network Protection is allowed to be configured into block or audit mode on Windows Server | Enabled |
183-
| Allow Network Protection Down Level | Network protection is enabled downlevel |
184-
| Allow Datagram Processing On Win Server | Datagram processing on Windows Server is enabled |
185-
| Disable DNS over TCP parsing | DNS over TCP parsing is enabled |
186-
| Disable HTTP parsing | HTTP parsing is enabled |
187-
| Disable SSH parsing | SSH parsing is enabled |
188-
| Disable TLS parsing | TLS parsing is enabled |
189-
| Enable DNS Sinkhole | DNS Sinkhole is enabled |
183+
184+
To enable Network Protection for Windows Servers, for now, please use Powershell:
185+
186+
| OS | Powershell cmdlet |
187+
| --- | --- |
188+
| Windows Server 2012 R2Windows Server 2022 and later | set-MpPreference -AllowNetworkProtectionOnWinServer $true |
189+
| Windows Server 2016 and Windows Server 2012 R2 [unified MDE client](/defender-endpoint/update-agent-mma-windows#upgrade-to-the-new-unified-agent-for-defender-for-endpoint) | set-MpPreference -AllowNetworkProtectionOnWinServer $true and set-MpPreference -AllowNetworkProtectionDownLevel $true
190190

191191
## Attack Surface Reduction Rules
192192

@@ -207,7 +207,7 @@ Disable local administrator AV settings such as exclusions, and enforce the poli
207207
| c0033c00-d16d-4114-a5a0-dc9b3a7d2ceb<br><br>**Note:** ( \[PREVIEW\] Block use of copied or impersonated system tools) | 1 (Block) |
208208
| d3e037e1-3eb8-44c8-a917-57927947596d<br><br>**Note:** (Block JavaScript or VBScript from launching downloaded executable content) | 1 (Block) |
209209
| 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2<br><br>**Note:** (Block credential stealing from the Windows local security authority subsystem) | 1 (Block) |
210-
| a8f5898e-1dc8-49a9-9878-85004b8a61e6<br><br>**Note:** (Block Webshell creation for Servers) | 1 (Block) |
210+
| a8f5898e-1dc8-49a9-9878-85004b8a61e6<br><br>**Note:** (Block Web shell creation for Servers) | 1 (Block) |
211211
| 3b576869-a4ec-4529-8536-b80a7769e899<br><br>**Note:** (Block Office applications from creating executable content) | 1 (Block) |
212212
| b2b3f03d-6a65-4f7b-a9c7-1c7ef74a9ba4<br><br>**Note:** (Block untrusted and unsigned processes that run from USB) | 1 (Block) |
213213
| 75668c1f-73b5-4cf0-bb93-3ecf5cb7cc84<br><br>**Note:** (Block Office applications from injecting code into other processes) | 1 (Block) |

defender-endpoint/microsoft-defender-antivirus-compatibility.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,12 +207,13 @@ You can use one of several methods to confirm the state of Microsoft Defender An
207207
- [Use Windows PowerShell to confirm that antivirus protection is running](#use-windows-powershell-to-confirm-that-antivirus-protection-is-running).
208208

209209
> [!IMPORTANT]
210-
> Beginning with [platform version 4.18.2208.0 and later](microsoft-defender-antivirus-updates.md#platform-and-engine-releases): If a server has been onboarded to Microsoft Defender for Endpoint, the "Turn off Windows Defender" [group policy](configure-endpoints-gp.md#update-endpoint-protection-configuration) setting no longer completely disables Windows Defender Antivirus on Windows Server 2012 R2 and later. Instead, it place Microsoft Defender Antivirus into passive mode. In addition, the [tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) allows a switch to active mode, but not to passive mode.
210+
> Beginning with [platform version 4.18.2208.0 and later](microsoft-defender-antivirus-updates.md#platform-and-engine-releases): If a server has been onboarded to Microsoft Defender for Endpoint, the "Turn off Windows Defender" [group policy](configure-endpoints-gp.md#update-endpoint-protection-configuration) setting no longer completely disables Windows Defender Antivirus on Windows Server 2012 R2 and later. Instead, it places Microsoft Defender Antivirus into passive mode. In addition, the [tamper protection](prevent-changes-to-security-settings-with-tamper-protection.md) allows a switch to active mode, but not to passive mode.
211211
>
212212
> - If "Turn off Windows Defender" is already in place before onboarding to Microsoft Defender for Endpoint, Microsoft Defender Antivirus remains disabled.
213213
> - To switch Microsoft Defender Antivirus to passive mode, even if it was disabled before onboarding, you can apply the [ForceDefenderPassiveMode configuration](switch-to-mde-phase-2.md#set-microsoft-defender-antivirus-to-passive-mode-on-windows-server) with a value of `1`. To place it into active mode, switch this value to `0` instead.
214214
>
215215
> Note the modified logic for `ForceDefenderPassiveMode` when tamper protection is enabled: Once Microsoft Defender Antivirus is toggled to active mode, tamper protection prevents it from going back into passive mode even when `ForceDefenderPassiveMode` is set to `1`.
216+
>Microsoft Defender for Endpoint – EDR response actions always operate in Passive mode, even if EDR is in block mode.
216217
217218
### Use the Windows Security app to identify your antivirus app
218219

exposure-management/configure-data-connectors.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,29 @@ ms.date: 11/06/2024
1111

1212
# Configure your data connectors
1313

14+
[Microsoft Security Exposure Management](microsoft-security-exposure-management.md) consolidates security posture data from all your digital assets, enabling you to map your attack surface and focus your security efforts on areas at greatest risk. Data from Microsoft Security products like Microsoft Defender for Endpoint, Microsoft Defender for Identity, Microsoft Defender for Cloud, Microsoft Entra ID, and others are automatically ingested and consolidated within Exposure Management. You can further enrich and extend this data by connecting to a range of external data sources.
15+
16+
## Prerequisites
17+
18+
The following prerequisites are required to integrate external data connecters to Microsoft Security Exposure Management.
19+
20+
### Roles & permissions
21+
22+
For full access to connect and disconnect the data connectors you need one of the following Microsoft Entra ID roles:
23+
24+
- Global Admin (read and write permissions)
25+
- Security Admin (read and write permissions)
26+
- Security Operator (read and limited write permissions)
27+
28+
To view the status of the connectors, you can use one of the following roles:
29+
30+
- Global Reader (read permissions)
31+
- Security Reader (read permissions)
32+
33+
You can find more details about the permission levels here, [Prerequisites, and support](prerequisites.md).
34+
35+
## Establish a connection
36+
1437
To establish a connection with any of the supported external products, follow these steps:
1538

1639
1. Complete the applicable prerequisite steps for your external data connectors.

exposure-management/overview-data-connectors.md

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -38,25 +38,6 @@ Data Connectors in Microsoft Security Exposure Management is currently in public
3838
> [!NOTE]
3939
> During the preview phase, use of the data connectors feature is free. Once data connectors become generally available, there will be a consumption-based cost for each non-Microsoft data connector based on number of assets retrieved from the connected security tool. The charge will be according to volume of ingested billable assets, where a billable asset is any asset (device, container, identity, application) on which data is reported from that connector. Each connector will have clearly defined applicable assets and guidance on how to determine the numbers. Pricing will be announced before billing of external connectors starts at GA.
4040
41-
## Prerequisites
42-
43-
The following prerequisites are required to integrate external data connecters to Microsoft Security Exposure Management.
44-
45-
### Roles & permissions
46-
47-
For full access to connect and disconnect the data connectors you need one of the following Microsoft Entra ID roles:
48-
49-
- Global Admin (read and write permissions)
50-
- Security Admin (read and write permissions)
51-
- Security Operator (read and limited write permissions)
52-
53-
To view the status of the connectors, you can use one of the following roles:
54-
55-
- Global Reader (read permissions)
56-
- Security Reader (read permissions)
57-
58-
You can find more details about the permission levels here, [Prerequisites, and support](prerequisites.md).
59-
6041
## Next steps
6142

6243
[Configure your data connectors](configure-data-connectors.md).

0 commit comments

Comments
 (0)