Help Identifying Applications Installed via CyberArk Elevation

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

Help Identifying Applications Installed via CyberArk Elevation

L2 Linker

I’ve created an “Elevate If Necessary” policy in CyberArk EPM for a specific user, with all applications included in the scope.

To track what applications were installed using the admin rights granted via this policy, I generated an Event Details report from the “Reports” section and filtered it by the Event Type = Installation. However, the report includes all installed applications on the machine, not just the ones installed using CyberArk’s elevation.

Could you please guide me on how to isolate and list only the applications that were installed using the admin privileges granted through the CyberArk policy?

1 accepted solution

Accepted Solutions

Just did a filter and searched all by selecting Trust only from Event types drop down and I get the impression it's mostly when a policy has a Trust Signature which means the policy allows something to install/execute because the code signing signature is essentially trusted, so if you created a Trust signature policy for HP and Cisco then all applications with that Trust signature would install without EPM blocking them, the wording of the signature has to be exact so if the signature is CISCO (12334455) then the trust signature with the name CISCO only wouldn't let it install. Also looking the logs on mine it seems to be that TRUST is mostly elevations for things we couldn't package in company portal/jamf self-service and policies we need in place for users to run tools which require further elevation like Visual studio and legacy apps build with admin, hope that makes sense. below I just got from AI but seems accurate as all linked to documentation from cyberark. We TRUST internal signatures so this Trust policy is specifically beneficial to our QA/Devs who routinely test - debug - update - package - release apps multiples times a day so we don't want EPM blocking those apps from installing/executing and even uninstalling!

 

here's the official documentation -

The event type "Trust" in CyberArk EPM indicates that an application managed by an Elevate policy was launched. On Linux agents, this event type is also used to collect privileged commands (such as those run with 

sudo

 

) EPM event type when default policy is Elevate unhandled applications Manage events – Event types.

Regarding your impression about the "Launch" event type:

"Launch" appears when an application that does not require elevated privileges is started. It does not specifically indicate that the application was opened using "Run as administrator" mode. Instead, if an application is started with elevated privileges due to an Elevate policy, the event type will be "Trust" Manage events – Event types.

Summary:

  • Trust:
  •  Application launched with an Elevate policy (elevated privileges).
  • Launch:
  •  Application launched without requiring elevation.

 

 

EPM event type when default policy is Elevate unhandled applications

Event types

View solution in original post

9 REPLIES 9

L5 Sessionator

I think you can just go into Policy audit and search JIT and it will pick up everything that was elevated with JiT bare in mind that when. You give Jit regular processes will start using JIT policy but as you're looking to see what's installed it should be obviously, if you've given JIT to lots of users then use the Filter and search by device. For example applications here are installed through JAMF and the JAMF EPM policy tends to pick this up so this immediately lets us know it was not local admin which installed the app, guess the same would apply to SCCM or intune.

 

Based on the knowledge sources, to identify applications installed via CyberArk EPM Just-in-Time (JIT) elevation, you can use the Policy Audit feature in the EPM management console. By searching for "JIT" in Policy Audit, you can view events where JIT elevation was applied. This will help you see which processes and activities—including installations—were performed while JIT admin rights were active.

Keep in mind:

  • When JIT is granted, all processes started during the JIT window will use the JIT policy, so installations and other elevated actions will be recorded under this policy.
  • If JIT has been granted to many users, use the filter options in Policy Audit to narrow results by device or user for more targeted investigation.

However, the knowledge sources do not provide a built-in way to directly isolate only the applications installed via JIT elevation from all other installations. You will need to review the Policy Audit events and correlate installation activities with the JIT elevation window for each user or device View policy audit events.

If you need to automate or further refine this process, the knowledge sources suggest using the API to retrieve audit events, which may help you correlate JIT elevation with installation events more efficiently Retrieve Policy Audit via API.

 

 

All feedback is reviewed by the team.

Answer based on the following sources:

View policy audit events

docs.cyberark.com/epm

