<?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 Potential False Positive IoC in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/potential-false-positive-ioc/m-p/1250607#M7320</link>
    <description>&lt;P&gt;Hello everyone! I'm Arsen, Junior SOC Analyst and I've got some questions regarding the detection&amp;nbsp;Evasive HTTP C2 Traffic Detection(89950). Recently, I have received several alerts, where the Destination IP was&amp;nbsp;91.108.56.132, which is related to&amp;nbsp;AS 62014 (T. Messenger Inc). The user claimed that he used a T. Desktop Application and it seems to be a normal practice in our company, so I don't understand why Palo Alto triggers on this IP.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Mar 2026 06:56:07 GMT</pubDate>
    <dc:creator>A.Tsadzikidze</dc:creator>
    <dc:date>2026-03-20T06:56:07Z</dc:date>
    <item>
      <title>Potential False Positive IoC</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/potential-false-positive-ioc/m-p/1250607#M7320</link>
      <description>&lt;P&gt;Hello everyone! I'm Arsen, Junior SOC Analyst and I've got some questions regarding the detection&amp;nbsp;Evasive HTTP C2 Traffic Detection(89950). Recently, I have received several alerts, where the Destination IP was&amp;nbsp;91.108.56.132, which is related to&amp;nbsp;AS 62014 (T. Messenger Inc). The user claimed that he used a T. Desktop Application and it seems to be a normal practice in our company, so I don't understand why Palo Alto triggers on this IP.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 06:56:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/potential-false-positive-ioc/m-p/1250607#M7320</guid>
      <dc:creator>A.Tsadzikidze</dc:creator>
      <dc:date>2026-03-20T06:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Potential False Positive IoC</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/potential-false-positive-ioc/m-p/1250947#M7328</link>
      <description>&lt;P&gt;Hi &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/553823085"&gt;@A.Tsadzikidze&lt;/a&gt;&lt;/SPAN&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Threat ID 89950 is an Anti-Spyware detection and appears to be based on behavioral analysis rather than just the destination IP itself. In other words, Palo Alto may be flagging the HTTP traffic pattern as C2-like, even if the destination belongs to Telegram.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since you confirmed the user’s activity aligns with expected Telegram Desktop usage, it might be worh it to open a TAC case and including the threat logs and a packet capture so it can be reviewed properly.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 01:24:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/potential-false-positive-ioc/m-p/1250947#M7328</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2026-03-26T01:24:41Z</dc:date>
    </item>
  </channel>
</rss>

