Skip to content

Commit 92cb740

Browse files
committed
Update network-protection.md
1 parent 20b45ab commit 92cb740

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

defender-endpoint/network-protection.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ Network protection is enabled per device, which is typically done using your man
180180
> [!NOTE]
181181
> Microsoft Defender Antivirus must be in active mode to enable network protection.
182182
183-
You can enable network protection in `audit` mode or `block` mode. If you want to evaluate the impact of enabling network protection before actually blocking IP addresses or URLs, you can enable network protection in audit mode, and gather data on what would be blocked. Audit mode logs whenever end users connect to an address or site that would otherwise have been blocked by network protection. Note that in order for indicators of compromise (IoC) or Web content filtering (WCF) to work, network protection must be in `block` mode.
183+
You can enable network protection in `audit` mode or `block` mode. If you want to evaluate the impact of enabling network protection before actually blocking IP addresses or URLs, you can enable network protection in audit mode, and gather data on what would be blocked. Audit mode logs whenever end users connect to an address or site that would otherwise have been blocked by network protection. In order for indicators of compromise (IoC) or Web content filtering (WCF) to work, network protection must be in `block` mode.
184184

185185
For information about network protection for Linux and macOS see the following articles:
186186

@@ -189,7 +189,7 @@ For information about network protection for Linux and macOS see the following a
189189

190190
## Advanced hunting
191191

192-
If you're using advanced hunting to identify audit events, you'll have up to 30 days history available from the console. See [Advanced hunting](/defender-xdr/advanced-hunting-overview).
192+
If you're using advanced hunting to identify audit events, you have up to 30 days history available from the console. See [Advanced hunting](/defender-xdr/advanced-hunting-overview).
193193

194194
You can find the audit events in **Advanced hunting** in the Defender for Endpoint portal ([https://security.microsoft.com](https://security.microsoft.com)).
195195

@@ -221,7 +221,7 @@ DeviceEvents
221221
222222
```
223223

224-
The Response category tells you what caused the event, for example:
224+
The Response category tells you what caused the event, as in this example:
225225

226226
| ResponseCategory | Feature responsible for the event |
227227
|:---|:---|
@@ -233,7 +233,7 @@ The Response category tells you what caused the event, for example:
233233

234234
For more information, see [Troubleshoot endpoint blocks](web-protection-overview.md#troubleshoot-endpoint-blocks).
235235

236-
Note that Microsoft Defender SmartScreen events for the Microsoft Edge browser specifically, needs a different query:
236+
Microsoft Defender SmartScreen events for the Microsoft Edge browser specifically needs a different query:
237237

238238
```kusto
239239
@@ -244,13 +244,13 @@ DeviceEvents
244244
245245
```
246246

247-
You can use the resulting list of URLs and IPs to determine what would have been blocked if the device was in block mode, and which feature blocked them. Review each item on the list to identify URLS or IPs whether any are necessary to your environment. If you find any entries that have been audited which are critical to your environment, create an Indicator to allow them in your network. Allow URL / IP indicators take precedence over any block.
247+
You can use the resulting list of URLs and IPs to determine what would be blocked if network protection is set to block mode on the device. You can also see which features would block URLs and IPs. Review the list to identify any URLS or IPs that are necessary for your environment. You can then create an allow indicator for those URLs or IP addresses. Allow indicators take precedence over any blocks.
248248

249-
Once you've created an indicator, you can look at resolving the underlying issue:
249+
Once you've created an indicator, you can look at resolving the underlying issue as follows:
250250

251251
- SmartScreen – request review
252252
- Indicator – modify existing indicator
253-
- MCA – review unsanctioned APP
253+
- MCA – review unsanctioned app
254254
- WCF – request recategorization
255255

256256
Using this data you can make an informed decision on enabling Network protection in Block mode. See [Order of precedence for Network protection blocks](web-protection-overview.md#order-of-precedence).

0 commit comments

Comments
 (0)