Issue with Elevation Policy

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue with Elevation Policy

L0 Member

I am encountering an issue in CyberArk EPM related to application elevation. Here's the situation:

 

I have configured an elevate policy for a specific application and have whitelisted it for elevation in an application group.

 

When I view the events for this application, it shows that the elevation policy was applied.

 

However, in the policy audit for the same application, it indicates that the policy is UAC (User Account Control) rather than the intended elevation policy.

 

On the endpoint, the application is still prompting for admin credentials, and I see that the policy being applied is PrivMgmt Detect: Windows Main Default Policy.

 

Could anyone help explain why this discrepancy occurs and how to resolve it?

7 REPLIES 7

L2 Linker

Hello,

If you see the application in the Events Management, it confirms that the PrivMgmt Detect default policy was applied, means that your Elevate policy did not trigger for some reason.

 

In this situation I would review the application definitions as most probably there is a definition that does not apply on the application.

If you defined a Signature, try without the signature as there is a known issue that might fail on signature verification.

It could be a child process that requires the elevation, check if the policy works with child processes checked.

Lastly, review the local trace logs on the endpoint, you might see useful information there regarding that behavior.

Hope that helps.

 

L5 Sessionator

What's the application out of interest, so obviously you have right clicked properties on the application and gone to the EPM tab and what does it say there if it's assigend to any policy or not, must admit sounds like a bug, Personally I'd create a policy from the audit and remove the existing policy you have created and then as the chap mentioned tick child processes, but also insure you don't have any block policies or other policies that taking priority so might need to link this application policy to an advanced policy and increase the presidence /priority to highest. Also run a report on your policies from Reports and make sure in the spreadsheet you don't have any duplicate policies for the same application and/or block policies heck maybe you created an Allow policy by mistake and it actually needs elevation to launch if it's a legacy app that can't run without admin. I've seen that before esp on Windows.

L4 Transporter

What's the application out of interest, so obviously you have right clicked properties on the application and gone to the EPM tab and what does it say there if it's assigend to any policy or not, must admit sounds like a bug, Personally I'd create a policy from the audit and remove the existing policy you have created and then as the chap mentioned tick child processes, but also insure you don't have any block policies or other policies that taking priority so might need to link this application policy to an advanced policy and increase the presidence /priority to highest. Also run a report on your policies from Reports and make sure in the spreadsheet you don't have any duplicate policies for the same application and/or block policies heck maybe you created an Allow policy by mistake and it actually needs elevation to launch if it's a legacy app that can't run without admin. I've seen that before esp on Windows.

L5 Sessionator

I can see you're continuing to troubleshoot the EPM elevation policy issue. Based on the knowledge sources, here are some specific reasons why your elevation policy might not be applying as expected:

Policy Precedence and Default Policies

The "PrivMgmt Detect: Windows Main Default Policy" you're seeing is likely the "Detect privileged unhandled applications" default policy. This policy is designed to detect applications that require administrative privileges but aren't covered by other policies.

As mentioned in the documentation: "The privilege management default policies determine how EPM monitors unhandled applications on endpoints and protects your environment from ransomware." Privilege management policies

Possible Causes and Solutions

  1. Application Definition Issues: As Igor suggested, there might be a mismatch in how your application is defined. The documentation recommends: "When you create a new application policy, we recommend you specify the source URL and add at least one more parameter to increase the security level of the policy." Application policies
  2. Child Process Configuration: If the application launches child processes that require elevation, you need to include them in your policy. The documentation states: "When you apply a policy to the child processes of an application, any process launched by the application or its children use the same security token as the application." Child processes
  3. Digital Signature Issues: As Igor mentioned, there can be issues with signature verification. The documentation recommends: "Create policies that securely identify the application by defining specific policy parameters and features, such as application location, application parameters, application checksum, a custom token, restriction rules, and more." Apply policies
  4. Policy Audit Verification: You can check the Policy Audits to see what's actually being applied: "Check the Policy Audits for blocked unsigned services... You can now see all the events that EPM blocked, as defined in the policy." Check the audits

