- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-20-2025 06:06 AM
I’m looking for guidance on the best approach to block unapproved remote connection tools using CyberArk EPM. Our goal is to prevent any remote access software that isn’t explicitly approved or managed by policy from running on endpoints.
Has anyone implemented a similar control, and if so, what’s the recommended configuration or best practice for ensuring only approved remote access tools (e.g., corporate-approved software) are allowed to run for selected users?
10-20-2025 06:16 AM
Not really an answer but was asked recently - https://community.cyberark.com/s/question/0D5Vy00000xaSKGKA2/how-do-i-block-all-remote-access-tools-i-dont-want-to-specify-every-tools-i-want-to-block-all-of-them-then-whitelist-what-is-allowed I know I've personally created a block policy for Quick assist, and I don't think it would be difficult creating a all-win-block policy for any other remote tool apps like Beyond Trust, Desktop anywhere etc etc..
10-20-2025 06:16 AM
Not really an answer but was asked recently - https://community.cyberark.com/s/question/0D5Vy00000xaSKGKA2/how-do-i-block-all-remote-access-tools-i-dont-want-to-specify-every-tools-i-want-to-block-all-of-them-then-whitelist-what-is-allowed I know I've personally created a block policy for Quick assist, and I don't think it would be difficult creating a all-win-block policy for any other remote tool apps like Beyond Trust, Desktop anywhere etc etc..
10-20-2025 06:23 AM
Would it be possible to implement a policy that blocks all tools by default, while maintaining a separate policy to explicitly allow only specific ones? I was considering whether the default "block unhandled applications" policy could be leveraged for this purpose, but I’m interested in learning how others have approached similar scenarios.
10-20-2025 07:03 AM
If you mean specifically remote apps not sure without blocking all apps from being installed too - using the - https://docs.cyberark.com/epm/latest/en/content/epm/server%20user%20guide/privmgmnt-blockunhandledapps-newui.htm#:~:text=Activate%20the%20default%20policy,the%20policy%20with%20default%20settings. ?
Otherwise you're have to create a policy for each application to block them, Assuming they're installed or you're wanting to stop users from installing them if they have local admin ? I guess you can ask the chap from the previous thread see if he's found a way, personally sounds like you're have to create a block policy for each application and create an advanced policy so a user gets a GUI message saying you need to use this tool instead - https://community.cyberark.com/s/events?tab=all&products=Endpoint%2520Privilege%2520Manager%2520%28EPM%29 plenty of training guides here but not for your specific scenario.
We don't block unhandled apps from being elevated for now and would never approve a remote tool anyway if it came into the events inbox, our cyber team would simply reject the ticket. So maybe you need a helpdesk education and implement a work flow, we actually dont allow manual apps from being installed so hoping thy will switch on block default policies, reason being we ain;t done it yet is we've migrated 20k users to epm all devs and some EUC/cyber and so on, but we want all the apps packaged first and ready via intune/homebrew/manual etc before we fully lock it down, tbh no need to keep it manual anyways it just creates a ton of tickets, I don't think raising an ER will help as it would take ages for them to implement it. I really am not sure sounds like a lot of manual effort if users can actually run these remote software , if epm just pics up the install an prevents it by default then simply add each request to a all-block policy application group then add that to an advanced policy and create a GUI saying blocked and state you cant do this in the prompt message?
You should really find a way to audit and query if someone installs a remote tool too if its considered high risk where you work, so look into splunk/siem too? and I've just summarised using copilot as it's easier to understand - Create an “All-Win-Block” Policy Group
If you want more granular control:
This gives users feedback and reduces helpdesk tickets.
3. Audit and Monitor via SIEM (e.g., Splunk)
Since remote access tools are high-risk:
This helps with visibility and incident response.
4. User Education & Workflow Integration
As you mentioned:
🛠️ Optional Enhancements
10-20-2025 07:03 AM
If you mean specifically remote apps not sure without blocking all apps from being installed too - using the - https://docs.cyberark.com/epm/latest/en/content/epm/server%20user%20guide/privmgmnt-blockunhandledapps-newui.htm#:~:text=Activate%20the%20default%20policy,the%20policy%20with%20default%20settings. ?
Otherwise you're have to create a policy for each application to block them, Assuming they're installed or you're wanting to stop users from installing them if they have local admin ? I guess you can ask the chap from the previous thread see if he's found a way, personally sounds like you're have to create a block policy for each application and create an advanced policy so a user gets a GUI message saying you need to use this tool instead - https://community.cyberark.com/s/events?tab=all&products=Endpoint%2520Privilege%2520Manager%2520%28EPM%29 plenty of training guides here but not for your specific scenario.
We don't block unhandled apps from being elevated for now and would never approve a remote tool anyway if it came into the events inbox, our cyber team would simply reject the ticket. So maybe you need a helpdesk education and implement a work flow, we actually dont allow manual apps from being installed so hoping thy will switch on block default policies, reason being we ain;t done it yet is we've migrated 20k users to epm all devs and some EUC/cyber and so on, but we want all the apps packaged first and ready via intune/homebrew/manual etc before we fully lock it down, tbh no need to keep it manual anyways it just creates a ton of tickets, I don't think raising an ER will help as it would take ages for them to implement it. I really am not sure sounds like a lot of manual effort if users can actually run these remote software , if epm just pics up the install an prevents it by default then simply add each request to a all-block policy application group then add that to an advanced policy and create a GUI saying blocked and state you cant do this in the prompt message?
You should really find a way to audit and query if someone installs a remote tool too if its considered high risk where you work, so look into splunk/siem too? and I've just summarised using copilot as it's easier to understand - Create an “All-Win-Block” Policy Group
If you want more granular control:
This gives users feedback and reduces helpdesk tickets.
3. Audit and Monitor via SIEM (e.g., Splunk)
Since remote access tools are high-risk:
This helps with visibility and incident response.
4. User Education & Workflow Integration
As you mentioned:
🛠️ Optional Enhancements
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!

