mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 08:17:23 +00:00
Merge branch 'master' into martyav-fips-acrolinx
This commit is contained in:
commit
1afb28df7e
@ -241,7 +241,7 @@ Value type is chr. Supported operations include Get, Add, Replace, and Delete.
|
|||||||
Added in Windows 10, version 2004. Specifies the traffic direction to apply this policy to. Default is Outbound. The value can be one of the following:
|
Added in Windows 10, version 2004. Specifies the traffic direction to apply this policy to. Default is Outbound. The value can be one of the following:
|
||||||
|
|
||||||
- Outbound - The rule applies to all outbound traffic
|
- Outbound - The rule applies to all outbound traffic
|
||||||
- nbound - The rule applies to all inbound traffic
|
- Inbound - The rule applies to all inbound traffic
|
||||||
|
|
||||||
If no inbound filter is provided, then by default all unsolicated inbound traffic will be blocked.
|
If no inbound filter is provided, then by default all unsolicated inbound traffic will be blocked.
|
||||||
|
|
||||||
|
Binary file not shown.
After Width: | Height: | Size: 6.5 KiB |
@ -26,6 +26,11 @@ ms.topic: conceptual
|
|||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> Extensive testing of MDE (Microsoft Defender for Endpoint) with new system extensions on macOS 11 (Big Sur) revealed an intermittent issue that impacts macOS devices with specific graphic cards models. In rare cases on impacted macOS devices calls into macOS system extensions were seen resulting in kernel panic. Microsoft is actively working with Apple engineering to clarify profile of impacted devices and to address this macOS issue. In the meantime, if you encounter such a kernel panic, please submit a feedback report to Apple through the Feedback Assistant app.
|
> Extensive testing of MDE (Microsoft Defender for Endpoint) with new system extensions on macOS 11 (Big Sur) revealed an intermittent issue that impacts macOS devices with specific graphic cards models. In rare cases on impacted macOS devices calls into macOS system extensions were seen resulting in kernel panic. Microsoft is actively working with Apple engineering to clarify profile of impacted devices and to address this macOS issue. In the meantime, if you encounter such a kernel panic, please submit a feedback report to Apple through the Feedback Assistant app.
|
||||||
|
|
||||||
|
## 101.13.75
|
||||||
|
|
||||||
|
- Fixed a memory leak in the Endpoint Security system extension when running on mac 11 (Big Sur)
|
||||||
|
- Bug fixes
|
||||||
|
|
||||||
## 101.10.72
|
## 101.10.72
|
||||||
|
|
||||||
- Bug fixes
|
- Bug fixes
|
||||||
|
@ -41,7 +41,7 @@ Ensure that your devices:
|
|||||||
> Windows 10 Version 1809 | [KB 4516077](https://support.microsoft.com/help/4516077/windows-10-update-kb4516077)
|
> Windows 10 Version 1809 | [KB 4516077](https://support.microsoft.com/help/4516077/windows-10-update-kb4516077)
|
||||||
> Windows 10 Version 1903 | [KB 4512941](https://support.microsoft.com/help/4512941/windows-10-update-kb4512941)
|
> Windows 10 Version 1903 | [KB 4512941](https://support.microsoft.com/help/4512941/windows-10-update-kb4512941)
|
||||||
|
|
||||||
- Are onboarded to [Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/what-is-intune) and [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-protection-configure). If you're using Configuration Manager, update your console to the latest version.
|
- Are onboarded to [Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/what-is-intune) and [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-protection-configure) to help remediate threats found by threat and vulnerability management. If you're using Configuration Manager, update your console to the latest version.
|
||||||
- Have at least one security recommendation that can be viewed in the device page
|
- Have at least one security recommendation that can be viewed in the device page
|
||||||
- Are tagged or marked as co-managed
|
- Are tagged or marked as co-managed
|
||||||
|
|
||||||
|
@ -69,6 +69,16 @@ Once you are in the Remediation page, select the remediation activity that you w
|
|||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
> There is a 180 day retention period for completed remediation activities. To keep the Remediation page performing optimally, the remediation activity will be removed 6 months after its completion.
|
> There is a 180 day retention period for completed remediation activities. To keep the Remediation page performing optimally, the remediation activity will be removed 6 months after its completion.
|
||||||
|
|
||||||
|
### Completed by column
|
||||||
|
|
||||||
|
Track who closed the remediation activity with the "Completed by" column on the Remediation page.
|
||||||
|
|
||||||
|
- **Email address**: The email of the person who manually completed the task
|
||||||
|
- **System confirmation**: The task was automatically completed (all devices remediated)
|
||||||
|
- **N/A**: Information is not available because we don't know how this older task was completed
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
### Top remediation activities in the dashboard
|
### Top remediation activities in the dashboard
|
||||||
|
|
||||||
View **Top remediation activities** in the [threat and vulnerability management dashboard](tvm-dashboard-insights.md). Select any of the entries to go to the **Remediation** page. You can mark the remediation activity as completed after the IT admin team remediates the task.
|
View **Top remediation activities** in the [threat and vulnerability management dashboard](tvm-dashboard-insights.md). Select any of the entries to go to the **Remediation** page. You can mark the remediation activity as completed after the IT admin team remediates the task.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user