mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-22 02:07:24 +00:00
Merge branch 'master' into lomayor-ta-report-guide
This commit is contained in:
Louie Mayor
commit
9ab261f57d
@ -74,7 +74,7 @@ The following is a list of functions performed by the Device HealthAttestation C
|
||||
|
||||
<strong>DHA-Enabled MDM (Device HealthAttestation enabled device management solution)</strong>
|
||||
<p style="margin-left: 20px">Device HealthAttestation enabled (DHA-Enabled) device management solution is a device management tool that is integrated with the DHA feature.</p>
|
||||
<p style="margin-left: 20px">DHA-Enabled device management solutions enable enterprise IT managers to raise the security protection bar for their managed devices based on hardware (TPM) protected data that can be trusted even if a device is compromized by advanced security threats or running a malicious (jailbroken) operating system.</p>
|
||||
<p style="margin-left: 20px">DHA-Enabled device management solutions enable enterprise IT managers to raise the security protection bar for their managed devices based on hardware (TPM) protected data that can be trusted even if a device is compromised by advanced security threats or running a malicious (jailbroken) operating system.</p>
|
||||
<p style="margin-left: 20px">The following list of operations are performed by DHA-Enabled-MDM:</p>
|
||||
<ul>
|
||||
<li>Enables the DHA feature on a DHA-Enabled device</li>
|
||||
@ -195,10 +195,10 @@ The following diagram shows the Device HealthAttestation configuration service p
|
||||
|
||||
<p style="margin-left: 20px">The following list shows some examples of supported values. For the complete list of status see <a href="#device-healthattestation-csp-status-and-error-codes" data-raw-source="[Device HealthAttestation CSP status and error codes](#device-healthattestation-csp-status-and-error-codes)">Device HealthAttestation CSP status and error codes</a>.</p>
|
||||
|
||||
- 0 - (HEALTHATTESTATION\_CERT\_RETRI_UNINITIALIZED): DHA-CSP is preparing a request to get a new DHA-EncBlob from DHA-Service
|
||||
- 1 - (HEALTHATTESTATION\_CERT\_RETRI_REQUESTED): DHA-CSP is waiting for the DHA-Service to respond back, and issue a DHA-EncBlob to the device
|
||||
- 0 - (HEALTHATTESTATION\_CERT\_RETRIEVAL_UNINITIALIZED): DHA-CSP is preparing a request to get a new DHA-EncBlob from DHA-Service
|
||||
- 1 - (HEALTHATTESTATION\_CERT\_RETRIEVAL_REQUESTED): DHA-CSP is waiting for the DHA-Service to respond back, and issue a DHA-EncBlob to the device
|
||||
- 2 - (HEALTHATTESTATION\_CERT\_RETRIEVAL_FAILED): A valid DHA-EncBlob could not be retrieved from the DHA-Service for reasons other than discussed in the DHA error/status codes
|
||||
- 3 - (HEALTHATTESTATION\_CERT\_RETRI_COMPLETE): DHA-Data is ready for pick up
|
||||
- 3 - (HEALTHATTESTATION\_CERT\_RETRIEVAL_COMPLETE): DHA-Data is ready for pick up
|
||||
|
||||
<a href="" id="forceretrieve"></a>**ForceRetrieve** (Optional)
|
||||
<p style="margin-left: 20px">Instructs the client to initiate a new request to DHA-Service, and get a new DHA-EncBlob (a summary of the boot state that is issued by DHA-Service). This option should only be used if the MDM server enforces a certificate freshness policy, which needs to force a device to get a fresh encrypted blob from DHA-Service.</p>
|
||||
@ -220,7 +220,7 @@ The following diagram shows the Device HealthAttestation configuration service p
|
||||
<a href="" id="correlationid"></a>**CorrelationId** (Required)
|
||||
<p style="margin-left: 20px">Identifies a unique device health attestation session. CorrelationId is used to correlate DHA-Service logs with the MDM server events and Client event logs for debug and troubleshooting.</p>
|
||||
|
||||
<p style="margin-left: 20px">Value type is integer, the minimum value is - 2,147,483,648 and the maximun value is 2,147,483,647. The supported operation is Get.</p>
|
||||
<p style="margin-left: 20px">Value type is integer, the minimum value is - 2,147,483,648 and the maximum value is 2,147,483,647. The supported operation is Get.</p>
|
||||
|
||||
<a href="" id="hasendpoint"></a>**HASEndpoint** (Optional)
|
||||
<p style="margin-left: 20px">Identifies the fully qualified domain name (FQDN) of the DHA-Service that is assigned to perform attestation. If an FQDN is not assigned, DHA-Cloud (Microsoft owned and operated cloud service) will be used as the default attestation service.</p>
|
||||
@ -359,8 +359,8 @@ The following example shows a sample call that triggers collection and verificat
|
||||
|
||||
After the client receives the health attestation request, it sends a response. The following list describes the responses, along with a recommended action to take.
|
||||
|
||||
- If the response is HEALTHATTESTATION\_CERT_RETRI_COMPLETE (3) then proceed to the next section.
|
||||
- If the response is HEALTHATTESTATION_CERT_RETRI_REQUESTED (1) or HEALTHATTESTATION_CERT_RETRI_UNINITIALIZED (0) wait for an alert, then proceed to the next section.
|
||||
- If the response is HEALTHATTESTATION\_CERT_RETRIEVAL_COMPLETE (3) then proceed to the next section.
|
||||
- If the response is HEALTHATTESTATION_CERT_RETRIEVAL_REQUESTED (1) or HEALTHATTESTATION_CERT_RETRIEVAL_UNINITIALIZED (0) wait for an alert, then proceed to the next section.
|
||||
|
||||
Here is a sample alert that is issued by DHA_CSP:
|
||||
|
||||
@ -830,7 +830,7 @@ Each of these are described in further detail in the following sections, along w
|
||||
<tr>
|
||||
<td style="vertical-align:top">3</td>
|
||||
<td style="vertical-align:top">HEALTHATTESTATION_CERT_RETRIEVAL_COMPLETE</td>
|
||||
<td style="vertical-align:top">This state signifies that the device failed to retrieve DHA-EncBlob from DHA-Server.</td>
|
||||
<td style="vertical-align:top">This state signifies that the device has successfully retrieved DHA-EncBlob from the DHA-Server.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td style="vertical-align:top">4</td>
|
||||
|
||||
@ -199,6 +199,7 @@
|
||||
- name: Data handling and privacy in Update Compliance
|
||||
href: update/update-compliance-privacy.md
|
||||
- name: Update Compliance schema reference
|
||||
href: update/update-compliance-schema.md
|
||||
items:
|
||||
- name: WaaSUpdateStatus
|
||||
href: update/update-compliance-schema-waasupdatestatus.md
|
||||
|
||||
@ -48,6 +48,9 @@ Each MDM Policy links to its documentation in the CSP hierarchy, providing its e
|
||||
|**System/**[**ConfigureTelemetryOptInSettingsUx**](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-system#system-configuretelemetryoptinsettingsux) | 1 - Disable Telemetry opt-in Settings | (in Windows 10, version 1803 and later) Determines whether end-users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy or the effective diagnostic data level on devices might not be sufficient. |
|
||||
|**System/**[**AllowDeviceNameInDiagnosticData**](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata) | 1 - Allowed | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or set to 0 (Disabled), Device Name will not be sent and will not be visible in Update Compliance, showing `#` instead. |
|
||||
|
||||
> [!NOTE]
|
||||
> If you use Microsoft Intune, set the **ProviderID** to *MS DM Server*. If you use another MDM product, check with its vendor. See also [DMClient CSP](https://docs.microsoft.com/windows/client-management/mdm/dmclient-csp).
|
||||
|
||||
### Group Policies
|
||||
|
||||
All Group Policies that need to be configured for Update Compliance are under **Computer Configuration>Administrative Templates>Windows Components\Data Collection and Preview Builds**. All of these policies must be in the *Enabled* state and set to the defined *Value* below.
|
||||
|
||||
@ -19,7 +19,11 @@ ms.topic: article
|
||||
|
||||
The Update Compliance Configuration Script is the recommended method of configuring devices to send data to Microsoft for use with Update Compliance. The script configures device policies via Group Policy, ensures that required services are running, and more.
|
||||
|
||||
You can [**download the script here**](https://www.microsoft.com/en-us/download/details.aspx?id=101086). Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting.
|
||||
> [!NOTE]
|
||||
> The Update Compliance configuration script does not offer options to configure Delivery Optimization. You have to do that separately.
|
||||
|
||||
|
||||
You can download the script from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=101086). Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting.
|
||||
|
||||
## How the script is organized
|
||||
|
||||
|
||||
@ -20,6 +20,9 @@ When the visualizations provided in the default experience don't fulfill your re
|
||||
|
||||
The table below summarizes the different tables that are part of the Update Compliance solution. To learn how to navigate Azure Monitor Logs to find this data, see [Get started with log queries in Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/log-query/get-started-queries).
|
||||
|
||||
> [!NOTE]
|
||||
> Data is collected daily. The TimeGenerated field shows the time data was collected. It's added by Log Analytics when data is collected. Device data from the past 28 days is collected, even if no new data has been generated since the last time. LastScan is a clearer indicator of data freshness (that is, the last time the values were updated), while TimeGenerated indicates the freshness of data within Log Analytics.
|
||||
|
||||
|Table |Category |Description |
|
||||
|--|--|--|
|
||||
|[**WaaSUpdateStatus**](update-compliance-schema-waasupdatestatus.md) |Device record |This table houses device-centric data and acts as the device record for Update Compliance. Each record provided in daily snapshots map to a single device in a single tenant. This table has data such as the current device's installed version of Windows, whether it is on the latest available updates, and whether the device needs attention. |
|
||||
|
||||
@ -186,7 +186,7 @@ This group includes all domain controllers in an Active Directory forest. Domain
|
||||
|
||||
All interactive, network, dial-up, and authenticated users are members of the Everyone group. This special identity group gives wide access to system resources. Whenever a user logs on to the network, the user is automatically added to the Everyone group.
|
||||
|
||||
On computers running Windows 2000 and earlier, the Everyone group included the Anonymous Logon group as a default member, but as of Windows Server 2003, the Everyone group contains only Authenticated Users and Guest; and it no longer includes Anonymous Logon by default (although this can be changed).
|
||||
On computers running Windows 2000 and earlier, the Everyone group included the Anonymous Logon group as a default member, but as of Windows Server 2003, the Everyone group contains only Authenticated Users and Guest; and it no longer includes Anonymous Logon by default (although this can be changed, using Registry Editor, by going to the **Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa** key and setting the value of **everyoneincludesanonymous** DWORD to 1).
|
||||
|
||||
Membership is controlled by the operating system.
|
||||
|
||||
|
||||
@ -458,7 +458,7 @@ contoso.sharepoint.com,contoso.internalproxy1.com|contoso.visualstudio.com,conto
|
||||
Value format without proxy:
|
||||
|
||||
```console
|
||||
contoso.sharepoint.com,|contoso.visualstudio.com,|contoso.onedrive.com
|
||||
contoso.sharepoint.com,|contoso.visualstudio.com,|contoso.onedrive.com,
|
||||
```
|
||||
|
||||
### Protected domains
|
||||
|
||||
@ -256,9 +256,17 @@
|
||||
#### [Resources](microsoft-defender-atp/mac-resources.md)
|
||||
|
||||
|
||||
|
||||
|
||||
### [Microsoft Defender Advanced Threat Protection for iOS]()
|
||||
#### [Overview of Microsoft Defender Advanced Threat Protection for iOS](microsoft-defender-atp/microsoft-defender-atp-ios.md)
|
||||
|
||||
#### [Deploy]()
|
||||
##### [App-based deployment](microsoft-defender-atp/ios-install.md)
|
||||
|
||||
#### [Configure]()
|
||||
##### [Configure iOS features](microsoft-defender-atp/ios-configure-features.md)
|
||||
|
||||
|
||||
### [Microsoft Defender Advanced Threat Protection for Linux]()
|
||||
#### [Overview of Microsoft Defender ATP for Linux](microsoft-defender-atp/microsoft-defender-atp-linux.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Collect diagnostic data of Microsoft Defender Antivirus
|
||||
description: Use a tool to collect data to troubleshoot Microsoft Defender Antivirus
|
||||
keywords: troubleshoot, error, fix, update compliance, oms, monitor, report, Microsoft Defender av
|
||||
keywords: troubleshoot, error, fix, update compliance, oms, monitor, report, Microsoft Defender av, group policy object, setting, diagnostic data
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
@ -25,7 +25,7 @@ manager: dansimp
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Microsoft Defender AV.
|
||||
This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you might encounter when using the Microsoft Defender AV.
|
||||
|
||||
> [!NOTE]
|
||||
> As part of the investigation or response process, you can collect an investigation package from a device. Here's how: [Collect investigation package from devices](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/respond-machine-alerts#collect-investigation-package-from-devices).
|
||||
@ -54,7 +54,7 @@ On at least two devices that are experiencing the same issue, obtain the .cab di
|
||||
4. A .cab file will be generated that contains various diagnostic logs. The location of the file will be specified in the output in the command prompt. By default, the location is `C:\ProgramData\Microsoft\Microsoft Defender\Support\MpSupportFiles.cab`.
|
||||
|
||||
> [!NOTE]
|
||||
> To redirect the cab file to a a different path or UNC share, use the following command: `mpcmdrun.exe -GetFiles -SupportLogLocation <path>` <br/>For more information see [Redirect diagnostic data to a UNC share](#redirect-diagnostic-data-to-a-unc-share).
|
||||
> To redirect the cab file to a a different path or UNC share, use the following command: `mpcmdrun.exe -GetFiles -SupportLogLocation <path>` <br/>For more information, see [Redirect diagnostic data to a UNC share](#redirect-diagnostic-data-to-a-unc-share).
|
||||
|
||||
5. Copy these .cab files to a location that can be accessed by Microsoft support. An example could be a password-protected OneDrive folder that you can share with us.
|
||||
|
||||
@ -78,7 +78,7 @@ mpcmdrun.exe -GetFiles -SupportLogLocation <path>
|
||||
|
||||
Copies the diagnostic data to the specified path. If the path is not specified, the diagnostic data will be copied to the location specified in the Support Log Location Configuration.
|
||||
|
||||
When the SupportLogLocation parameter is used, a folder structure as below will be created in the destination path:
|
||||
When the SupportLogLocation parameter is used, a folder structure like as follows will be created in the destination path:
|
||||
|
||||
```Dos
|
||||
<path>\<MMDD>\MpSupport-<hostname>-<HHMM>.cab
|
||||
@ -86,13 +86,30 @@ When the SupportLogLocation parameter is used, a folder structure as below will
|
||||
|
||||
| field | Description |
|
||||
|:----|:----|
|
||||
| path | The path as specified on the commandline or retrieved from configuration
|
||||
| MMDD | Month Day when the diagnostic data was collected (eg 0530)
|
||||
| hostname | the hostname of the device on which the diagnostic data was collected.
|
||||
| HHMM | Hours Minutes when the diagnostic data was collected (eg 1422)
|
||||
| path | The path as specified on the command line or retrieved from configuration
|
||||
| MMDD | Month and day when the diagnostic data was collected (for example, 0530)
|
||||
| hostname | The hostname of the device on which the diagnostic data was collected
|
||||
| HHMM | Hours and minutes when the diagnostic data was collected (for example, 1422)
|
||||
|
||||
> [!NOTE]
|
||||
> When using a File share please make sure that account used to collect the diagnostic package has write access to the share.
|
||||
> When using a file share please make sure that account used to collect the diagnostic package has write access to the share.
|
||||
|
||||
## Specify location where diagnostic data is created
|
||||
|
||||
You can also specify where the diagnostic .cab file will be created using a Group Policy Object (GPO).
|
||||
|
||||
1. Open the Local Group Policy Editor and find the SupportLogLocation GPO at: `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\SupportLogLocation`
|
||||
|
||||
1. Select **Define the directory path to copy support log files**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Inside the policy editor, select **Enabled**.
|
||||
|
||||
4. Specify the directory path where you want to copy the support log files in the **Options** field.
|
||||
|
||||
5. Select **OK** or **Apply**.
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 314 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
@ -11,7 +11,7 @@ ms.localizationpriority: medium
|
||||
author: denisebmsft
|
||||
ms.author: deniseb
|
||||
ms.custom: nextgen
|
||||
ms.date: 07/22/2020
|
||||
ms.date: 09/30/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -28,14 +28,13 @@ manager: dansimp
|
||||
> [!NOTE]
|
||||
> By default, Microsoft Defender Antivirus checks for an update 15 minutes before the time of any scheduled scans. You can [Manage the schedule for when protection updates should be downloaded and applied](manage-protection-update-schedule-microsoft-defender-antivirus.md) to override this default.
|
||||
|
||||
|
||||
In addition to always-on real-time protection and [on-demand](run-scan-microsoft-defender-antivirus.md) scans, you can set up regular, scheduled scans.
|
||||
|
||||
You can configure the type of scan, when the scan should occur, and if the scan should occur after a [protection update](manage-protection-updates-microsoft-defender-antivirus.md) or if the endpoint is being used. You can also specify when special scans to complete remediation should occur.
|
||||
|
||||
This topic describes how to configure scheduled scans with Group Policy, PowerShell cmdlets, and WMI. You can also configure schedules scans with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/protect/deploy-use/endpoint-antimalware-policies#scheduled-scans-settings) or [Microsoft Intune](https://docs.microsoft.com/intune/device-restrictions-configure).
|
||||
This article describes how to configure scheduled scans with Group Policy, PowerShell cmdlets, and WMI. You can also configure schedules scans with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/protect/deploy-use/endpoint-antimalware-policies#scheduled-scans-settings) or [Microsoft Intune](https://docs.microsoft.com/intune/device-restrictions-configure).
|
||||
|
||||
To configure the Group Policy settings described in this topic:
|
||||
## To configure the Group Policy settings described in this article
|
||||
|
||||
1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
@ -201,7 +200,7 @@ Scan | Specify the time for a daily quick scan | Specify the number of minutes a
|
||||
Use the following cmdlets:
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -ScanScheduleQuickTime
|
||||
Set-MpPreference -ScanScheduleQuickScanTime
|
||||
```
|
||||
|
||||
See [Use PowerShell cmdlets to configure and run Microsoft Defender Antivirus](use-powershell-cmdlets-microsoft-defender-antivirus.md) and [Defender cmdlets](https://technet.microsoft.com/itpro/powershell/windows/defender/index) for more information on how to use PowerShell with Microsoft Defender Antivirus.
|
||||
@ -229,9 +228,7 @@ Location | Setting | Description | Default setting (if not configured)
|
||||
---|---|---|---
|
||||
Signature updates | Turn on scan after Security intelligence update | A scan will occur immediately after a new protection update is downloaded | Enabled
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
## See also
|
||||
- [Prevent or allow users to locally modify policy settings](configure-local-policy-overrides-microsoft-defender-antivirus.md)
|
||||
- [Configure and run on-demand Microsoft Defender Antivirus scans](run-scan-microsoft-defender-antivirus.md)
|
||||
- [Configure Microsoft Defender Antivirus scanning options](configure-advanced-scan-types-microsoft-defender-antivirus.md)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: deniseb
|
||||
author: denisebmsft
|
||||
ms.date: 09/28/2020
|
||||
ms.date: 09/30/2020
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
@ -87,22 +87,7 @@ You can configure the following levels of automation:
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Regarding automation levels and default settings:
|
||||
> - If your tenant already has device groups defined, then the automation level settings are not changed for those device groups.
|
||||
> - If your tenant was onboarded to Microsoft Defender for Endpoint *before* August 16, 2020, and you have not defined a device group, your organization's default setting is **Semi - require approval for any remediation**.
|
||||
> - If your tenant was onboarded to Microsoft Defender for Endpoint *before* August 16, 2020, and you do have a device group defined, you also have an **Ungrouped devices (default)** device group that is set to **Semi - require approval for any remediation**.
|
||||
> - If your tenant was onboarded to Microsoft Defender for Endpoint *on or after* August 16, 2020, and you have not defined a device group, your orgnaization's default setting is **Full - remediate threats automatically**.
|
||||
> - If your tenant was onboarded to Microsoft Defender for Endpoint *on or after* August 16, 2020, and you do have a device group defined, you also have an **Ungrouped devices (default)** device group that is set to **Full - remediate threats automatically**.
|
||||
> - To change an automation level, **[edit your device groups](configure-automated-investigations-remediation.md#set-up-device-groups)**.
|
||||
|
||||
|
||||
### A few points to keep in mind
|
||||
|
||||
- Your level of automation is determined by your device group settings. To learn more, see [Set up device groups](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-automated-investigations-remediation#set-up-device-groups).
|
||||
|
||||
- If your Microsoft Defender for Endpoint tenant was created before August 16, 2020, then you have a default device group that is configured for semi-automatic remediation. In this case, some or all remediation actions for malicious entities require approval. Such actions are listed on the **Pending actions** tab in the [Action center](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center#the-action-center). You can set your [device groups](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-automated-investigations-remediation#set-up-device-groups) to use full automation so that no user approval is needed.
|
||||
|
||||
- If your Microsoft Defender for Endpoint tenant was created on or after August 16, 2020, then you have a default device group that is configured for full automation. In this case, remediation actions are taken automatically for entities that are considered to be malicious. Such actions are listed on the **History** tab in the [Action center](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center#the-action-center).
|
||||
> If your tenant already has device groups defined, then the automation level settings are not changed for those device groups.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 612 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 326 KiB |
@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Configure Microsoft Defender ATP for iOS features
|
||||
ms.reviewer:
|
||||
description: Describes how to deploy Microsoft Defender ATP for iOS features
|
||||
keywords: microsoft, defender, atp, ios, configure, features, ios
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Configure Microsoft Defender ATP for iOS features
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **PUBLIC PREVIEW EDITION**
|
||||
>
|
||||
> This documentation is for a pre-release solution. The guidelines and the solution are subject to change between now and its general availability.
|
||||
>
|
||||
> As with any pre-release solution, remember to exercise caution when determining the target population for your deployments.
|
||||
|
||||
|
||||
## Configure custom indicators
|
||||
Microsoft Defender ATP for iOS enables admins to configure custom indicators on
|
||||
iOS devices as well. Refer to [Manage
|
||||
indicators](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators)
|
||||
on how to configure custom indicators
|
||||
|
||||
## Web Protection
|
||||
By default, Microsoft Defender ATP for iOS includes and enables the web
|
||||
protection feature. [Web
|
||||
protection](web-protection-overview.md) helps
|
||||
to secure devices against web threats and protect users from phishing attacks.
|
||||
|
||||
>[!NOTE]
|
||||
>Microsoft Defender ATP for iOS would use a VPN in order to provide the Web Protection feature. This is not a regular VPN and is a local/self-looping VPN that does not take traffic outside the device.
|
||||
|
||||
@ -0,0 +1,80 @@
|
||||
---
|
||||
title: App-based deployment for Microsoft Defender ATP for iOS
|
||||
ms.reviewer:
|
||||
description: Describes how to deploy Microsoft Defender ATP for iOS using an app
|
||||
keywords: microsoft, defender, atp, ios, app, installation, deploy, uninstallation, intune
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# App-based deployment for Microsoft Defender ATP for iOS
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **PUBLIC PREVIEW EDITION**
|
||||
>
|
||||
> This documentation is for a pre-release solution. The guidelines and the solution are subject to change between now and its general availability.
|
||||
>
|
||||
> As with any pre-release solution, remember to exercise caution when determining the target population for your deployments.
|
||||
|
||||
Microsoft Defender ATP for iOS is currently available as a preview app on TestFlight, Apple's beta testing platform. In GA, it will be available on the Apple App store.
|
||||
|
||||
Deployment devices need to be enrolled on Intune Company portal. Refer to
|
||||
[Enroll your
|
||||
device](https://docs.microsoft.com/mem/intune/enrollment/ios-enroll) to
|
||||
learn more about Intune device enrollment
|
||||
|
||||
## Before you begin
|
||||
|
||||
- Ensure you have access to [Microsoft Endpoint manager admin
|
||||
center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
|
||||
- Ensure iOS enrollment is done for your users. Users need to have Microsoft Defender ATP
|
||||
license assigned in order to use Microsoft Defender ATP for iOS. Refer [Assign licenses to
|
||||
users](https://docs.microsoft.com/azure/active-directory/users-groups-roles/licensing-groups-assign)
|
||||
for instructions on how to assign licenses.
|
||||
|
||||
|
||||
## Deployment steps
|
||||
|
||||
To install Microsoft Defender ATP for iOS, end-users can visit
|
||||
<https://aka.ms/defenderios> on their iOS devices. This link will open the
|
||||
TestFlight application on their device or prompt them to install TestFlight. On
|
||||
the TestFlight app, follow the onscreen instructions to install Microsoft
|
||||
Defender ATP.
|
||||
|
||||
|
||||
|
||||
|
||||
## Complete onboarding and check status
|
||||
|
||||
1. Once Microsoft Defender ATP for iOS has been installed on the device, you
|
||||
will see the app icon.
|
||||
|
||||
|
||||
|
||||
2. Tap the Microsoft Defender ATP app icon and follow the on-screen
|
||||
instructions to complete the onboarding steps. The details include end-user
|
||||
acceptance of iOS permissions required by Microsoft Defender ATP for iOS.
|
||||
|
||||
3. Upon successful onboarding, the device will start showing up on the Devices
|
||||
list in Microsoft Defender Security Center.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
## Next Steps
|
||||
|
||||
[Configure Microsoft Defender ATP for iOS features](ios-configure-features.md)
|
||||
@ -31,7 +31,7 @@ ms.topic: conceptual
|
||||
|
||||
## Summary
|
||||
|
||||
In enterprise organizations, Microsoft Defender ATP for Mac can be managed through a configuration profile that is deployed by using one of several management tools. Preferences that are managed by your security operations team take precedence over preferences that are set locally on the device. Users in your organization are not able to change preferences that are set through the configuration profile.
|
||||
In enterprise organizations, Microsoft Defender ATP for Mac can be managed through a configuration profile that is deployed by using one of several management tools. Preferences that are managed by your security operations team take precedence over preferences that are set locally on the device. Changing the preferences that are set through the configuration profile requires escalated privileges and is not available for users without administrative permissions.
|
||||
|
||||
This article describes the structure of the configuration profile, includes a recommended profile that you can use to get started, and provides instructions on how to deploy the profile.
|
||||
|
||||
|
||||
@ -32,9 +32,9 @@ ms.topic: conceptual
|
||||
|
||||
|
||||
The public preview of Microsoft Defender ATP for iOS will offer protection
|
||||
against phishing and unsafe network connections from websites, emails and apps.
|
||||
against phishing and unsafe network connections from websites, emails, and apps.
|
||||
All alerts will be available through a single pane of glass in the Microsoft
|
||||
Defender Security Center, giving security teams a centralized view of threats on
|
||||
Defender Security Center. The portal gives security teams a centralized view of threats on
|
||||
iOS devices along with other platforms.
|
||||
|
||||
## Pre-requisites
|
||||
@ -72,4 +72,5 @@ iOS devices along with other platforms.
|
||||
|
||||
## Next steps
|
||||
|
||||
Microsoft Defender for Endpoint capabilities for iOS will be released into public preview in the coming weeks. At that time, we will publish additional deployment and configuration information. Please check back here in a few weeks.
|
||||
- [Deploy Microsoft Defender ATP for iOS](ios-install.md)
|
||||
- [Configure Microsoft Defender ATP for iOS features](ios-configure-features.md)
|
||||
@ -107,13 +107,12 @@ The hardware requirements for Microsoft Defender ATP on devices are the same for
|
||||
|
||||
### Other supported operating systems
|
||||
- Android
|
||||
- Linux (currently, Microsoft Defender ATP is only available in the Public Preview Edition for Linux)
|
||||
- Linux
|
||||
- macOS
|
||||
|
||||
> [!NOTE]
|
||||
> You'll need to know the exact Linux distributions and versions of Android and macOS that are compatible with Microsoft Defender ATP for the integration to work.
|
||||
>
|
||||
> Also note that Microsoft Defender ATP is currently only available in the Public Preview Edition for Linux.
|
||||
|
||||
|
||||
|
||||
### Network and data storage and configuration requirements
|
||||
|
||||
@ -51,6 +51,7 @@ Turn on the preview experience setting to be among the first to try upcoming fea
|
||||
|
||||
The following features are included in the preview release:
|
||||
- [Microsoft Defender ATP for iOS](microsoft-defender-atp-ios.md) <br> Microsoft Defender ATP now adds support for iOS. Learn how to install, configure, and use Microsoft Defender ATP for iOS.
|
||||
|
||||
- [Microsoft Defender ATP for Android](microsoft-defender-atp-android.md) <br> Microsoft Defender ATP now adds support for Android. Learn how to install, configure, and use Microsoft Defender ATP for Android.
|
||||
|
||||
- [Threat & Vulnerability supported operating systems and platforms](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/tvm-supported-os) <BR> Ensure that you meet the operating system or platform requisites for Threat & Vulnerability Management so the activities in your devices are properly accounted for. Threat & Vulnerability Management supports Windows 7, Windows 10 1607-1703, Windows 10 1709+, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, Windows Server 2019. <BR> <BR> Secure Configuration Assessment (SCA) supports Windows 10 1709+, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, and Windows Server 2019.
|
||||
|
||||
@ -84,6 +84,9 @@ Tip: You can deploy a policy without selecting any category on a device group. T
|
||||
>[!NOTE]
|
||||
>If you are removing a policy or changing device groups at the same time, this might cause a delay in policy deployment.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Blocking the "Uncategorized" category may lead to unexpected and undesired results.
|
||||
|
||||
### Allow specific websites
|
||||
|
||||
It is possible to override the blocked category in web content filtering to allow a single site by creating a custom indicator policy. The custom indicator policy will supersede the web content filtering policy when it is applied to the device group in question.
|
||||
|
||||
@ -25,7 +25,7 @@ ms.date: 10/30/2019
|
||||
|
||||
Beginning with the Windows 10 November 2019 update (build 18363), Microsoft Intune enables customers to deploy and run business critical Win32 applications as well as Windows components that are normally blocked in S mode (ex. PowerShell.exe) on their Intune-managed Windows 10 in S mode devices.
|
||||
|
||||
With Intune, IT Pros can now configure their managed S mode devices using a Windows Defender Application Control (WDAC) supplemental policy that expands the S mode base policy to authorize the apps their business uses. This feature changes the S mode security posture from “every app is Microsoft-verified" to “every app is verified by Microsoft or your organization”.
|
||||
With Intune, IT Pros can now configure their managed S mode devices using a Windows Defender Application Control (WDAC) supplemental policy that expands the S mode base policy to authorize the apps their business uses. This feature changes the S mode security posture from "every app is Microsoft-verified" to "every app is verified by Microsoft or your organization".
|
||||
|
||||
Refer to the below video for an overview and brief demo.
|
||||
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4mlcp]
|
||||
@ -57,7 +57,7 @@ The general steps for expanding the S mode base policy on your Intune-managed de
|
||||
```powershell
|
||||
Set-RuleOption -FilePath "<path>\SupplementalPolicy.xml>" -Option 3 –Delete
|
||||
```
|
||||
This deletes the ‘audit mode’ qualifier.
|
||||
This deletes the 'audit mode' qualifier.
|
||||
- Since you'll be signing your policy, you must authorize the signing certificate you will use to sign the policy and optionally one or more additional signers that can be used to sign updates to the policy in the future. For more information, refer to Section 2, Sign policy. Use Add-SignerRule to add the signing certificate to the WDAC policy:
|
||||
|
||||
```powershell
|
||||
@ -88,9 +88,9 @@ Refer to [Intune Standalone - Win32 app management](https://docs.microsoft.com/i
|
||||
|
||||
## Optional: Process for Deploying Apps using Catalogs
|
||||
|
||||
Your supplemental policy can be used to significantly relax the S mode base policy, but there are security trade-offs you must consider in doing so. For example, you can use a signer rule to trust an external signer, but that will authorize all apps signed by that certificate, which may include apps you don’t want to allow as well.
|
||||
Your supplemental policy can be used to significantly relax the S mode base policy, but there are security trade-offs you must consider in doing so. For example, you can use a signer rule to trust an external signer, but that will authorize all apps signed by that certificate, which may include apps you don't want to allow as well.
|
||||
|
||||
Instead of authorizing signers external to your organization, Intune has added new functionality to make it easier to authorize existing applications (without requiring repackaging or access to the source code) through the use of signed catalogs. This works for apps which may be unsigned or even signed apps when you don’t want to trust all apps that may share the same signing certificate.
|
||||
Instead of authorizing signers external to your organization, Intune has added new functionality to make it easier to authorize existing applications (without requiring repackaging or access to the source code) through the use of signed catalogs. This works for apps which may be unsigned or even signed apps when you don't want to trust all apps that may share the same signing certificate.
|
||||
|
||||
The basic process is to generate a catalog file for each app using Package Inspector, then sign the catalog files using the DGSS or a custom PKI. Use the Add-SignerRule PowerShell cmdlet as shown above to authorize the catalog signing certificate in the supplemental policy. After that, IT Pros can use the standard Intune app deployment process outlined above. Refer to [Deploy catalog files to support Windows Defender Application Control](deploy-catalog-files-to-support-windows-defender-application-control.md) for more in-depth guidance on generating catalogs.
|
||||
|
||||
@ -184,8 +184,6 @@ Below is a sample policy that allows kernel debuggers, PowerShell ISE, and Regis
|
||||
In order to revert users to an unmodified S mode policy, an IT Pro can remove a user or users from the targeted Intune group which received the policy, which will trigger a removal of both the policy and the authorization token from the device.
|
||||
|
||||
IT Pros also have the choice of deleting a supplemental policy through Intune.
|
||||
> [!Note]
|
||||
> This feature currently has a known bug which occurs when an S mode supplemental policy is deleted through Intune, in which the policy is not immediately removed from the devices to which it was deployed. A fix is expected in the 2D update in late February 2020. In the meantime, IT Pros are recommended to update their policy with the below 'empty' policy which makes no changes to S mode.
|
||||
|
||||
```xml
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: WDAC and AppLocker Overview
|
||||
description: Compare Windows application control technologies.
|
||||
keywords: security, malware
|
||||
keywords: security, malware, allow-list, block-list
|
||||
ms.assetid: 8d6e0474-c475-411b-b095-1c61adb2bdbb
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ author: denisebmsft
|
||||
ms.reviewer: isbrahm
|
||||
ms.author: deniseb
|
||||
manager: dansimp
|
||||
ms.date: 04/15/2020
|
||||
ms.date: 09/30/2020
|
||||
ms.custom: asr
|
||||
---
|
||||
|
||||
@ -29,58 +29,48 @@ Windows 10 includes two technologies that can be used for application control de
|
||||
|
||||
## Windows Defender Application Control
|
||||
|
||||
WDAC was introduced with Windows 10 and allows organizations to control what drivers and applications are allowed to run on their Windows 10 clients. WDAC was designed as a security feature under the [servicing criteria](https://www.microsoft.com/msrc/windows-security-servicing-criteria) defined by the Microsoft Security Response Center (MSRC).
|
||||
|
||||
> [!NOTE]
|
||||
> Prior to Windows 10, version 1709, Windows Defender Application Control was known as configurable code integrity (CCI) policies.
|
||||
WDAC was introduced with Windows 10 and allows organizations to control which drivers and applications are allowed to run on their Windows 10 clients. WDAC was designed as a security feature under the [servicing criteria](https://www.microsoft.com/msrc/windows-security-servicing-criteria) defined by the Microsoft Security Response Center (MSRC).
|
||||
|
||||
WDAC policies apply to the managed computer as a whole and affects all users of the device. WDAC rules can be defined based on:
|
||||
|
||||
- Attributes of the codesigning certificate(s) used to sign an app and its binaries;
|
||||
- Attributes of the app's binaries that come from the signed metadata for the files, such as Original Filename and version, or the hash of the file;
|
||||
- The reputation of the app as determined by Microsoft's Intelligent Security Graph;
|
||||
- The identity of the process that initiated the installation of the app and its binaries (managed installer);
|
||||
- The path from which the app or file is launched (beginning with Windows 10 version 1903);
|
||||
- The process that launched the app or binary.
|
||||
- Attributes of the codesigning certificate(s) used to sign an app and its binaries
|
||||
- Attributes of the app's binaries that come from the signed metadata for the files, such as Original Filename and version, or the hash of the file
|
||||
- The reputation of the app as determined by Microsoft's [Intelligent Security Graph](use-windows-defender-application-control-with-intelligent-security-graph.md)
|
||||
- The identity of the process that initiated the installation of the app and its binaries ([managed installer](use-windows-defender-application-control-with-managed-installer.md))
|
||||
- The [path from which the app or file is launched](select-types-of-rules-to-create.md#more-information-about-filepath-rules) (beginning with Windows 10 version 1903)
|
||||
- The process that launched the app or binary
|
||||
|
||||
Note that prior to Windows 10, version 1709, Windows Defender Application Control was known as configurable code integrity (CCI). WDAC was also one of the features which comprised the now-defunct term 'Device Guard'.
|
||||
|
||||
### WDAC System Requirements
|
||||
|
||||
WDAC policies can only be created on computers running Windows 10 build 1903+ on any SKU, pre-1903 Windows 10 Enterprise, or Windows Server 2016 and above.
|
||||
WDAC policies can be applied to computers running any edition of Windows 10 or Windows Server 2016 and above via a Mobile Device Management (MDM) solution like Intune, a management interface like Configuration Manager, or a script host like PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 Enterprise edition or Windows Server 2016 and above, but cannot deploy policies to machines running non-Enterprise SKUs of Windows 10.
|
||||
WDAC policies can only be created on devices running Windows 10 build 1903+ on any SKU, pre-1903 Windows 10 Enterprise, or Windows Server 2016 and above.
|
||||
|
||||
WDAC policies can be applied to devices running any edition of Windows 10 or Windows Server 2016 and above via a Mobile Device Management (MDM) solution like Intune, a management interface like Configuration Manager, or a script host like PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 Enterprise edition or Windows Server 2016 and above, but cannot deploy policies to devices running non-Enterprise SKUs of Windows 10.
|
||||
|
||||
## AppLocker
|
||||
|
||||
AppLocker was introduced with Windows 7 and allows organizations to control what applications their users are allowed to run on their Windows clients. AppLocker provides security value as a defense in depth feature and helps end users avoid running unapproved software on their computers.
|
||||
AppLocker was introduced with Windows 7 and allows organizations to control which applications are allowed to run on their Windows clients. AppLocker helps to prevent end users from running unapproved software on their computers, but it does not meet the servicing criteria for being a security feature.
|
||||
|
||||
AppLocker policies can apply to all users on a computer or to individual users and groups. AppLocker rules can be defined based on:
|
||||
|
||||
- Attributes of the codesigning certificate(s) used to sign an app and its binaries;
|
||||
- Attributes of the app's binaries that come from the signed metadata for the files, such as Original Filename and version, or the hash of the file;
|
||||
- The path from which the app or file is launched (beginning with Windows 10 version 1903).
|
||||
- Attributes of the codesigning certificate(s) used to sign an app and its binaries
|
||||
- Attributes of the app's binaries that come from the signed metadata for the files, such as Original Filename and version, or the hash of the file
|
||||
- The path from which the app or file is launched
|
||||
|
||||
### AppLocker System Requirements
|
||||
|
||||
AppLocker policies can only be configured on and applied to computers that are running on the supported versions and editions of the Windows operating system. For more info, see [Requirements to Use AppLocker](applocker/requirements-to-use-applocker.md).
|
||||
AppLocker policies can only be configured on and applied to devices that are running on the supported versions and editions of the Windows operating system. For more info, see [Requirements to Use AppLocker](applocker/requirements-to-use-applocker.md).
|
||||
AppLocker policies can be deployed using Group Policy or MDM.
|
||||
|
||||
## Choose when to use WDAC or AppLocker
|
||||
|
||||
Although either AppLocker or WDAC can be used to control application execution on Windows 10 clients, the following factors can help you decide when to use each of the technologies.
|
||||
Generally, it is recommended that customers who are able to implement application control using WDAC rather than AppLocker do so. WDAC is undergoing continual improvements and will be getting added support from Microsoft management platforms. AppLocker is a legacy technology which will continue to receive security fixes but will not undergo new feature improvements.
|
||||
|
||||
### WDAC is best when:
|
||||
|
||||
- You are adopting application control primarily for security reasons.
|
||||
- Your application control policy can be applied to all users on the managed computers.
|
||||
- All of the devices you wish to manage are running Windows 10.
|
||||
|
||||
### AppLocker is best when:
|
||||
In some cases, however, AppLocker may be the more appropriate technology for your organization. AppLocker is best when:
|
||||
|
||||
- You have a mixed Windows operating system (OS) environment and need to apply the same policy controls to Windows 10 and earlier versions of the OS.
|
||||
- You need to apply different policies for different users or groups on a shared computer.
|
||||
- You are using application control to help users avoid running unapproved software, but you do not require a solution designed as a security feature.
|
||||
- You do not wish to enforce application control on application files such as DLLs or drivers.
|
||||
- You need to apply different policies for different users or groups on shared computers.
|
||||
|
||||
## When to use both WDAC and AppLocker together
|
||||
|
||||
AppLocker can also be deployed as a complement to WDAC to add user- or group-specific rules for shared device scenarios where its important to prevent some users from running specific apps.
|
||||
As a best practice, you should enforce WDAC at the most restrictive level possible for your organization, and then you can use AppLocker to fine-tune the restrictions to an even lower level.
|
||||
AppLocker can also be deployed as a complement to WDAC to add user- or group-specific rules for shared device scenarios where it is important to prevent some users from running specific apps.
|
||||
As a best practice, you should enforce WDAC at the most restrictive level possible for your organization, and then you can use AppLocker to further fine-tune the restrictions.
|
||||
|
||||
@ -86,7 +86,7 @@ The following table identifies and defines terms used throughout this guide.
|
||||
| Certificate-based isolation | A way to add devices that cannot use Kerberos V5 authentication to an isolated domain, by using an alternate authentication technique. Every device in the isolated domain and the devices that cannot use Kerberos V5 are provided with a device certificate that can be used to authenticate with each other. Certificate-based isolation requires a way to create and distribute an appropriate certificate (if you choose not to purchase one from a commercial certificate provider).|
|
||||
| Domain isolation | A technique for helping protect the devices in an organization by requiring that the devices authenticate each other's identity before exchanging information, and refusing connection requests from devices that cannot authenticate. Domain isolation takes advantage of Active Directory domain membership and the Kerberos V5 authentication protocol available to all members of the domain. Also see "Isolated domain" in this table.|
|
||||
| Encryption zone | A subset of the devices in an isolated domain that process sensitive data. Devices that are part of the encryption zone have all network traffic encrypted to prevent viewing by non-authorized users. Devices that are part of the encryption zone also typically are subject to the access control restrictions of server isolation.|
|
||||
| Firewall rule | A rule in Windows Defender Firewall that contains a set of conditions used to determine whether a network packet is allowed to pass through the firewall.<br/>By default, the firewall rules in Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 8, Windows 7, and Windows Vista block unsolicited inbound network traffic. Likewise, by default, all outbound network traffic is allowed. The firewall included in previous versions of Windows only filtered inbound network traffic. |
|
||||
| Firewall rule | A rule in Windows Defender Firewall that contains a set of conditions used to determine whether a network packet is allowed to pass through the firewall.<br/>By default, the firewall rules in Windows Server 2016. Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 10, Windows 8, Windows 7, and Windows Vista block unsolicited inbound network traffic. Likewise, by default, all outbound network traffic is allowed. The firewall included in previous versions of Windows only filtered inbound network traffic. |
|
||||
| Internet Protocol security (IPsec) | A set of industry-standard, cryptography-based protection services and protocols. IPsec protects all protocols in the TCP/IP protocol suite except Address Resolution Protocol (ARP).|
|
||||
| IPsec policy | A collection of connection security rules that provide the required protection to network traffic entering and leaving the device. The protection includes authentication of both the sending and receiving device, integrity protection of the network traffic exchanged between them, and can include encryption.|
|
||||
| Isolated domain | An Active Directory domain (or an Active Directory forest, or set of domains with two-way trust relationships) that has Group Policy settings applied to help protect its member devices by using IPsec connection security rules. Members of the isolated domain require authentication on all unsolicited inbound connections (with exceptions handled by the other zones).<br/>In this guide, the term *isolated domain* refers to the IPsec concept of a group of devices that can share authentication. The term *Active Directory domain* refers to the group of devices that share a security database by using Active Directory.|
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user