- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-01-2025 04:23 AM
Hi Guys,
I am facing this issue on my new build env.
I login to my PSM Server, try to open heidisql with my PSM-xxxxxxxxxx user by right-click to heidisq.exe > run as diffirent user > Input the credential but also show this error:
I think this might be the root cause right? because when access via remote session, the CBA system also use this user PSM-xxxxxxxxxx to run the HeidiSQL tool?
I try to clear all the Applocker rule and restart but still no luck. Please help advice
10-01-2025 07:51 AM
Application is blocked by applocker
10-01-2025 07:54 AM
Check PSMapplocker.xml has an entry for the app
10-01-2025 07:55 AM
Step-by-Step Guide: Whitelisting an Application in PSMConfigureAppLocker.xml
This guide provides detailed instructions for Senior Technical Trainers on how to whitelist an application in CyberArk's PSMConfigureAppLocker.xml file. This is essential for enabling custom executables, DLLs, or scripts to run during PSM sessions.
Step 1: Locate the Configuration File
Navigate to the PSM hardening directory on the PSM server:
C:\Program Files (x86)\CyberArk\PSM\Hardening\
Step 2: Identify the Application Type
Determine whether the application is one of the following:
- Executable (.exe)
- DLL (.dll)
- Script (.cmd, .bat, .ps1)
Step 3: Add the Application Entry
Insert the appropriate XML entry based on the application type:
· For Executables:
<Application Name="MyApp" Type="Exe" Path="C:\Path\To\MyApp.exe" Method="Hash" SessionType="*" />
· For DLLs:
<Libraries Name="MyAppDLL" Type="Dll" Path="C:\Path\To\DLLFolder\*" Method="Path" SessionType="*" />
· For Scripts:
<Application Name="MyScript" Type="Script" Path="C:\Path\To\Script.cmd" Method="Path" SessionType="*" />
Notes:
- Use Method="Hash" for strict validation or Method="Path" for flexibility.
- SessionType="*" allows all session types unless you want to restrict it.
Step 4: Save and Apply the Configuration
Open PowerShell as Administrator and run the following commands:
Set-ExecutionPolicy Bypass -Scope Process
.\PSMConfigureAppLocker.ps1
Step 5: Verify the Application Is Allowed
Use Event Viewer to check for AppLocker logs:
Applications and Services Logs > Microsoft > Windows > AppLocker > EXE and DLL
Filter by Event ID 8003 to find blocked applications.
Example: Whitelisting Chrome and Chromedriver
To allow Google Chrome and its driver, add the following entries:
<Application Name="GoogleChrome" Type="Exe" Path="C:\Program Files\Google\Chrome\Application\chrome.exe" Method="Publisher" />
<Application Name="GoogleChromeDriver" Type="Exe" Path="C:\Program Files (x86)\CyberArk\PSM\Components\chromedriver.exe" Method="Path" />
<Libraries Name="ChromeFolder" Type="Dll" Path="C:\Program Files (x86)\Google\Chrome\Application\*" Method="Path" SessionType="*" />
10-03-2025 03:47 AM
Yeah thank you, it is really due to Applocker. I disable it with this KN cause i don't need AppLocker https://community.cyberark.com/s/article/how-to-cleanup-existing-applocker-rule-in-psm-server
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

