- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-15-2024 06:24 AM
Hi all,
Despite creating a Trust policy for Docker's publisher signature to Elevate if Necessary, I'm encountering an issue. The first time Docker runs, a startup Wizard is launched, requiring admin rights and still asking for the local admin user/password. I had expected the Trust policy to Elevate if Necessary automatically, but this is not happening.
I ran CyberArkEPM --log on the laptop. I noticed that a separate script is launched, and even if the Trusted policy includes "Child processes Handled exclusively by this policy | Elevate if necessary", it still doesn't elevate.
While I was able to get it to work by testing with a broader elevate for /usr/bin/osascript, I'm concerned that this solution is too permissive. I'm in need of a more secure solution. Do you have any ideas?
Here are the logs:
2024-07-14 18:24:23.020 I com.cyberark.CyberArkEPMEndpointSecurityExtension[326:10d2a8] [com.cyberark.CyberArkEPM:Policy] ac_41507641613984: Process '/Applications/Docker.app/Contents/MacOS/com.docker.backend' [87822:502:87726:87725] try to exec '/usr/bin/osascript' [87822:502:87726:87725]: defer, deny caching, decision time 0.008702 seconds, PolicyMatch(name: "[SDS Global] - Exceptions to Blocked/Restricted", id: 66600, isDefault: false, action: VFPA_NORMAL_RUN, target: Target(type: VFPT_MAC_EXE, id: DC0965D2-0B97-4705-A9FF-215F6822C5C7, childMode: nil, eventSuppressionOptions: 0b0, inheritable: false, distributorName: nil), restrictionId: nil, ui: nil, accessControlUI: nil, sendPolicyUsage: true, sendPolicyAutomation: false)
2024-07-14 18:24:23.052 I com.cyberark.CyberArkEPMEndpointSecurityExtension[326:10c7dc] [com.cyberark.CyberArkEPM:Policy] ac_41507641613984: Collected audit events
2024-07-14 18:24:23.327 I authorizationhosthelper.x86_64[87790:10d1b8] [com.cyberark.CyberArkEPM:AuthorizationPlugin] ac_41507957739728: Process '/usr/bin/osascript' [87822:502] try to obtain right 'system.privilege.admin' for authorization created by '/usr/bin/osascript' [87822:502] (rule: system.privilege.admin, rule flags: 19, prompt: 'Docker Desktop requires privileged access to apply configuration')
2024-07-14 18:24:23.336 I com.cyberark.CyberArkEPMEndpointSecurityExtension[326:10c7dc] [com.cyberark.CyberArkEPM:Policy] ac_41507957739728: Process '/usr/bin/osascript' [87822:502] try to obtain right 'system.privilege.admin': defer, PolicyMatch(name: "[AppCtrl Block: Mac OS (10.4)]", id: 66777, isDefault: true, action: VFPA_NORMAL_RUN, target: Target(type: VFPT_MAC_EXE, id: 09389A43-10BA-4013-A106-67A7AA42934D, childMode: nil, eventSuppressionOptions: 0b0, inheritable: false, distributorName: nil), restrictionId: nil, ui: nil, accessControlUI: nil, sendPolicyUsage: false, sendPolicyAutomation: false)
07-17-2024 05:04 AM
Hi @Thomas Capacci
I would suggest, instead of a broad elevation policy for /usr/bin/osascript, create specific elevation policies for each identified script or process. This will limit the scope of elevation to only what is necessary.
07-22-2024 05:12 AM
Hi @Thomas Capacci
Hope it helps !
08-07-2024 01:28 PM
We're running into the exact same issue. I've tried everything that I can think of to get this to work, but all roads seem to lead to osascript needing elevated permissions, but as TCapacci has stated, we don't want to elevate it across the board as that opens up more security concerns than I'm comfortable with.
If anyone has any other ideas, I'm all ears. This one has me pulling my hair out. 😅
08-08-2024 07:33 AM
I have experienced many issues with the "Include Installed Applications" portion of Trust policies in EPM. Some of these issues that I've exposed have recently been fixed, some still remain, and I'm sure more are yet to be discovered. It deals with how manufacturers of the installers are not always following the proper standards, causing EPM to not recognize it as an installer (it thinks it's a regular exe) and therefore the things it installs are not recognized as being installed by it and not having the policy applied.
My recommendation to you (and everyone experiencing this) is to open a support case with the details. They will need the SupportInfo trace logging of the install, the actual installer file (if you can provide) it, etc. so they can try to replicate and pinpoint the issue. The more of these we can provide to CyberArk, the more of these problematic installers they'll be able to properly handle as we go forward.
-rwm
06-23-2025 07:28 AM
Did anyone ever open a case for this, and if so, was there ever a solution to this issue?
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!