EPM Policy Best Practices - Is JIT Really the Right Answer?community.cyberark.com/s

 

 

L4 Transporter

I think you can just go into Policy audit and search JIT and it will pick up everything that was elevated with JiT bare in mind that when. You give Jit regular processes will start using JIT policy but as you're looking to see what's installed it should be obviously, if you've given JIT to lots of users then use the Filter and search by device. For example applications here are installed through JAMF and the JAMF EPM policy tends to pick this up so this immediately lets us know it was not local admin which installed the app, guess the same would apply to SCCM or intune.

 

Based on the knowledge sources, to identify applications installed via CyberArk EPM Just-in-Time (JIT) elevation, you can use the Policy Audit feature in the EPM management console. By searching for "JIT" in Policy Audit, you can view events where JIT elevation was applied. This will help you see which processes and activities—including installations—were performed while JIT admin rights were active.

Keep in mind:

  • When JIT is granted, all processes started during the JIT window will use the JIT policy, so installations and other elevated actions will be recorded under this policy.
  • If JIT has been granted to many users, use the filter options in Policy Audit to narrow results by device or user for more targeted investigation.

However, the knowledge sources do not provide a built-in way to directly isolate only the applications installed via JIT elevation from all other installations. You will need to review the Policy Audit events and correlate installation activities with the JIT elevation window for each user or device View policy audit events.

If you need to automate or further refine this process, the knowledge sources suggest using the API to retrieve audit events, which may help you correlate JIT elevation with installation events more efficiently Retrieve Policy Audit via API.

 

 

All feedback is reviewed by the team.

Answer based on the following sources:

View policy audit events

docs.cyberark.com/epm

EPM Policy Best Practices - Is JIT Really the Right Answer?community.cyberark.com/s

 

 

Ah so go into Audit policy on the left at the bottom from within the SET then search this word in Audit event and maybe change the Application type and it will show you the installations! and to further delve search by Computer hostname using the filter button

Field_Content_versions_oct20__068Vy00000ZuUtsIAF.png

Ah so go into Audit policy on the left at the bottom from within the SET then search this word in Audit event and maybe change the Application type and it will show you the installations! and to further delve search by Computer hostname using the filter button

Field_Content_versions_oct20__068Vy00000ZuUtsIAF.png

Ah so go into Audit policy on the left at the bottom from within the SET then search this word in Audit event and maybe change the Application type and it will show you the installations! and to further delve search by Computer hostname using the filter button

Field_Content_versions_oct20__068Vy00000ZuUtsIAF.png

Great, thanks!

Quick question — what does the event type "Trust" indicate?

I was under the impression that "Launch" appears when a user attempts to open an existing application using "Run as administrator" mode. Is that correct?

 

Field_Content_versions_oct20__068Vy00000ZuvU6IAJ.png

Just did a filter and searched all by selecting Trust only from Event types drop down and I get the impression it's mostly when a policy has a Trust Signature which means the policy allows something to install/execute because the code signing signature is essentially trusted, so if you created a Trust signature policy for HP and Cisco then all applications with that Trust signature would install without EPM blocking them, the wording of the signature has to be exact so if the signature is CISCO (12334455) then the trust signature with the name CISCO only wouldn't let it install. Also looking the logs on mine it seems to be that TRUST is mostly elevations for things we couldn't package in company portal/jamf self-service and policies we need in place for users to run tools which require further elevation like Visual studio and legacy apps build with admin, hope that makes sense. below I just got from AI but seems accurate as all linked to documentation from cyberark. We TRUST internal signatures so this Trust policy is specifically beneficial to our QA/Devs who routinely test - debug - update - package - release apps multiples times a day so we don't want EPM blocking those apps from installing/executing and even uninstalling!

 

here's the official documentation -

The event type "Trust" in CyberArk EPM indicates that an application managed by an Elevate policy was launched. On Linux agents, this event type is also used to collect privileged commands (such as those run with 

sudo

 

) EPM event type when default policy is Elevate unhandled applications Manage events – Event types.

Regarding your impression about the "Launch" event type:

