- 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.
04-23-2023 07:24 AM
I'm sorry in advance if I overlooked an obvious answer but I'm stuck.
I am in the process of finalizing application control within our environment and have been asked to create a trusted source in the event a manual installation is required.
My test executables show to correct policy applied directly in that share however they are blocked when copied to the local machine.
Is this by design? I was very certain in past tests, I was able to copy/execute from a trusted source instead of just executing from a trusted source.
The main objective is to remove the need for a trusted source directory on the machine itself
Any advice would be greatly appreciated.
05-02-2023 08:01 AM
Hi @Brian Starbuck ,
You can head to our documentation to understand how to create trust application policies, which determine how EPM manages trusted applications on endpoints: https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/EPM/Server%20User%20Guide/TrustPolicies-NewUI.htm
Thanks,
Tamir
05-02-2023 08:01 AM
Hi @Brian Starbuck ,
You can head to our documentation to understand how to create trust application policies, which determine how EPM manages trusted applications on endpoints: https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/EPM/Server%20User%20Guide/TrustPolicies-NewUI.htm
Thanks,
Tamir
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!

