<?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: Cohesity Agent keeps triggering  powershell alarm in cortex xdr in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/516592#M2939</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/241462"&gt;@moversk&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason this alert is persistent is because you have whitelisted the Cohesity SHA256 to the allow list. Cortex XDR Hash verdict and hash exception is a pre-execution detection and prevention mechanism, while the alert generated is a Behavioral Threat which is a post execution module. In order to allow the execution for the BTP events, the recommendation is to create alert exceptions for the same. I am listing down the practice steps for you down below:&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Right click on the alert&amp;gt; Manage Alert&amp;gt; Create Alert Exception&lt;/LI&gt;
&lt;LI&gt;Choose the exception field parameters of your choice&lt;/LI&gt;
&lt;LI&gt;Choose the exception scope(&lt;/LI&gt;
&lt;LI&gt;for specific endpoints, you should have a exception profile created and mapped to those policy rules for those endpoints and choose "Profile", for global endpoints, choose "Global"&lt;/LI&gt;
&lt;LI&gt;Once created, right click on the alert &amp;gt; Retrieve Additional Data&amp;gt; Retrieve alert data. Action will be listed in the action center&lt;/LI&gt;
&lt;LI&gt;Wait for the alert data to be uploaded and download it from the action center&lt;/LI&gt;
&lt;LI&gt;Open a TAC case and report the event as false positive to be whitelisted in content updated&lt;/LI&gt;
&lt;LI&gt;Upon confirmation from the engineering team for this event to be whitelisted in the content, wait for the content update to be fetched to the endpoints and then remove the alert exception created initially.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Hope this answers your question.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Oct 2022 09:32:04 GMT</pubDate>
    <dc:creator>neelrohit</dc:creator>
    <dc:date>2022-10-03T09:32:04Z</dc:date>
    <item>
      <title>Cohesity Agent keeps triggering  powershell alarm in cortex xdr</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/516590#M2938</link>
      <description>&lt;P&gt;I have witelistet choesity agent but i keeps&amp;nbsp; trigger&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PowerShell script executing with iex from suspicious script source - Behavioral threat detected (rule: dotnet_iex_suspicious_source)&lt;BR /&gt;Sep 30th 2022 16:04:40 SYSTEM powershell.exe 25384 29488 Process Start Process Start Command Line : powershell -nologo -noninteractive -executionpolicy bypass -encodedcommand&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is ther anyway to whiteliste this to so cohesity agent do not keeps getting&amp;nbsp; blockt&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="moversk_0-1664788133676.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/44334i0270060E48A3D8E4/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="moversk_0-1664788133676.png" alt="moversk_0-1664788133676.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 09:12:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/516590#M2938</guid>
      <dc:creator>moversk</dc:creator>
      <dc:date>2022-10-03T09:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: Cohesity Agent keeps triggering  powershell alarm in cortex xdr</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/516592#M2939</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/241462"&gt;@moversk&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason this alert is persistent is because you have whitelisted the Cohesity SHA256 to the allow list. Cortex XDR Hash verdict and hash exception is a pre-execution detection and prevention mechanism, while the alert generated is a Behavioral Threat which is a post execution module. In order to allow the execution for the BTP events, the recommendation is to create alert exceptions for the same. I am listing down the practice steps for you down below:&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Right click on the alert&amp;gt; Manage Alert&amp;gt; Create Alert Exception&lt;/LI&gt;
&lt;LI&gt;Choose the exception field parameters of your choice&lt;/LI&gt;
&lt;LI&gt;Choose the exception scope(&lt;/LI&gt;
&lt;LI&gt;for specific endpoints, you should have a exception profile created and mapped to those policy rules for those endpoints and choose "Profile", for global endpoints, choose "Global"&lt;/LI&gt;
&lt;LI&gt;Once created, right click on the alert &amp;gt; Retrieve Additional Data&amp;gt; Retrieve alert data. Action will be listed in the action center&lt;/LI&gt;
&lt;LI&gt;Wait for the alert data to be uploaded and download it from the action center&lt;/LI&gt;
&lt;LI&gt;Open a TAC case and report the event as false positive to be whitelisted in content updated&lt;/LI&gt;
&lt;LI&gt;Upon confirmation from the engineering team for this event to be whitelisted in the content, wait for the content update to be fetched to the endpoints and then remove the alert exception created initially.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Hope this answers your question.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 09:32:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/516592#M2939</guid>
      <dc:creator>neelrohit</dc:creator>
      <dc:date>2022-10-03T09:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cohesity Agent keeps triggering  powershell alarm in cortex xdr</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/521269#M3142</link>
      <description>&lt;P&gt;look like it still triggers even with&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;exception profile&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.JPG" style="width: 415px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/45343i4492FCAB383A435D/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="1.JPG" alt="1.JPG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.JPG" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/45344iCC0486AC22ABA908/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2.JPG" alt="2.JPG" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2022 13:05:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cohesity-agent-keeps-triggering-powershell-alarm-in-cortex-xdr/m-p/521269#M3142</guid>
      <dc:creator>moversk</dc:creator>
      <dc:date>2022-11-15T13:05:17Z</dc:date>
    </item>
  </channel>
</rss>