"Launch" appears when an application that does not require elevated privileges is started. It does not specifically indicate that the application was opened using "Run as administrator" mode. Instead, if an application is started with elevated privileges due to an Elevate policy, the event type will be "Trust" Manage events – Event types.

Summary:

  • Trust:
  •  Application launched with an Elevate policy (elevated privileges).
  • Launch:
  •  Application launched without requiring elevation.

 

 

EPM event type when default policy is Elevate unhandled applications

Event types

Just did a filter and searched all by selecting Trust only from Event types drop down and I get the impression it's mostly when a policy has a Trust Signature which means the policy allows something to install/execute because the code signing signature is essentially trusted, so if you created a Trust signature policy for HP and Cisco then all applications with that Trust signature would install without EPM blocking them, the wording of the signature has to be exact so if the signature is CISCO (12334455) then the trust signature with the name CISCO only wouldn't let it install. Also looking the logs on mine it seems to be that TRUST is mostly elevations for things we couldn't package in company portal/jamf self-service and policies we need in place for users to run tools which require further elevation like Visual studio and legacy apps build with admin, hope that makes sense. below I just got from AI but seems accurate as all linked to documentation from cyberark. We TRUST internal signatures so this Trust policy is specifically beneficial to our QA/Devs who routinely test - debug - update - package - release apps multiples times a day so we don't want EPM blocking those apps from installing/executing and even uninstalling!

 

here's the official documentation -

The event type "Trust" in CyberArk EPM indicates that an application managed by an Elevate policy was launched. On Linux agents, this event type is also used to collect privileged commands (such as those run with 

sudo

 

) EPM event type when default policy is Elevate unhandled applications Manage events – Event types.

Regarding your impression about the "Launch" event type:

"Launch" appears when an application that does not require elevated privileges is started. It does not specifically indicate that the application was opened using "Run as administrator" mode. Instead, if an application is started with elevated privileges due to an Elevate policy, the event type will be "Trust" Manage events – Event types.

Summary:

  • Trust:
  •  Application launched with an Elevate policy (elevated privileges).
  • Launch:
  •  Application launched without requiring elevation.

 

 

EPM event type when default policy is Elevate unhandled applications

Event types

Just did a filter and searched all by selecting Trust only from Event types drop down and I get the impression it's mostly when a policy has a Trust Signature which means the policy allows something to install/execute because the code signing signature is essentially trusted, so if you created a Trust signature policy for HP and Cisco then all applications with that Trust signature would install without EPM blocking them, the wording of the signature has to be exact so if the signature is CISCO (12334455) then the trust signature with the name CISCO only wouldn't let it install. Also looking the logs on mine it seems to be that TRUST is mostly elevations for things we couldn't package in company portal/jamf self-service and policies we need in place for users to run tools which require further elevation like Visual studio and legacy apps build with admin, hope that makes sense. below I just got from AI but seems accurate as all linked to documentation from cyberark. We TRUST internal signatures so this Trust policy is specifically beneficial to our QA/Devs who routinely test - debug - update - package - release apps multiples times a day so we don't want EPM blocking those apps from installing/executing and even uninstalling!

 

here's the official documentation -

The event type "Trust" in CyberArk EPM indicates that an application managed by an Elevate policy was launched. On Linux agents, this event type is also used to collect privileged commands (such as those run with 

sudo

 

) EPM event type when default policy is Elevate unhandled applications Manage events – Event types.

Regarding your impression about the "Launch" event type:

"Launch" appears when an application that does not require elevated privileges is started. It does not specifically indicate that the application was opened using "Run as administrator" mode. Instead, if an application is started with elevated privileges due to an Elevate policy, the event type will be "Trust" Manage events – Event types.

Summary:

  • Trust:
  •  Application launched with an Elevate policy (elevated privileges).
  • Launch:
  •  Application launched without requiring elevation.

 

 

EPM event type when default policy is Elevate unhandled applications

Event types

  • 1 accepted solution
  • 102 Views
  • 9 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!