<?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: Preventing (non-elevated) run of unsigned scripts in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421561#M9113</link>
    <description>&lt;P&gt;Hi @Adam Marks​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ps1scripts can be blocked in the way you mentioned above. please check and let us know..&lt;/P&gt;&lt;P&gt;On the other hand, bat and cmd can't be typically signed so the Publisher is not valid for these types.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arik.,&lt;/P&gt;</description>
    <pubDate>Tue, 03 Feb 2026 16:45:57 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-02-03T16:45:57Z</dc:date>
    <item>
      <title>Preventing (non-elevated) run of unsigned scripts</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421560#M9112</link>
      <description>&lt;P&gt;We are currently attempting to move away from AppLocker, and don't really want to wade into the minefield of WDAC in an estate with a lot of historic baggage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As part of our security approval process for specific work, we need to ensure that standard users are unable to run unsigned scripts - bat, cmd, ps1, you name it, if they don't have a proper digital signature with a certification chain, users should not be allowed to run them, elevated or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attempted to create a new advanced policy with a Block rule, specifying "Script" with the simple parameter "Publisher: Unsigned". &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With this policy set to highest-priority in the chain, it doesn't appear to have any effect, and instead unsigned scripts are seemingly "managed" by the default global 'detect privileged unhandled applications' policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can someone guide us in how we can accomplish the goal described above?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 11:44:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421560#M9112</guid>
      <dc:creator>AdamMarks</dc:creator>
      <dc:date>2026-01-20T11:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Preventing (non-elevated) run of unsigned scripts</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421561#M9113</link>
      <description>&lt;P&gt;Hi @Adam Marks​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ps1scripts can be blocked in the way you mentioned above. please check and let us know..&lt;/P&gt;&lt;P&gt;On the other hand, bat and cmd can't be typically signed so the Publisher is not valid for these types.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arik.,&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 16:45:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421561#M9113</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-03T16:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Preventing (non-elevated) run of unsigned scripts</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421562#M9114</link>
      <description>&lt;P&gt;Thanks for the response - it does make sense that this would only work on scripts that can be signed!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have now tested again, and my findings are mixed:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The script is now marked correctly as "Block" in EPM properties&lt;/LI&gt;&lt;LI&gt;When attempting to run the file simply by double-clicking, it is blocked as expected&lt;/LI&gt;&lt;LI&gt;HOWEVER - if I run the script via powershell command line, it &lt;B&gt;still runs.&lt;/B&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Is this expected behaviour?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 08:59:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421562#M9114</guid>
      <dc:creator>AdamMarks</dc:creator>
      <dc:date>2026-02-04T08:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: Preventing (non-elevated) run of unsigned scripts</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421563#M9115</link>
      <description>&lt;P&gt;Ok, now figured out that PS1 scripts are indeed blocked via command line as long as execution policy is set to Default.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HOWEVER - one issue I am now observing is that the rule on unsigned scripts is not applying to VBS scripts, which &lt;B&gt;can&lt;/B&gt; be digitally signed. Are these typically covered by a Script based policy?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 11:17:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/preventing-non-elevated-run-of-unsigned-scripts/m-p/1421563#M9115</guid>
      <dc:creator>AdamMarks</dc:creator>
      <dc:date>2026-02-04T11:17:29Z</dc:date>
    </item>
  </channel>
</rss>

