In other words, Allow is whitelisting an app and Deny is blacklisting an app. To create a rule for a executable right-click on “Executable Rules” under AppLocker and select “Create New Rule…”.Īt this point you choose whether your rule is to Allow or Deny an executable from running. This is already done in the two GPOs that currently have AppLocker policies. It is recommended to create a set of default rules for each of the collection of rules. *If your script, exe or installer require the use of DLL files then you must also create rules for the DLL files in addition to the script/exe/installer.ĪppLocker rules are only configured in the Computer Configuration of a GPO but you can apply any rule to a specific group of users or set it to apply to the “Everyone” group. To use DLL rules you have to enable it by right-clicking on “AppLocker” > Advanced tab > check “Enable the DLL rule collection”. *Note that the DLL rules node is not visible by default (as shown in the previous screenshot). Set Enable = Yes for Run AppLocker rules.This is for allowing or denying. Run the Hardening stage of the PSM installation with only Run Applocker Rules enabled.įrom the CD image, open InstallationAutomation\Hardening\HardeningConfig.XML. Merge any changes in the PSMConfigureAppLocker.xml file to the PSMConfigureAppLocker.xml_.bak file.īack up the PSMConfigureAppLocker.xml file and rename the PSMConfigureAppLocker.xml_.bak file to PSMConfigureAppLocker.xml.
In the PSM installation folder, remove the read-only permissions from the PSMConfigureAppLocker.xml file. If your environment includes DLL files that are not located with the allowed executables, you must add them to the PSMConfigureAppLocker.xml file. Associated executables are automatically updated in the AppLocker rules, but DLL dependencies must be added manually.īeginning in version 12.2.2, DLL files are allowed only when located with the allowed executables. For details, see Deploy Universal Connectors on multiple PSM servers. If you have connectors deployed using shared universal connector deployment on multiple PSM servers they will be updated automatically in the AppLocker rules. If your environment includes executables that must be allowed, in addition to those that are built-in to the PSM installation, such as PSM Universal Connectors executables, you must edit this file to add rules that will allow these executables.
#Applocker policy windows
The PSM installation includes an AppLocker script which enables PSM users to invoke internal PSM applications, mandatory Windows applications, and 3 rd party external applications that are used as clients in the PSM.Īll AppLocker rules are defined in the PSMConfigureAppLocker.xml file in the PSM installation folder > Hardening. These rules specify which users or groups can run those applications. To do this, the PSM uses the Windows AppLocker feature, which defines a set of rules that allow or deny applications from running on the PSM machine, based on unique file identities. To create a hardened and secure PSM environment, the system must limit the applications that can be launched during a PSM session. Use this reference when you run the applocker script manually.
#Applocker policy how to
This section describes how to configure the PSMConfigureAppLocker.xml file.
0 kommentar(er)
