Experiencing EPM elevate privilege issue with 24.8.0.2240

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Experiencing EPM elevate privilege issue with 24.8.0.2240

L1 Bithead

We are experiencing an issue on version 24.8.0.2240 where elevation for defined applications/policies fails because the agent goes offline suddenly due to the service stopping. We have to manually restart the service to restore functionality, but it goes offline again after a certain period.

 

Has anyone else encountered this issue? We are also unable to upgrade to the latest version due to our disconnected status.

1 accepted solution

Accepted Solutions

L1 Bithead

The issue was solved (still in watching mode) after upgrading the EPM agent to. 25.2.0.2476.

View solution in original post

4 REPLIES 4

L5 Sessionator

Can you see the devices in the beta section and do they show the Green tick stating they are alive or the - dash showing as disconnected, ? if it's the latter for all maybe worth updating your firewall entries to include the new AWS IOT connectivity applies to proxy too such as zscaler for example for versions 24.7 onward only, might improve the connectivity obviously you're saying the epm agent is showing as a stopped service in services,msc can't say I've come across that issue here. might be worth sharing the logs with a ticket to Cyberark?

 

https://docs.cyberark.com/epm/24.9.0/en/content/installation/firewallrules.htm IOT is way faster to update the agents for us so even if they do go down you would have time to update them of course I don't know what your network is like and what devices these are and cpu/ram/hard drive etc , IOPS could be a factor in the performance of the agent?

 

personally i would want to make sure the EPM agent isn't being interfered with by other security tools - https://community.cyberark.com/s/article/00004063 and perhaps keep a constant ping to the server and run a Procmon capture during the policy update if that's when it suddenly stops working and share with Cyberark?

 

Possible Causes

Looking at the release notes for version 24.8.0, there were several behavior changes that might be relevant to your issue:

  1. Communication Protocol Changes: The documentation mentions "We have improved access to Active Directory in the communication protocol used and fallback options in case of protocol communication issues" Version 24.8.0. This change might be causing unexpected behavior.
  2. Enhanced Endpoint Management: Version 24.8.0 introduced "enhanced endpoint management" which changed how agents communicate with the EPM service. This was initially only available in certain regions (UK and Canada data centers), but it might be affecting your deployment Enhanced endpoints management.
  3. Bug Fixes: There were bug fixes in version 24.8.1 that might address your issue, suggesting known problems in 24.8.0 Bug fixes.

Recommendations

Since you're unable to upgrade due to disconnected status, here are some troubleshooting steps:

  1. Check Agent Logs: Collect agent support information to identify what's causing the service to stop. The logs might show errors related to communication or policy enforcement.
  2. Verify Network Connectivity: Even though you mentioned being disconnected, check if there are intermittent connectivity issues that might be causing the agent to attempt connections and fail.
  3. Review Policy Configuration: Check if there are any policies that might be causing conflicts, especially if you're using the "Detect privileged unhandled applications" default policy.
  4. Consider Offline Authorization: Since you're experiencing disconnection issues, you might want to use the Offline Policy Authorization Generator tool to provide temporary access: Provide temporary access to offline users
  5. Contact CyberArk Support: This appears to be a specific issue with version 24.8.0.2240 that might require direct support from CyberArk. They might have a hotfix or specific guidance for your situation.

If you're able to provide more details about when exactly the service stops (e.g., after specific actions or at regular intervals), that might help narrow down the cause of the issue.

 

All feedback is reviewed by the team.

Answer based on the following sources:

Version 24.8.0

Version 24.8.x

Bug fixes

Version 24.8.x

Provide temporary access to offline users

docs.cyberark.com/epm

 

 

 

 

L4 Transporter

Can you see the devices in the beta section and do they show the Green tick stating they are alive or the - dash showing as disconnected, ? if it's the latter for all maybe worth updating your firewall entries to include the new AWS IOT connectivity applies to proxy too such as zscaler for example for versions 24.7 onward only, might improve the connectivity obviously you're saying the epm agent is showing as a stopped service in services,msc can't say I've come across that issue here. might be worth sharing the logs with a ticket to Cyberark?

 

https://docs.cyberark.com/epm/24.9.0/en/content/installation/firewallrules.htm IOT is way faster to update the agents for us so even if they do go down you would have time to update them of course I don't know what your network is like and what devices these are and cpu/ram/hard drive etc , IOPS could be a factor in the performance of the agent?

 

personally i would want to make sure the EPM agent isn't being interfered with by other security tools - https://community.cyberark.com/s/article/00004063 and perhaps keep a constant ping to the server and run a Procmon capture during the policy update if that's when it suddenly stops working and share with Cyberark?

 

Possible Causes

Looking at the release notes for version 24.8.0, there were several behavior changes that might be relevant to your issue:

  1. Communication Protocol Changes: The documentation mentions "We have improved access to Active Directory in the communication protocol used and fallback options in case of protocol communication issues" Version 24.8.0. This change might be causing unexpected behavior.
  2. Enhanced Endpoint Management: Version 24.8.0 introduced "enhanced endpoint management" which changed how agents communicate with the EPM service. This was initially only available in certain regions (UK and Canada data centers), but it might be affecting your deployment Enhanced endpoints management.
  3. Bug Fixes: There were bug fixes in version 24.8.1 that might address your issue, suggesting known problems in 24.8.0 Bug fixes.

Recommendations

Since you're unable to upgrade due to disconnected status, here are some troubleshooting steps:

  1. Check Agent Logs: Collect agent support information to identify what's causing the service to stop. The logs might show errors related to communication or policy enforcement.
  2. Verify Network Connectivity: Even though you mentioned being disconnected, check if there are intermittent connectivity issues that might be causing the agent to attempt connections and fail.
  3. Review Policy Configuration: Check if there are any policies that might be causing conflicts, especially if you're using the "Detect privileged unhandled applications" default policy.
  4. Consider Offline Authorization: Since you're experiencing disconnection issues, you might want to use the Offline Policy Authorization Generator tool to provide temporary access: Provide temporary access to offline users
  5. Contact CyberArk Support: This appears to be a specific issue with version 24.8.0.2240 that might require direct support from CyberArk. They might have a hotfix or specific guidance for your situation.

If you're able to provide more details about when exactly the service stops (e.g., after specific actions or at regular intervals), that might help narrow down the cause of the issue.

 

All feedback is reviewed by the team.

Answer based on the following sources:

Version 24.8.0

Version 24.8.x

Bug fixes

Version 24.8.x

Provide temporary access to offline users

docs.cyberark.com/epm

 

 

 

 

L4 Transporter

Hi @Kailash Bohara​ 

 

As it seems Trehman provided an answer for your question, could you kindly share if this solution resolved your issue?

If so, could you please mark the answer as "Select as Best" to help other community members?

 

If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.

 

Thank you,

Liad

L1 Bithead

The issue was solved (still in watching mode) after upgrading the EPM agent to. 25.2.0.2476.

  • 1 accepted solution
  • 115 Views
  • 4 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!