Use a reference device to create and maintain AppLocker policies

This article for the IT professional describes the steps to create and maintain AppLocker policies by using a reference computer.

Background and prerequisites

An AppLocker reference device is a baseline device you can use to configure policies and can then be used to maintain AppLocker policies. For the procedure to configure a reference device, see Configure the AppLocker reference device.

An AppLocker reference device that is used to create and maintain AppLocker policies should contain the corresponding apps for each organizational unit (OU) to mimic your production environment.

You can perform AppLocker policy testing on the reference device by using the Audit only enforcement mode setting or Windows PowerShell cmdlets.

Step 1: Automatically generate rules on the reference device

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 information on how to automatically generate rules, see Run the Automatically Generate Rules wizard.

Step 2: Create the default rules on the reference device

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 info 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.

Step 3: Modify rules and the rule collection on the reference device

If AppLocker policies are currently running in your production environment, export the policies from the corresponding GPOs and save them to the reference device. For information on how to export and save the policies, see Export an AppLocker policy from a GPO. If no AppLocker policies are 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
• Add exceptions for an AppLocker rule
• Delete an AppLocker rule
• Enable the DLL rule collection
• Enforce AppLocker rules

Step 4: Test and update AppLocker policy on the reference device

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 apps on your reference device are blocked by the rules in your rule collections. Perform the steps on each reference device that you used to define the AppLocker policy. Ensure that the reference device is joined to the domain and that it's 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:

• Test an AppLocker Policy with Test-AppLockerPolicy
• Discover the Effect of an AppLocker Policy

Step 5: Export and import the policy into production

After you test your AppLocker policy, you can import it into the GPO (or imported into individual computers not managed by Group Policy) and checked for its intended effectiveness. To do these tasks, 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're satisfied that the policy is fulfilling your intent, you can change it to Enforce rules. For info about how to change the enforcement setting, see Configure an AppLocker policy for enforce rules.

Step 6: Monitor the effect of the policy in production

If more refinements or updates are necessary after a policy is deployed, use the appropriate following procedures to monitor and update the policy:

• Monitor app usage with AppLocker
• Edit an AppLocker policy
• Refresh an AppLocker policy

See also

• Deploy the AppLocker policy into production