What are users actually self-installing (not just elevating) via EPM?

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

What are users actually self-installing (not just elevating) via EPM?

L4 Transporter

Sorry for the basic question. We unfortunately don't have significant time to devote to EPM, and due this to (as well as other organizational challenges) remain in Quick Start for 2+ years. Which is fine. But as we're being asked to reduce our EPM licensing, I'm trying to find a reliable way to report on applications that our EPM users (a small subset of our overall population) are self-installing, to be able to take this to our application delivery teams and have them packaged. Our endpoints are locked down by GPO and other methods, and most corporate applications are deployed through your typical tools (SCCM/Intune). We've been down this road several times. Policy Audit has not helped, as we can't easily differentiate between installs and elevations. Application Inventory includes things folks get by default or subsequently request thru accepted methods (there's no company application inventory, so I can't determine a delta). The latest attempt was looking at an agent (example: my own) in the Endpoints (Beta) tab. The Applications List -> Installed By does not properly reflect applications I know I download and installed myself thru EPM, to test this out. The overall goal is to root out folks that are not using EPM for its intended purposes - apps that have to elevate, actual Developers that need to continually install/update and can't be sustainably supported through other means. We're hoping to find teams that had perhaps been approved for EPM, are using it as a workaround to going through the approved processes (having an app packaged) and maybe only ever self-installed 1-2 apps, which don't need to elevate, and we can transition them over and get them off EPM. One last thing. JIT (something else we've looked at) isn't really the use case here. Those folks would still need agents to make JIT requests thru EPM. Basically we're trying to redirect installations to where they should be done. TIA.

1 accepted solution

Accepted Solutions

L5 Sessionator

https://community.cyberark.com/s/question/0D5Vy00000oPS7PKAW/looking-to-find-the-computers-with-epm-... -

Someone else asked a similar question.

I would look at exporting a report of all events and then using a filter in excel to look for setup.exe msi, installers - I guess they need to be instructed on not manually installing apps, ensure that QA developers cant install/uninstall/execute in-house apps by creating code signing certificates for those apps and ensure you have trust policies in place, also discussed on the epm forum if any of your Dev's are QA's.

I would look to create a report rather than manually going through the policy audit and Catalogue, if you go to reports - events and create a report on all events last 90 days and then filter the columns and look for setup/installer/msi.exe etc i guess that will give you an answer on who's essentially bypassed mdm to use JIT to install things and to further remove click the link posted and see how to create a policy report of unused policies.

 

 

I guess you should look to build out a workflow so you don't just give JIT rights to a user so they can bypass sccm/intune to install an application, this puts more pressure on epm to create policies to allow it to uninstall, reconfigure, update. Obviously you would ideally have some sort of ITSM integration so when users elevate a ticket is created and they're asked to fill in mandatory boxes, or pre filled hostname, user justification etc ?

 

For JIT we only let our EUC staff use it for troubleshooting hardware/software, test new infra/euc changes and work on bugs and when vendors are onsite and need to test/fix things, must admit using it a bit with developers where there's no solution but again its really for troubleshooting purposes only. We're heavy on the use of MDM and repo's and securing everything down to limit admin access to the point very few use it through AAD groups for high risk processes.

 

The below is taken from AI but seems accurate

To reliably identify what users are actually self-installing (not just elevating) via CyberArk EPM, especially in a Quick Start scenario, you should leverage EPM’s event reporting capabilities. Here’s a focused approach based on CyberArk best practices and available features:

  1. Export and Analyze Event Reports:
  2. Use the EPM console to generate an Events or Application Catalog report for your desired timeframe (e.g., last 90 days). These reports provide detailed information about application executions, including installer files like 
  3. setup.exe
  4.  
  5. , 
  6. .msi
  7.  
  8. , and other common installer types. Export the report to CSV and use Excel to filter for installer-related filenames or paths. This will help you pinpoint which applications users are actually installing themselves, rather than just elevating existing applications. This method is recommended in the community and aligns with CyberArk’s reporting best practices [EPM Policy Best Practices – Policy Review Using Reports].
  9. Policy Audit Details Report:
  10. If you have Policy Audit enabled (especially with Quick Start policies), the Policy Audit Details report can capture all events covered by those policies. While it may require some filtering, it can help differentiate between installation and elevation events by focusing on installer executables and their context [Applications/executables report].
  11. Application Catalog and Certificate Filtering:
  12. The Application Catalog allows you to search for applications by signature, publisher, or filename. You can filter for unsigned or specifically signed installer files, which is useful for tracking in-house or QA-developed apps. This can help you identify if users are installing applications that should be managed or packaged centrally [Tracking Certificates issued by PKI teams?].
  13. Workflow and ITSM Integration:
  14. Consider integrating EPM with your ITSM system (like ServiceNow) to require justification and ticketing for elevation or installation requests. This not only provides an audit trail but also discourages users from bypassing standard application delivery processes [EPM Policy Best Practices: Is JIT Really the Right Answer?].
  15. JIT Usage Monitoring:
  16. JIT elevation should be reserved for break-glass or troubleshooting scenarios, not routine installations. Monitor JIT requests using the Events report and create policies for recurring requests to minimize misuse [EPM Best Practices – Health check tasks].

Summary of Steps:

  • Generate an Events or Application Catalog report for all endpoints with EPM agents.
  • Filter for installer-related executables (e.g., 
  • setup.exe
  •  
  • , 
  • .msi
  • ).
  • Review the “Installed By” or user context columns to identify self-installs.
  • Use this data to engage with application delivery teams for packaging and to identify users or teams misusing EPM for installations.

If you find that the “Installed By” field in the Endpoints (Beta) tab is unreliable, rely on the raw event data from the reports as described above. This approach is supported by CyberArk community best practices and should help you achieve your goal of identifying and redirecting self-installation activity.

If you need more granular tracking (e.g., by certificate or publisher), the Application Catalog’s filtering capabilities can assist, but for most use cases, event report analysis is the most direct and reliable method.

sed on the following sources:

 

View event raw details

Manage events

 

 

 

 

View solution in original post

3 REPLIES 3

L5 Sessionator

https://community.cyberark.com/s/question/0D5Vy00000oPS7PKAW/looking-to-find-the-computers-with-epm-... -

Someone else asked a similar question.

I would look at exporting a report of all events and then using a filter in excel to look for setup.exe msi, installers - I guess they need to be instructed on not manually installing apps, ensure that QA developers cant install/uninstall/execute in-house apps by creating code signing certificates for those apps and ensure you have trust policies in place, also discussed on the epm forum if any of your Dev's are QA's.

I would look to create a report rather than manually going through the policy audit and Catalogue, if you go to reports - events and create a report on all events last 90 days and then filter the columns and look for setup/installer/msi.exe etc i guess that will give you an answer on who's essentially bypassed mdm to use JIT to install things and to further remove click the link posted and see how to create a policy report of unused policies.

 

 

I guess you should look to build out a workflow so you don't just give JIT rights to a user so they can bypass sccm/intune to install an application, this puts more pressure on epm to create policies to allow it to uninstall, reconfigure, update. Obviously you would ideally have some sort of ITSM integration so when users elevate a ticket is created and they're asked to fill in mandatory boxes, or pre filled hostname, user justification etc ?

 

For JIT we only let our EUC staff use it for troubleshooting hardware/software, test new infra/euc changes and work on bugs and when vendors are onsite and need to test/fix things, must admit using it a bit with developers where there's no solution but again its really for troubleshooting purposes only. We're heavy on the use of MDM and repo's and securing everything down to limit admin access to the point very few use it through AAD groups for high risk processes.

 

The below is taken from AI but seems accurate

To reliably identify what users are actually self-installing (not just elevating) via CyberArk EPM, especially in a Quick Start scenario, you should leverage EPM’s event reporting capabilities. Here’s a focused approach based on CyberArk best practices and available features:

  1. Export and Analyze Event Reports:
  2. Use the EPM console to generate an Events or Application Catalog report for your desired timeframe (e.g., last 90 days). These reports provide detailed information about application executions, including installer files like 
  3. setup.exe
  4.  
  5. , 
  6. .msi
  7.  
  8. , and other common installer types. Export the report to CSV and use Excel to filter for installer-related filenames or paths. This will help you pinpoint which applications users are actually installing themselves, rather than just elevating existing applications. This method is recommended in the community and aligns with CyberArk’s reporting best practices [EPM Policy Best Practices – Policy Review Using Reports].
  9. Policy Audit Details Report:
  10. If you have Policy Audit enabled (especially with Quick Start policies), the Policy Audit Details report can capture all events covered by those policies. While it may require some filtering, it can help differentiate between installation and elevation events by focusing on installer executables and their context [Applications/executables report].
  11. Application Catalog and Certificate Filtering:
  12. The Application Catalog allows you to search for applications by signature, publisher, or filename. You can filter for unsigned or specifically signed installer files, which is useful for tracking in-house or QA-developed apps. This can help you identify if users are installing applications that should be managed or packaged centrally [Tracking Certificates issued by PKI teams?].
  13. Workflow and ITSM Integration:
  14. Consider integrating EPM with your ITSM system (like ServiceNow) to require justification and ticketing for elevation or installation requests. This not only provides an audit trail but also discourages users from bypassing standard application delivery processes [EPM Policy Best Practices: Is JIT Really the Right Answer?].
  15. JIT Usage Monitoring:
  16. JIT elevation should be reserved for break-glass or troubleshooting scenarios, not routine installations. Monitor JIT requests using the Events report and create policies for recurring requests to minimize misuse [EPM Best Practices – Health check tasks].

Summary of Steps:

  • Generate an Events or Application Catalog report for all endpoints with EPM agents.
  • Filter for installer-related executables (e.g., 
  • setup.exe
  •  
  • , 
  • .msi
  • ).
  • Review the “Installed By” or user context columns to identify self-installs.
  • Use this data to engage with application delivery teams for packaging and to identify users or teams misusing EPM for installations.

If you find that the “Installed By” field in the Endpoints (Beta) tab is unreliable, rely on the raw event data from the reports as described above. This approach is supported by CyberArk community best practices and should help you achieve your goal of identifying and redirecting self-installation activity.

If you need more granular tracking (e.g., by certificate or publisher), the Application Catalog’s filtering capabilities can assist, but for most use cases, event report analysis is the most direct and reliable method.

sed on the following sources:

 

View event raw details

Manage events

 

 

 

 

L4 Transporter

https://community.cyberark.com/s/question/0D5Vy00000oPS7PKAW/looking-to-find-the-computers-with-epm-... -

Someone else asked a similar question.

I would look at exporting a report of all events and then using a filter in excel to look for setup.exe msi, installers - I guess they need to be instructed on not manually installing apps, ensure that QA developers cant install/uninstall/execute in-house apps by creating code signing certificates for those apps and ensure you have trust policies in place, also discussed on the epm forum if any of your Dev's are QA's.

I would look to create a report rather than manually going through the policy audit and Catalogue, if you go to reports - events and create a report on all events last 90 days and then filter the columns and look for setup/installer/msi.exe etc i guess that will give you an answer on who's essentially bypassed mdm to use JIT to install things and to further remove click the link posted and see how to create a policy report of unused policies.

 

 

I guess you should look to build out a workflow so you don't just give JIT rights to a user so they can bypass sccm/intune to install an application, this puts more pressure on epm to create policies to allow it to uninstall, reconfigure, update. Obviously you would ideally have some sort of ITSM integration so when users elevate a ticket is created and they're asked to fill in mandatory boxes, or pre filled hostname, user justification etc ?

 

For JIT we only let our EUC staff use it for troubleshooting hardware/software, test new infra/euc changes and work on bugs and when vendors are onsite and need to test/fix things, must admit using it a bit with developers where there's no solution but again its really for troubleshooting purposes only. We're heavy on the use of MDM and repo's and securing everything down to limit admin access to the point very few use it through AAD groups for high risk processes.

 

The below is taken from AI but seems accurate

To reliably identify what users are actually self-installing (not just elevating) via CyberArk EPM, especially in a Quick Start scenario, you should leverage EPM’s event reporting capabilities. Here’s a focused approach based on CyberArk best practices and available features:

  1. Export and Analyze Event Reports:
  2. Use the EPM console to generate an Events or Application Catalog report for your desired timeframe (e.g., last 90 days). These reports provide detailed information about application executions, including installer files like 
  3. setup.exe
  4.  
  5. , 
  6. .msi
  7.  
  8. , and other common installer types. Export the report to CSV and use Excel to filter for installer-related filenames or paths. This will help you pinpoint which applications users are actually installing themselves, rather than just elevating existing applications. This method is recommended in the community and aligns with CyberArk’s reporting best practices [EPM Policy Best Practices – Policy Review Using Reports].
  9. Policy Audit Details Report:
  10. If you have Policy Audit enabled (especially with Quick Start policies), the Policy Audit Details report can capture all events covered by those policies. While it may require some filtering, it can help differentiate between installation and elevation events by focusing on installer executables and their context [Applications/executables report].
  11. Application Catalog and Certificate Filtering:
  12. The Application Catalog allows you to search for applications by signature, publisher, or filename. You can filter for unsigned or specifically signed installer files, which is useful for tracking in-house or QA-developed apps. This can help you identify if users are installing applications that should be managed or packaged centrally [Tracking Certificates issued by PKI teams?].
  13. Workflow and ITSM Integration:
  14. Consider integrating EPM with your ITSM system (like ServiceNow) to require justification and ticketing for elevation or installation requests. This not only provides an audit trail but also discourages users from bypassing standard application delivery processes [EPM Policy Best Practices: Is JIT Really the Right Answer?].
  15. JIT Usage Monitoring:
  16. JIT elevation should be reserved for break-glass or troubleshooting scenarios, not routine installations. Monitor JIT requests using the Events report and create policies for recurring requests to minimize misuse [EPM Best Practices – Health check tasks].

Summary of Steps:

  • Generate an Events or Application Catalog report for all endpoints with EPM agents.
  • Filter for installer-related executables (e.g., 
  • setup.exe
  •  
  • , 
  • .msi
  • ).
  • Review the “Installed By” or user context columns to identify self-installs.
  • Use this data to engage with application delivery teams for packaging and to identify users or teams misusing EPM for installations.

If you find that the “Installed By” field in the Endpoints (Beta) tab is unreliable, rely on the raw event data from the reports as described above. This approach is supported by CyberArk community best practices and should help you achieve your goal of identifying and redirecting self-installation activity.

If you need more granular tracking (e.g., by certificate or publisher), the Application Catalog’s filtering capabilities can assist, but for most use cases, event report analysis is the most direct and reliable method.

sed on the following sources:

 

View event raw details

Manage events

 

 

 

 

Thanks very much for the detailed response. I will also check out the similar post. You've sort of hit on our core challenge in the process. We have no approved software library, so even if we were to be building policy off of installation activity, we're always playing catch up. Especially since there are also no guidelines around what users can download and install (if they have EPM). It's holding back the ocean and not our issue to solve organizationally. We're mainly interested in clawing back EPM from folks who aren't even using it for that. Anyway, thanks for the response.

  • 1 accepted solution
  • 16 Views
  • 3 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!