<?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 Re: Powershell elevation best practice in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348190#M2788</link>
    <description>&lt;P&gt;Hi @John F​&amp;nbsp;, Elevating powershell.exe is basically providing admin rights to the end user. The best practice would be to ask users to capture what they need to do, in a PowerShell script and only elevate that specific script by hash or signature. If elevating powershell.exe is still needed, you can apply step-up authentication upon launch and also apply some restrictions on the shell, such as access to network shares, registry, local files, and the internet.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Yossi&lt;/P&gt;</description>
    <pubDate>Tue, 10 Oct 2023 10:57:32 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-10-10T10:57:32Z</dc:date>
    <item>
      <title>Powershell elevation best practice</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348189#M2787</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;we have requests to allow powershell to be run elevated if necessary, where local admin rights are removed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the risk?&lt;/P&gt;&lt;P&gt;What can be done by default through PS, when ran elevated, but elevate child processes is disabled?&lt;/P&gt;&lt;P&gt;How would you allow the elevation of PS, but tighten it´s execution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for sharing your best practice.&lt;/P&gt;&lt;P&gt;J.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 14:51:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348189#M2787</guid>
      <dc:creator>John_F</dc:creator>
      <dc:date>2023-10-09T14:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell elevation best practice</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348190#M2788</link>
      <description>&lt;P&gt;Hi @John F​&amp;nbsp;, Elevating powershell.exe is basically providing admin rights to the end user. The best practice would be to ask users to capture what they need to do, in a PowerShell script and only elevate that specific script by hash or signature. If elevating powershell.exe is still needed, you can apply step-up authentication upon launch and also apply some restrictions on the shell, such as access to network shares, registry, local files, and the internet.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Yossi&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 10:57:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348190#M2788</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-10-10T10:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell elevation best practice</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348191#M2789</link>
      <description>&lt;P&gt;Hi @Yossi Dantes​&amp;nbsp;, thanks for your suggestions above.&lt;/P&gt;&lt;P&gt;However, if PowerShell is elevated, without child processes and local admin rights are removed. Can you really achieve that much with it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tried a couple of commands using PowerShell in elevated mode, but as soon as the commands triggers a tasks that Windows OS judge as needing admin rights, the commands stops.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only then can non privileged actions could be achieved by the OS or if "Admin tasks" or specific applications are elevated in a separate policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would that be correct?&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julien&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 07:57:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/powershell-elevation-best-practice/m-p/1348191#M2789</guid>
      <dc:creator>John_F</dc:creator>
      <dc:date>2023-10-19T07:57:13Z</dc:date>
    </item>
  </channel>
</rss>

