EPM - How to Contain User-Based Applications

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
4 min read
L1 Bithead
No ratings

User-Based Apps are Installer based or portable programs that users can deploy to their profiles without administrative approval. These applications reside in directories where users have full control (e.g., %USERPROFILE% on Windows or /Users/{username}/ on macOS).

While some of these apps are legitimate, they present three primary challenges:

  1. Lack of Oversight: Without non-privileged application controls, users and AI agents can run software with impunity, leading to the spread of "Shadow IT" and unauthorized software.

  2. Strategic Misalignment: Attempting full application control before privilege management is established often causes event overload and contradicts EPM Success Path best practices.

  3. Resource Constraints: Many organizations lack the operational capacity to manage comprehensive application control beyond their existing privilege management efforts.

 

These portable-apps are growing in popularity especially with the proliferation of Agentic AI.  AI solutions such as Claude, Cursor, and many others all can be installed within a user profile and be utilized for privilege escalation via relatively trivial mechanisms. 

Steps

The Solution

This article introduces a scalable policy framework that allows you to manage user-based applications effectively at any point in your EPM journey. Because these applications  run without administrative rights, the framework utilizes a purpose-driven order of precedence consisting of Allow and Block policies. This approach integrates seamlessly with the QuickStart methodology, providing robust application control that evolves with your EPM Success Path journey.

 

This policy framework consists of three layers to manage user-based applications. 

 

ka3Vy00000CUdxtIAD__eid=ka3Vy00000CUdxt&feoid=00N2J000009R3kv&refid=0EMVy00000psrpx.png

Layer 1 — Risk‑Reduction Controls

The first layer restricts all user‑based applications from invoking sensitive OS components that are commonly abused by attackers or leveraged for automation by Agentic AI. This establishes a baseline reduction in privilege exposure.


Layer 2 — Allowlist for Approved User‑Based Apps

The second layer introduces an allowlist for sanctioned user‑based applications. The associated application group includes sample entries that you should refine by removing irrelevant examples and adding known, approved apps. This layer acts as a placeholder for ongoing discovery: as new legitimate user‑based apps are identified and approved, they should be added here following the same matching criteria in the examples.

Layer 3 — Discovery and Default‑Deny

The final layer contains two policies:

  • One to discover and log user‑based applications.

  • A second, higher‑priority policy that enforces a default‑deny posture once discovery is complete. When enabled, this default‑deny policy supersedes the discovery policy, making it optional to disable or remove the discovery rule.

After default‑deny in the final layer is activated, any unapproved or unknown user‑based application will be blocked and logged. These logs can then be used to update the allowlist as needed.

These policies are aligned with QuickStart, intersecting appropriately with risk reduction and privilege management to ensure compatibility. Customers using QuickStart can import them knowing they'll function as intended without disrupting QuickStart's design principles.

 

ka3Vy00000CUdxtIAD__eid=ka3Vy00000CUdxt&feoid=00N2J000009R3kv&refid=0EMVy00000psfjy.png

 

Pro-Tip

When building definitions for Allowed User-Based Apps, use the following criteria:

  • Location -  %USERPROFILE%, including any subfolders. This approach ensures that the policy  targets the user profile correctly, whether it's in the default directory (C:\Users), on a secondary drive, or part of a roaming profile.
  • Publisher - If the app is signed, this option securely identifies the vendor. To approve all apps from a specific vendor, combine Publisher with Location and this is all you need.
  • Original filename -   If you only want to approve a specific app from a vendor consider adding Original filename to the definition.  This is metadata compiled into an app’s file, making it a reliable way to identify a specific vendor app since it remains secure when the file is signed.
  • Checksum - When a file isn't signed, the best way to verify its identity is by using the checksum, which is particularly important for applications stored in user profiles where metadata and filenames can be altered.
Rate this article: