How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?

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

How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?

L3 Networker

Correct me if I am wrong, but I understand that the following is Best Practice for elevating commands:

  1. Create an Allow Policy (without child-processes) for PowerShell/Command Prompt. Make this a parent policy.
  2. Create an Elevation Policy (without child-processes) for PowerShell/Command Prompt. Add parameters next to executable i.e. powershell.exe --Parameter

 

However, this does not seem to work efficiently for thousands of users running hundreds of different commands. Is there a better approach to this? Any suggestions are appreciated. Thank you.

 

4 REPLIES 4

L7 Applicator

Hi @Martin Carlos​ 

 

You’re correct that the approach you’ve described is a common best practice for managing command-line arguments in EPM. However, when scaling to thousands of users with diverse command needs, this method can become inefficient.

 

Here are few approaches you can try,

 

  • Instead of specifying each command individually, consider using wildcards or regular expressions in your Elevation Policies to match a broader set of command-line arguments. This can reduce the number of individual policies required.
  • If there are common sets of commands or parameters that multiple users need, you can group them under a single policy. This simplifies management and reduces the number of policies you need to create.
  • Segment users into roles or groups based on their typical usage patterns and create policies that apply to each role. This allows you to manage a smaller number of policies while still covering the necessary commands for different user types.
  • Implement centralized logging to track which commands are being used most frequently and adjust your policies accordingly. This helps optimize and refine your policy set over time.

 

Hope it helps !

L2 Linker

We've started working with our developers to have them sign their powershell scripts, and the we will elevate if necessary signed powershell scripts.

L5 Sessionator

oh cool thats something we haven't thought off so is this the same as getting an internal QA app signed??

L4 Transporter

oh cool thats something we haven't thought off so is this the same as getting an internal QA app signed??

  • 18 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!