Use a Reference Computer to Create and Maintain AppLocker Policies
Updated: June 27, 2012
Applies To: Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
This topic for the IT professional describes the steps to create and maintain AppLocker policies by using a reference computer.
An AppLocker reference computer is a baseline computer you can use to configure policies and can subsequently be used to maintain AppLocker policies. For the procedure to configure a reference computer, see Configure the AppLocker Reference Computer.
An AppLocker reference computer that is used to create and maintain AppLocker policies should contain the corresponding applications for each organizational unit (OU) to mimic your production environment.
|The reference computer must be running one of the supported editions of Windows. For information about operating system requirements for AppLocker, see Requirements to Use AppLocker.|
You can perform AppLocker policy testing on the reference computer by using the Audit only enforcement setting or Windows PowerShell cmdlets. You can also use the reference computer as part of a testing configuration that includes policies that are created by using Software Restriction Policies.
With AppLocker, you can automatically generate rules for all files within a folder. AppLocker scans the specified folder and creates the condition types that you choose for each file in that folder. For the procedure to do this, see Run the Automatically Generate Rules Wizard.
|If you run this wizard to create your first rules for a Group Policy Object (GPO), after you complete the wizard, you will be prompted to create the default rules, which allow critical system files to run. You can edit the default rules at any time. If your organization has decided to edit the default rules or create custom rules to allow the Windows system files to run, ensure that you delete the default rules after you replace them with your custom rules.|
AppLocker includes default rules for each rule collection. These rules are intended to help ensure that the files that are required for Windows to operate properly are allowed in an AppLocker rule collection. You must run the default rules for each rule collection. For information about default rules and considerations for using them, see Understanding AppLocker Default Rules. For the procedure to create default rules, see Create AppLocker Default Rules.
|You can use the default rules as a template when you create your own rules. This allows files within the Windows directory to run. However, these rules are only meant to function as a starter policy when you are first testing AppLocker rules.|
If AppLocker policies are currently running in your production environment, export the policies from the corresponding GPOs and save them to the reference computer. For the procedure to do this, see Export an AppLocker Policy from a GPO. If no AppLocker policies have been deployed, create the rules and develop the policies by using the following procedures:
Create a Rule That Uses a Publisher Condition
Create a Rule That Uses a File Hash Condition
Create a Rule That Uses a Path Condition
Edit AppLocker Rules
Configure Exceptions for an AppLocker Rule
Delete an AppLocker Rule
Enable the DLL Rule Collection
Enforce AppLocker Rules
You should test each set of rules to ensure that they perform as intended. The Test-AppLockerPolicy Windows PowerShell cmdlet can be used to determine whether any of the rules in your rule collection will be blocked on your reference computer. Perform the steps on each reference computer that you used to define the AppLocker policy. Ensure that the reference computer is joined to the domain and that it is receiving the AppLocker policy from the appropriate GPO. Because AppLocker rules are inherited from linked GPOs, you should deploy all of the rules to simultaneously test all of your test GPOs. Use the following procedures to complete this step:
|If you have set the enforcement setting on the rule collection to Enforce rules or you have not configured the rule collection, the policy will be implemented when the GPO is updated in the next step. If you have set the enforcement setting on the rule collection to Audit only, application access events are written to the AppLocker log, and the policy will not take effect.|
When the AppLocker policy has been tested successfully, it can be imported into the GPO (or imported into individual computers that are not managed by Group Policy) and checked for its intended effectiveness. To do this, perform the following procedures:
Export an AppLocker Policy to an XML File
Import an AppLocker Policy into a GPO or
Discover the Effect of an AppLocker Policy
If the AppLocker policy enforcement setting is Audit only and you are satisfied that the policy is fulfilling your intent, you can change it to Enforce rules. For information about how to change the enforcement setting, see Configure an AppLocker Policy for Enforce Rules.