mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 08:17:23 +00:00
Merge pull request #2 from jgeurten/wdac-wizard-topic
finalized Wdac wizard topic draft
This commit is contained in:
Jordan Geurten
GitHub
commit
54f647a6f2
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
@ -19,3 +19,110 @@ ms.date: 10/14/2020
|
||||
---
|
||||
|
||||
# Creating a new Supplemental Policy with the Wizard
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server 2016 and above
|
||||
|
||||
Beginning in Windows 10 version 1903, WDAC supports the creation of multiple active policies on a device. One or more supplemental policies allow customers to expand a [WDAC base policy](wdac-wizard-create-base-policy.md) to increase the circle of trust of the policy. A supplemental policy can expand only one base policy, but multiple supplementals can expand the same base policy. When using supplemental policies, applications allowed by the base or its supplemental policy/policies will be allowed to execute.
|
||||
|
||||
Prerequisite information about application control can be accessed through the [WDAC design guide](windows-defender-application-control-design-guide.md). This page outlines the steps to create a supplemental application control policy, configure the policy options, and the signer and file rules.
|
||||
|
||||
## Expanding a Base Policy
|
||||
|
||||
Once the Policy Creator > Supplemental Policy type is chosen, a policy name and file location dialog will appear to name and save the supplemental policy. The next step requires selecting a base policy to expand. To expand a base policy, the base must allow supplemental policies. The WDAC Wizard will verify whether the base poliy allows supplementals and will show either of the following confirmations.
|
||||
|
||||
|
||||
|
||||
|
||||
If the base policy is not configured for supplemental policies, first edit the base policy to allow supplementals using the [WDAC Wizard edit workflow](edac-wizard-editing-policy.md).
|
||||
|
||||
## Configuring Policy Rules
|
||||
|
||||
Upon page launch, policy rules will be automatically enabled/disabled depending on the chosen template from the previous page. Choose to enable or disable the desired policy rule options by pressing the slider button next to the policy rule titles. Hovering the mouse over the policy rule title will display a short description of the rule at the bottom of the page.
|
||||
|
||||
### Policy Rules Description
|
||||
|
||||
A description of the policy rules, beginning with the left-most column are provided below.
|
||||
|
||||
| Rule option | Description |
|
||||
|------------ | ----------- |
|
||||
| **Advanced Boot Options Menu** | The F8 preboot menu is disabled by default for all WDAC policies. Setting this rule option allows the F8 menu to appear to physically present users. |
|
||||
| **Allow Supplemental Policies** | Use this option on a base policy to allow supplemental policies to expand it. |
|
||||
| **Disable Script Enforcement** | This option disables script enforcement options. Unsigned PowerShell scripts and interactive PowerShell are no longer restricted to [Constrained Language Mode](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_language_modes). NOTE: This option is only supported with the Windows 10 May 2019 Update (1903) and higher. Using it on earlier versions of Windows 10 is not supported and may have unintended results. |
|
||||
|**[Hypervisor-protected code integrity](https://docs.microsoft.com/en-us/windows/security/threat-protection/device-guard/enable-virtualization-based-protection-of-code-integrity)**| When enabled, policy enforcement uses virtualization-based security to run the code integrity service inside a secure environment. This provides stronger protections against kernel malware.|
|
||||
| **Intelligent Security Graph Authorization** | Use this option to automatically allow applications with "known good" reputation as defined by Microsoft’s Intelligent Security Graph (ISG). |
|
||||
| **Managed Installer** | Use this option to automatically allow applications installed by a software distribution solution, such as Microsoft Endpoint Configuration Manager, that has been defined as a managed installer. |
|
||||
| **Require WHQL** | By default, legacy drivers that are not Windows Hardware Quality Labs (WHQL) signed are allowed to execute. Enabling this rule requires that every executed driver is WHQL signed and removes legacy driver support. Going forward, every new Windows 10–compatible driver must be WHQL certified. |
|
||||
| **Update Policy without Rebooting** | Use this option to allow future WDAC policy updates to apply without requiring a system reboot. |
|
||||
| **Unsigned System Integrity Policy** | Allows the policy to remain unsigned. When this option is removed, the policy must be signed and have UpdatePolicySigners added to the policy to enable future policy modifications. |
|
||||
| **User Mode Code Integrity** | WDAC policies restrict both kernel-mode and user-mode binaries. By default, only kernel-mode binaries are restricted. Enabling this rule option validates user mode executables and scripts. |
|
||||
|
||||
### Advanced Policy Rules Description
|
||||
|
||||
Selecting the **+ Advanced Options** label will show another column of policy rules; advanced policy rules. A description of the policy rules are provided below.
|
||||
|
||||
| Rule option | Description |
|
||||
|------------ | ----------- |
|
||||
| **Boot Audit on Failure** | Used when the WDAC policy is in enforcement mode. When a driver fails during startup, the WDAC policy will be placed in audit mode so that Windows will load. Administrators can validate the reason for the failure in the CodeIntegrity event log. |
|
||||
| **Disable Flight Signing** | If enabled, WDAC policies will not trust flightroot-signed binaries. This would be used in the scenario in which organizations only want to run released binaries, not flighted builds. |
|
||||
| **Disable Runtime FilePath Rule Protection** | Disable default FilePath rule protection (apps and executables allowed based on file path rules must come from a file path that’s only writable by an administrator) for any FileRule that allows a file based on FilePath. |
|
||||
| **Dynamic Code Security** | Enables policy enforcement for .NET applications and dynamically-loaded libraries. |
|
||||
| **Invalidate EAs on Reboot** | When the Intelligent Security Graph option (14) is used, WDAC sets an extended file attribute that indicates that the file was authorized to run. This option will cause WDAC to periodically re-validate the reputation for files that were authorized by the ISG.|
|
||||
| **Require EV Signers** | In addition to being WHQL signed, this rule requires that drivers must have been submitted by a partner that has an Extended Verification (EV) certificate. All Windows 10 and later drivers will meet this requirement. |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> We recommend that you **enable Audit Mode** initially because it allows you to test new WDAC policies before you enforce them. With audit mode, no application is blocked—instead the policy logs an event whenever an application outside the policy is started. For this reason, all templates have Audit Mode enabled by default.
|
||||
|
||||
## Creating custom file rules
|
||||
|
||||
File rules in an application control policy will specify the level at which appiations will be identified and trusted. File rules are the main mechanism for defining trust in the application control policy. Selecting the **+ Custom Rules** will open the custom file rule conditions panel to create and customize targeted file rules for your policy. The Wizard supports 4 types of file rules:
|
||||
|
||||
### Publisher Rules
|
||||
|
||||
The Publisher file rule type uses properties in the code signing certificate chain to base file rules. Once the file to base the rule off of, called the *reference file*, is selected, use the slider to indicate the specifity of the rule. The table below shows the relationship between the slider placement, the corresponding WDAC rule level and its description. The lower the placement on the table and the UI slider, the greater the specificity of the rule.
|
||||
|
||||
| Rule Condition | WDAC Rule Level | Description |
|
||||
|------------ | ----------- | ----------- |
|
||||
| **Issuing CA** | PCACertificate | Highest available certificate is added to the signers. This is typically the PCA certificate, one level below the root certificate. Any file signed by this certificate will be affected. |
|
||||
| **Publisher** | Publisher | This rule is a combination of the PCACertificate rule and the common name (CN) of the leaf certificate. Any file signed by a major CA but with a leaf from a specific company, for example a device driver corp, is affected. |
|
||||
| **File version** | SignedVersion | This rule is a combination of PCACertificate, Publisher and a version number. Anything from the specified publisher with a version at or above the one specified is affected. |
|
||||
| **File name** | FilePublisher | Most specific. Combination of the file name, publisher and PCA certificate as well as a minimum version number. Files from the publisher with the specified name and greater or equal to the specified version are affected. |
|
||||
|
||||
|
||||
|
||||
|
||||
### Filepath Rules
|
||||
|
||||
Filepath rules do not provide the same security guarantees that explicit signer rules do, as they are based on mutable access permissions. To create a filepath rule, simply select the file using the *Browse* button.
|
||||
|
||||
### File Attribute Rules
|
||||
|
||||
The Wizard supports the creation of [file name rules](select-types-of-rules-to-create#windows-defender-application-control-filename-rules) based on authenticated file attributes. File name rules are useful when an application and its dependencies (eg. DLLs) may all share the same product name, for instance. This allows users to easily create targeted policies based on the Product Name filename rule level. To select the file attribute to create the rule, move the slider on the Wizard to the desired attribute. The table below describes each of the supported file attributes off which to create a rule.
|
||||
|
||||
| Rule level | Description |
|
||||
|------------ | ----------- |
|
||||
| **Original Filename** | Specifies the original file name, or the name with which the file was first created, of the binary. |
|
||||
| **File description** | Specifies the file description provided by the developer of the binary. |
|
||||
| **Product name** | Specifies the name of the product with which the binary ships. |
|
||||
| **Internal name** | Specifies the internal name of the binary. |
|
||||
|
||||
|
||||
|
||||
|
||||
### File Hash Rules
|
||||
|
||||
Lastly, the Wizard supports creating file rules using the hash of the file. Although this level is specific, it can cause additional administrative overhead to maintain the current product versions’ hash values. Each time a binary is updated, the hash value changes, therefore requiring a policy update. By default, the Wizard will use file hash as the fallback in case a file rule cannot be created using the specified file rule level.
|
||||
|
||||
|
||||
#### Deleting Signing Rules
|
||||
|
||||
The policy signing rules list table on the left of the page will document the allow and deny rules in the template, as well as any custom rules you create. Template signing rules and custom rules can be deleted from the policy by selecting the rule from the rules list table. Once the rule is highlighted, press the delete button underneath the table. you will be prompted for additional confirmation. Select `Yes` to remove the rule from the policy and the rules table.
|
||||
|
||||
## Up next
|
||||
|
||||
- [Editing a WDAC policy using the Wizard](wdac-wizard-editing-policy.md)
|
||||
@ -19,3 +19,55 @@ ms.date: 10/14/2020
|
||||
---
|
||||
|
||||
# Editing exisiting base and supplemental WDAC policies with the Wizard
|
||||
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
- Windows Server 2016 and above
|
||||
|
||||
The WDAC Wizard makes editing and viewing base and supplemental WDAC policies much easier than by hand or using the PowerShell Cmdlets. The Wizard currently supports the following editing capbilities:
|
||||
<ul>
|
||||
<li>[Configuring policy rules](#Configuring-Policy-Rules)</li>
|
||||
<li>[Adding new allow or block file rules to existing policies](#Adding-File-Rules)</li>
|
||||
<li>[Removing allow or block file rules on existing policies](#Removing-File-Rules)</li>
|
||||
<li></li>
|
||||
</ul>
|
||||
|
||||
# Configuring Policy Rules
|
||||
|
||||
The `Policy Rules` page will load with the in-edit policy rules configured per the set rules. Selecting the `+ Advanced Options` button will reveal the advanced policy rule options panel. This grouping of rules contains additional policy rule options which are less common to the majority of users. To edit any of the rules, flip the corresponding policy rule state. For instance, to disable Audit Mode and enable Enforcement Mode in the figure below, the button beside the `Audit Mode` label needs only to be pressed. Once the policy rules are configured, select the Next button to continue the next stage of editing: [Adding File Rules](#Adding-File-Rules).
|
||||
|
||||
|
||||
|
||||
Hovering the mouse over the policy rule names will display a short description of the ruleat the bottom of the page.For a complete list of the policy rules and their capabilities see the [Windows Defender Application Control policy rules table](select-types-of-rules-to-create.md#windows-defender-application-control-policy-rules).
|
||||
|
||||
## Adding File Rules
|
||||
|
||||
Previously, to add rules to an existing policy, users would be required to create a new policy and merge it with their existing policy, or edit the policy by hand. The WDAC Wizard allows users to add rules to their exising policy seamlessly.
|
||||
|
||||
Selecting the `+ Custom Rules` button will open the Custom Rules panel. For more information on creating new policy file rules, see the guidelines provided in the [creating policy file rules section](wdac-wizard-create-base-policy.md#Creating-custom-file-rules).
|
||||
|
||||
## Removing File Rules
|
||||
|
||||
The WDAC Wizard makes deleting file rules from an existing policy quick and easy. To remove any type of file rule: publisher rule, path rule, filename rule or a hash rule, simply click on the rule in the `Policy Signing Rules List` table on the lefthand side of the page. Selecting the rule will highlight the entire row. Once the row is highlighted, select the remove icon underneath the table. The Wizard will prompt for user confirmation before removing the file rule. Once removed, the rule will no longer appear in the policy or the table.
|
||||
|
||||
|
||||
|
||||
**Note:** removing a publisher rule will also remove the associated File Attribute rules. For instance, in the xml block below, removing ID_SIGNER_CONTOSO_PUBLISHER would also remove the rules ID_FILEATTRIB_LOB_APP_1 and ID_FILEATTRIB_LOB_APP_2.
|
||||
|
||||
```xml
|
||||
<Signer ID="ID_SIGNER_CONTOSO_PUBLISHER" Name="Contoso LOB Publisher CA">
|
||||
<CertRoot Type="TBS" Value="0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF" />
|
||||
<CertPublisher Value="Contoso IT Dept App Publisher" />
|
||||
<FileAttribRef RuleID="ID_FILEATTRIB_LOB_APP_1" />
|
||||
<FileAttribRef RuleID="ID_FILEATTRIB_LOB_APP_2" />
|
||||
```
|
||||
|
||||
[comment]: <> (## Editing File Rules Coming soon!)
|
||||
|
||||
### Policy Creation
|
||||
|
||||
Once the WDAC Wizard finalizes creation of your edited policy, the new policy will be written to the same file path and name as the in-edit policy with the new version appended to the end of the file name. For instance, if the in-edit policy is saved at MyDocuments\BasePolicy.xml, after edit, the new policy will be saved at MyDocuments\BasePolicy_v10.0.0.1.xml.
|
||||
|
||||
## Up next
|
||||
|
||||
- [Merging WDAC policies using the Wizard](wdac-wizard-merging-policies.md)
|
||||
@ -19,3 +19,14 @@ ms.date: 10/14/2020
|
||||
---
|
||||
|
||||
# Merging existing policies with the WDAC Wizard
|
||||
|
||||
Beginning in Windows 10 version 1903, WDAC supports multiple policies. Before version 1903, however, Windows 10 could only have one WDAC policy. Consquently, users were required to merge multiple WDAC policies into one. The WDAC Wizard has a simple to use user interface to allow users to merge multiple WDAC policies. The Wizard can support up to 15 policy files as input during the merge workflow.
|
||||
|
||||
Simply select the policies you wish to merge into one policy using the `+ Add Policy` button under the table. Once added, policies will be enumerated within the table. To remove a policy from the table, in the case of accidental addition, highlight the policy row and click the `- Remove Policy` button. Confirmation will be required before the policy is withdrawn from the table.
|
||||
|
||||
> [!NOTE]
|
||||
> The policy type and ID of the final output policy will be determined based on the type and ID of the **first policy** in the policy list table. For instance, if a legacy policy format policy and a multi-policy format policy are merged together, the output format of the policy will be whichever policy is specified first in the table. For more information on policy formats, visit the [Multiple WDAC Policies page](deploy-multiple-windows-defender-application-control-policies).
|
||||
|
||||
Lastly, select a filepath save location for the final merged policy on disk using the Browse button. Once at least two policies to merge are specified, and the output file location is set, click Next to build the policy.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user