Maintaining AppLocker Policies
Updated: June 27, 2012
Applies To: Windows 7, Windows Server 2008 R2
This topic describes how to maintain rules within AppLocker policies.
To view this content updated for Windows Server 2012 and Windows 8, see Maintain AppLocker policies.
Common AppLocker maintenance scenarios include:
A new application is deployed, and you need to update an AppLocker policy.
A new version of an application is deployed, and you need to either update an AppLocker policy or create a new rule to update the policy.
An application is no longer supported by your organization, so you need to prevent it from being used.
An application appears to be blocked but should be allowed.
An application appears to be allowed but should be blocked.
A single user or small subset of users needs to use a specific application that is blocked.
There are two methods you can use to maintain AppLocker policies:
Maintaining AppLocker policies by using Group Policy
Maintaining AppLocker policies by using the Local Security Policy snap-in
As new applications are deployed or existing applications are removed by your organization or updated by the software publisher, you might need to make revisions to your rules and update the Group Policy Object (GPO) to ensure that your policy is current.
You can edit an AppLocker policy by adding, changing, or removing rules. However, you cannot specify a version for the AppLocker policy by importing additional rules. To ensure version control when modifying an AppLocker policy, use Group Policy management software that allows you to create versions of GPOs, such as Microsoft Advanced Group Policy Management (AGPM). For more information about AGPM, see Advanced Group Policy Management Overview (http://go.microsoft.com/fwlink/?LinkId=145013).
|You should not edit an AppLocker rule collection while it is being enforced in Group Policy. Because AppLocker controls what files are allowed to run, making changes to a live policy can create unexpected behavior.|
For every scenario, the steps to maintain an AppLocker policy distributed by Group Policy include the following tasks.
Before modifying a policy, evaluate how the policy is currently implemented. For example, if a new version of the application is deployed, you can use Test-AppLockerPolicy to verify the effectiveness of your current policy for that application. To read the procedures necessary to understand the current behavior of the policy, see Discovering the Effect of an AppLocker Policy. Updating your AppLocker planning document will help you track your findings. For information about creating this document, see Creating Your AppLocker Planning Document. For information about Test-AppLockerPolicy and examples of how to use it, see Test-AppLockerPolicy (http://go.microsoft.com/fwlink/?LinkId=169000).
Updating an AppLocker policy that is currently enforced in your production environment can have unintended results. Therefore, export the policy from the GPO and update the rule or rules by using AppLocker on your AppLocker reference or test computer. To prepare an AppLocker policy for modification, see Export an AppLocker Policy from a GPO.
After the AppLocker policy has been exported from the GPO into the AppLocker reference or test computer, or has been accessed on the local computer, the specific rules can be modified as required.
To modify AppLocker rules, see the following:
You should test each collection of rules to ensure that the rules perform as intended. (Because AppLocker rules are inherited from linked GPOs, you should deploy all rules for simultaneous testing in all test GPOs.) For steps to perform this testing, see Testing and Updating an AppLocker Policy.
After testing, import the AppLocker policy back into the GPO for implementation. To update the GPO with a modified AppLocker policy, see Import an AppLocker Policy into a GPO.
For every scenario, the steps to maintain an AppLocker policy distributed by using the Local Security Policy snap-in include the following tasks.
Before modifying a policy, evaluate how the policy is currently implemented. To read the procedures necessary to understand the current behavior of the policy, see Discovering the Effect of an AppLocker Policy. Updating your AppLocker planning document will help you track your findings. For information about creating this document, see Creating Your AppLocker Planning Document.
Rules are grouped into a collection, which can have the policy enforcement setting applied to it. By default, AppLocker rules do not allow users to open or run any files that are not specifically allowed.
To modify AppLocker rules, see the appropriate topic in the AppLocker Rule Procedures collection.
You should test each collection of rules to ensure that the rules perform as intended. For steps to perform this testing, see Testing and Updating an AppLocker Policy.