<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users? in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416117#M7563</link>
    <description>&lt;P&gt;Correct me if I am wrong, but I understand that the following is Best Practice for elevating commands:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create an Allow Policy (without child-processes) for PowerShell/Command Prompt. Make this a parent policy.&lt;/LI&gt;&lt;LI&gt;Create an Elevation Policy (without child-processes) for PowerShell/Command Prompt. Add parameters next to executable i.e. powershell.exe --Parameter&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2024 20:39:00 GMT</pubDate>
    <dc:creator>mcarlos</dc:creator>
    <dc:date>2024-08-27T20:39:00Z</dc:date>
    <item>
      <title>How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416117#M7563</link>
      <description>&lt;P&gt;Correct me if I am wrong, but I understand that the following is Best Practice for elevating commands:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create an Allow Policy (without child-processes) for PowerShell/Command Prompt. Make this a parent policy.&lt;/LI&gt;&lt;LI&gt;Create an Elevation Policy (without child-processes) for PowerShell/Command Prompt. Add parameters next to executable i.e. powershell.exe --Parameter&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 20:39:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416117#M7563</guid>
      <dc:creator>mcarlos</dc:creator>
      <dc:date>2024-08-27T20:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416118#M7564</link>
      <description>&lt;P&gt;Hi @Martin Carlos​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are few approaches you can try,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 10:59:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416118#M7564</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-08-28T10:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416119#M7565</link>
      <description>&lt;P&gt;We've started working with our developers to have them sign their powershell scripts, and the we will elevate if necessary signed powershell scripts.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2024 16:02:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416119#M7565</guid>
      <dc:creator>Carl_Chipman</dc:creator>
      <dc:date>2024-08-28T16:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416120#M7566</link>
      <description>&lt;P&gt;oh cool  thats something we haven't thought off so is this the same as getting an internal QA app signed??&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 10:32:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416120#M7566</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-01T10:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to appropriately map command-line arguments (PowerShell/Command Prompt) for thousands of users?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416121#M7567</link>
      <description>&lt;P&gt;oh cool  thats something we haven't thought off so is this the same as getting an internal QA app signed??&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 10:32:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/how-to-appropriately-map-command-line-arguments-powershell/m-p/1416121#M7567</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-01T10:32:18Z</dc:date>
    </item>
  </channel>
</rss>

