Create a Rule that Uses a Path Condition
Applies To: Windows 7, Windows Server 2008 R2
This topic shows how to create an AppLocker rule with a path condition in Windows Server 2008 R2 and Windows 7.
The path condition identifies an application by its location in the file system of the computer or on the network.
Important
When creating a rule that uses a deny action, path conditions are less secure for preventing access to a file because a user could easily copy the file to a different location than what is specified in the rule. Because path rules correspond to locations within the file system, you should ensure that there are no subdirectories that are writable by non-administrators. For example, if you create a path rule for C:\ with the allow action, any file within C:\ will be allowed to run, including users' profiles.
For information about the path condition, see Understanding the Path Rule Condition in AppLocker.
You can perform this task by using Group Policy for an AppLocker policy in a Group Policy object (GPO) or by using the Local Security Policy snap-in for an AppLocker policy on a local computer.
To create a new rule with a path condition by using Group Policy
To create a new rule with a path condition by using the Local Security Policy snap-in
To complete this procedure, you must have Edit Setting permission to edit a GPO. By default, members of the Domain Admins group, the Enterprise Admins group, and the Group Policy Creator Owners group have this permission.
To create a new rule with a path condition by using Group Policy
Click Start, click Administrative Tools, and then click Group Policy Management to open the Group Policy Management Console (GPMC).
Locate the GPO that contains the AppLocker policy to modify, right-click the GPO, and click Edit.
In the console tree, double-click Application Control Policies, double-click AppLocker, and then click the rule collection that you want to create the rule for.
On the Action menu, click Create New Rule.
On the Before You Begin page, click Next.
On the Permissions page, select the action (allow or deny) and the user or group that the rule should apply to, and then click Next.
On the Conditions page, select the Path rule condition, and then click Browse Files to locate the targeted folder for the application.
Note
When you browse to a file or folder location, the wizard automatically converts absolute file paths to use AppLocker path variables. You may edit the path after browsing to specify an absolute path, or you may type the path directly into the Path box. To learn more about AppLocker path variables, see Understanding the Path Rule Condition in AppLocker.
Click Next.
(Optional) On the Exceptions page, specify conditions by which to exclude files from being affected by the rule. Click Next.
On the Name and Description page, either accept the automatically generated rule name or type a new rule name, and then click Create.
Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.
To create a new rule with a path condition by using the Local Security Policy snap-in
Click Start, type secpol.msc in the Search programs and files box, and then press ENTER.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the console tree, double-click Application Control Policies, double-click AppLocker, and then click the rule collection that you want to create the rule for.
On the Action menu, click Create New Rule.
On the Before You Begin page, click Next.
On the Permissions page, select the action (allow or deny) and the user or group that the rule should apply to, and then click Next.
On the Conditions page, select the Path rule condition, and then click Browse Files to locate the targeted folder for the application.
Note
When you browse to a file or folder location, the wizard automatically converts absolute file paths to use AppLocker path variables. You may edit the path after browsing to specify an absolute path, or you may type the path directly into the Path box. To learn more about AppLocker path variables, see Understanding the Path Rule Condition in AppLocker.
Click Next.
(Optional) On the Exceptions page, specify conditions by which to exclude files from being affected by the rule. Click Next.
On the Name and Description page, either accept the automatically generated rule name or type a new rule name, and then click Create.