Recommended Steps

  1. Review Application Definition: Ensure your application definition is precise. Try removing the signature requirement temporarily as suggested.
  2. Check Child Processes: Enable the "Include child processes" option in your elevation policy.
  3. Verify Policy Priority: Ensure your custom policy has higher priority than the default policies.
  4. Check Over-the-Shoulder Authentication: If configured, this might be causing the credential prompt: "The Elevate and Elevate if necessary policies use the Elevate and Elevate Trusted dialogs to prompt for the username and password prior to running applications with elevated privileges." Over-the-shoulder Authentication
  5. Create Policy from Events: As suggested, you might want to create a new policy directly from the Events Management page, which can automatically capture the correct application parameters.

By addressing these specific aspects, you should be able to resolve the policy precedence issue and ensure your elevation policy is applied correctly.

 

 

 

 

L4 Transporter

I can see you're continuing to troubleshoot the EPM elevation policy issue. Based on the knowledge sources, here are some specific reasons why your elevation policy might not be applying as expected:

Policy Precedence and Default Policies

The "PrivMgmt Detect: Windows Main Default Policy" you're seeing is likely the "Detect privileged unhandled applications" default policy. This policy is designed to detect applications that require administrative privileges but aren't covered by other policies.

As mentioned in the documentation: "The privilege management default policies determine how EPM monitors unhandled applications on endpoints and protects your environment from ransomware." Privilege management policies

Possible Causes and Solutions

  1. Application Definition Issues: As Igor suggested, there might be a mismatch in how your application is defined. The documentation recommends: "When you create a new application policy, we recommend you specify the source URL and add at least one more parameter to increase the security level of the policy." Application policies
  2. Child Process Configuration: If the application launches child processes that require elevation, you need to include them in your policy. The documentation states: "When you apply a policy to the child processes of an application, any process launched by the application or its children use the same security token as the application." Child processes
  3. Digital Signature Issues: As Igor mentioned, there can be issues with signature verification. The documentation recommends: "Create policies that securely identify the application by defining specific policy parameters and features, such as application location, application parameters, application checksum, a custom token, restriction rules, and more." Apply policies
  4. Policy Audit Verification: You can check the Policy Audits to see what's actually being applied: "Check the Policy Audits for blocked unsigned services... You can now see all the events that EPM blocked, as defined in the policy." Check the audits

Recommended Steps

  1. Review Application Definition: Ensure your application definition is precise. Try removing the signature requirement temporarily as suggested.
  2. Check Child Processes: Enable the "Include child processes" option in your elevation policy.
  3. Verify Policy Priority: Ensure your custom policy has higher priority than the default policies.
  4. Check Over-the-Shoulder Authentication: If configured, this might be causing the credential prompt: "The Elevate and Elevate if necessary policies use the Elevate and Elevate Trusted dialogs to prompt for the username and password prior to running applications with elevated privileges." Over-the-shoulder Authentication
  5. Create Policy from Events: As suggested, you might want to create a new policy directly from the Events Management page, which can automatically capture the correct application parameters.

By addressing these specific aspects, you should be able to resolve the policy precedence issue and ensure your elevation policy is applied correctly.

 

 

 

 

L4 Transporter

Hi @Shastrula Sathwik​ ,

 

If you have issue with elevating an application even after creating a policy. Please use below steps to troubleshoot.

 

Enable EPM file tab

 

Navigate to Edit parameters under the General Configuration

Set "Show CyberArk EPM tab in File Properties" to On

Request settings on EPM agent for most recent policy settings

You can now see the EPM File tab in the application properties to view which policies are active for it

 

Thanks

 

L0 Member

Thank you all. It's sorted after removing the signature.

  • 236 Views
  • 7 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!