EPM - Application Coverage by Policies

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

Endpoint Privilege Manager (EPM) Articles
2 min read
L0 Member
No ratings

Question

Please explain the expected behavior of the "Application Coverage by Policies" in the EPM Console.
 

Answer

The following information was is based off behavior of EPM Console version 24.5.1.4050
  • If a policy is inactive, the "Application Coverage by Policies" still considers the application to be "handled"
  • If a policy was deleted or is inactive but the application still exists in a custom application group (EPM > Policies > Application Groups), "Application Coverage by Policies" considers the application to be handled. This is shown in the "Application Coverage by Policies" as...
Priority: 1
Action: N/A
Type: Custom application groups
 
Note: This entry always shows as "inactive"
  • Source Type "OldApplication" means it was installed before the EPM Agent 
  • "Application Coverage by Policies" data is calculated based on current data of application catalog (which has retention of 2 years total)
  • The "Application Coverage by Policies" report data itself has retention of 3 months since the last time the "Analyze coverage" button was clicked.
  • When you delete the custom application group and perform a new "Analyze coverage", the custom application group shown in the pane on the right should now be cleared out. However, on the main "Application Coverage by policies" screen, the application can still be shown as "Handled". This is because the deletion or changing of a policy is not immediate and can vary by several minutes. 
Rate this article: