<?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: XDR Analytics &amp;quot;Failed Connections&amp;quot; alert investigation in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-analytics-quot-failed-connections-quot-alert-investigation/m-p/450550#M1309</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/196640"&gt;@Daniel_Itenberg&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a couple of steps that I would suggest, my assumption being that the endpoint tried to connect to a malicious site.&lt;/P&gt;&lt;P&gt;1. Drill down into the alerts that are a part of the incident. Identify the sources and destinations, and the actions that led to the alert. If a malicious file is initiating the connections, you can block it, and retrieve it for further analysis in a sandboxed environment. Based on you analysis, you can proceed to remove the file/s based on your organizational processes. You can also proceed to investigate how the file came to be present in the host.&lt;/P&gt;&lt;P&gt;2. If the connection destinations are deemed malicious/suspicious, you can block them via EDLs or better still, update your firewall policies to block such connections in the event the destinations are alive in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the connections are port scans, lateral movements (wmiexec etc.), please investigate the reason for those activities as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this gets you started off in the right direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ref:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference/failed-connections.html" target="_blank"&gt;https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference/failed-connections.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Dec 2021 02:16:50 GMT</pubDate>
    <dc:creator>bbarmanroy</dc:creator>
    <dc:date>2021-12-01T02:16:50Z</dc:date>
    <item>
      <title>XDR Analytics "Failed Connections" alert investigation</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-analytics-quot-failed-connections-quot-alert-investigation/m-p/450385#M1306</link>
      <description>&lt;P&gt;Hi all, I am i need of assistance - how should I go about investigating an incident created by the "Failed Connections" alert?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I run malware scans on the host that raised the alarm, but what can I do beyond that?&lt;/P&gt;&lt;P&gt;I should also mention that whenever such an incident arises, it is not accompanied by a malware alert or anything of the sort.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Nov 2021 12:56:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-analytics-quot-failed-connections-quot-alert-investigation/m-p/450385#M1306</guid>
      <dc:creator>Daniel_Itenberg</dc:creator>
      <dc:date>2021-11-30T12:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: XDR Analytics "Failed Connections" alert investigation</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-analytics-quot-failed-connections-quot-alert-investigation/m-p/450550#M1309</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/196640"&gt;@Daniel_Itenberg&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a couple of steps that I would suggest, my assumption being that the endpoint tried to connect to a malicious site.&lt;/P&gt;&lt;P&gt;1. Drill down into the alerts that are a part of the incident. Identify the sources and destinations, and the actions that led to the alert. If a malicious file is initiating the connections, you can block it, and retrieve it for further analysis in a sandboxed environment. Based on you analysis, you can proceed to remove the file/s based on your organizational processes. You can also proceed to investigate how the file came to be present in the host.&lt;/P&gt;&lt;P&gt;2. If the connection destinations are deemed malicious/suspicious, you can block them via EDLs or better still, update your firewall policies to block such connections in the event the destinations are alive in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the connections are port scans, lateral movements (wmiexec etc.), please investigate the reason for those activities as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this gets you started off in the right direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ref:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference/failed-connections.html" target="_blank"&gt;https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference/failed-connections.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Dec 2021 02:16:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/xdr-analytics-quot-failed-connections-quot-alert-investigation/m-p/450550#M1309</guid>
      <dc:creator>bbarmanroy</dc:creator>
      <dc:date>2021-12-01T02:16:50Z</dc:date>
    </item>
  </channel>
</rss>

