<?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: Process Explorer Triggering Cortex XDR Alert – Clarification Needed in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/process-explorer-triggering-cortex-xdr-alert-clarification/m-p/1227964#M8284</link>
    <description>&lt;P&gt;&lt;SPAN&gt;From the logs, I see that the load of 'procexp.sys' was blocked by XDR. The BTP rule that blocked this activity was introduced in CU 640 aims to protect our agent from a potential vulnerability that could be exploited by the "procexp.sys" driver. When used maliciously, this driver's kernel functions could pose a risk to our agent. As a precaution, when this driver is being loaded by any application, the agent will prevent its loading but will allow the application itself to run (the source process will not be terminated).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The "procexp.sys" driver is commonly associated with tools like "Process Explorer" (procexp.exe). The driver is loaded when these applications are executed with administrative privileges, triggering an alert..&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 02 May 2025 11:04:25 GMT</pubDate>
    <dc:creator>tlmarques</dc:creator>
    <dc:date>2025-05-02T11:04:25Z</dc:date>
    <item>
      <title>Process Explorer Triggering Cortex XDR Alert – Clarification Needed</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/process-explorer-triggering-cortex-xdr-alert-clarification/m-p/1227751#M8280</link>
      <description>&lt;P class="" data-start="259" data-end="262"&gt;Hi,&lt;/P&gt;
&lt;P class="" data-start="264" data-end="430"&gt;When our system administration team uses &lt;STRONG data-start="305" data-end="325"&gt;Process Explorer&lt;/STRONG&gt; (Microsoft version), &lt;LI-PRODUCT title="Cortex XDR" id="Cortex_XDR"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&amp;nbsp;does &lt;STRONG data-start="363" data-end="376"&gt;not block&lt;/STRONG&gt; the execution, but it &lt;STRONG data-start="399" data-end="429"&gt;generates alerts/incidents&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="" data-start="432" data-end="450"&gt;&lt;STRONG data-start="432" data-end="450"&gt;Alert Details:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-start="451" data-end="833"&gt;
&lt;LI class="" data-start="451" data-end="499"&gt;
&lt;P class="" data-start="453" data-end="499"&gt;&lt;STRONG data-start="453" data-end="468"&gt;Alert Name:&lt;/STRONG&gt; Impair Defenses - 3645069560&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="500" data-end="609"&gt;
&lt;P class="" data-start="502" data-end="609"&gt;&lt;STRONG data-start="502" data-end="518"&gt;Description:&lt;/STRONG&gt; A tampering-capable driver with the original name &lt;CODE data-start="569" data-end="582"&gt;procexp.sys&lt;/CODE&gt; was loaded on the system&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="610" data-end="635"&gt;
&lt;P class="" data-start="612" data-end="635"&gt;&lt;STRONG data-start="612" data-end="623"&gt;Source:&lt;/STRONG&gt; XDR Agent&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="636" data-end="680"&gt;
&lt;P class="" data-start="638" data-end="680"&gt;&lt;STRONG data-start="638" data-end="649"&gt;Module:&lt;/STRONG&gt; Behavioral Threat Protection&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="681" data-end="706"&gt;
&lt;P class="" data-start="683" data-end="706"&gt;&lt;STRONG data-start="683" data-end="696"&gt;Category:&lt;/STRONG&gt; Malware&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="707" data-end="729"&gt;
&lt;P class="" data-start="709" data-end="729"&gt;&lt;STRONG data-start="709" data-end="722"&gt;Severity:&lt;/STRONG&gt; High&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="730" data-end="765"&gt;
&lt;P class="" data-start="732" data-end="765"&gt;&lt;STRONG data-start="732" data-end="743"&gt;Action:&lt;/STRONG&gt; Prevented (Blocked)&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="766" data-end="799"&gt;
&lt;P class="" data-start="768" data-end="799"&gt;&lt;STRONG data-start="768" data-end="786"&gt;Agent Version:&lt;/STRONG&gt; 8.7.0.7735&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="800" data-end="833"&gt;
&lt;P class="" data-start="802" data-end="833"&gt;&lt;STRONG data-start="802" data-end="822"&gt;Content Version:&lt;/STRONG&gt; 1750-15130&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="" data-start="835" data-end="856"&gt;&lt;STRONG data-start="835" data-end="856"&gt;My questions are:&lt;/STRONG&gt;&lt;/P&gt;
&lt;OL data-start="857" data-end="1080"&gt;
&lt;LI class="" data-start="857" data-end="968"&gt;
&lt;P class="" data-start="860" data-end="968"&gt;Is there a way to prevent this alert from being triggered when using legitimate tools like Process Explorer?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="" data-start="969" data-end="1080"&gt;
&lt;P class="" data-start="972" data-end="1080"&gt;Why is the software still able to run, even though the driver is flagged as vulnerable or tampering-capable?&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P class="" data-start="1082" data-end="1117"&gt;Thanks in advance for your support.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 09:49:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/process-explorer-triggering-cortex-xdr-alert-clarification/m-p/1227751#M8280</guid>
      <dc:creator>tlmarques</dc:creator>
      <dc:date>2025-04-30T09:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: Process Explorer Triggering Cortex XDR Alert – Clarification Needed</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/process-explorer-triggering-cortex-xdr-alert-clarification/m-p/1227964#M8284</link>
      <description>&lt;P&gt;&lt;SPAN&gt;From the logs, I see that the load of 'procexp.sys' was blocked by XDR. The BTP rule that blocked this activity was introduced in CU 640 aims to protect our agent from a potential vulnerability that could be exploited by the "procexp.sys" driver. When used maliciously, this driver's kernel functions could pose a risk to our agent. As a precaution, when this driver is being loaded by any application, the agent will prevent its loading but will allow the application itself to run (the source process will not be terminated).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The "procexp.sys" driver is commonly associated with tools like "Process Explorer" (procexp.exe). The driver is loaded when these applications are executed with administrative privileges, triggering an alert..&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 May 2025 11:04:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/process-explorer-triggering-cortex-xdr-alert-clarification/m-p/1227964#M8284</guid>
      <dc:creator>tlmarques</dc:creator>
      <dc:date>2025-05-02T11:04:25Z</dc:date>
    </item>
  </channel>
</rss>

