![]() ![]() ![]() 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.4, 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. 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. This section describes how to configure the PSMConfigureAppLocker.xml file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |