<?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 How to detect beaconing in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307035#M27</link>
    <description>&lt;P&gt;Is there any way to use XDR or the NGFW logs to detect beaconing?&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jan 2020 11:22:26 GMT</pubDate>
    <dc:creator>christowner</dc:creator>
    <dc:date>2020-01-17T11:22:26Z</dc:date>
    <item>
      <title>How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307035#M27</link>
      <description>&lt;P&gt;Is there any way to use XDR or the NGFW logs to detect beaconing?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 11:22:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307035#M27</guid>
      <dc:creator>christowner</dc:creator>
      <dc:date>2020-01-17T11:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307185#M28</link>
      <description>&lt;P&gt;There are many ways we can detect C2 (beaconing) activities using the Cortex XDR, we can do it by looking on the endpoint and or the network data, take a look here for a few examples of the detections we have in the product&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference.html" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-analytics-alert-reference/cortex-xdr-analytics-alert-reference.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition for that we have many more ways to detect using C2 as an example protecting the endpoint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Menachem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Jan 2020 20:26:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307185#M28</guid>
      <dc:creator>mperlman</dc:creator>
      <dc:date>2020-01-19T20:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307236#M29</link>
      <description>&lt;P&gt;Thanks,&amp;nbsp;&lt;SPAN&gt;Menachem.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I can see there are several built in detections. What I was looking for was a way to use the Investigation &amp;gt; Query Builder (or NGFW logs) to detect beaconing where the built in detectors haven't identified the events. The kind of traffic I was hoping to detect was regular connections to the same IP address/domain where that domain wasn't necessarily malicious (or randomly generated).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jan 2020 08:42:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307236#M29</guid>
      <dc:creator>christowner</dc:creator>
      <dc:date>2020-01-20T08:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307282#M30</link>
      <description>&lt;P&gt;Hi Christowner,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can leverage the existing pre-built in query builder to query and do threat hunting for different C2 activities like attackers leveraging regular connections to hide their channels or attackers using benign domains or files, Cortex XDR have multiple methods to detect attackers from pre-built in ML algorithms to rules or signatures and you can also create your own different queries for detection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have a specific type of attack you would like to know feel free to send me PM or post it here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Menachem.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jan 2020 14:01:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307282#M30</guid>
      <dc:creator>mperlman</dc:creator>
      <dc:date>2020-01-20T14:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307288#M31</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Menachem,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks again. The exact attack is where C&amp;amp;C beaconing occurs using HTTPS to a domain at 10 second intervals. I have the domain details now, so I can query the NGFW and XDR logs for the data. What I am trying to do is work out how I would be able to find this traffic if I didn't already know the domain. The XDR logs do not show network beaconing at 10 second intervals as the same source process made repeated HTTPS requests (so it only shows the requests at 5-20 minute intervals as associated&amp;nbsp;with a process). The NGFW does show the exact traffic, but I don't see a way to create a query that shows any domain access that repeats at regular intervals (or to query the NGFW at all in XDR, outside of Explore).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks for your continued help,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Chris.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jan 2020 16:08:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307288#M31</guid>
      <dc:creator>christowner</dc:creator>
      <dc:date>2020-01-20T16:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to detect beaconing</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307299#M32</link>
      <description>&lt;P&gt;Thank you for elaborating more,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Behind the scenes we look on connection to domains&amp;nbsp; in order to detect abnormal activities,&amp;nbsp; in the Cortex XDR UI we display the information rounded to minutes or hours depends on the type of the detection.&lt;/P&gt;&lt;P&gt;You are correct that using the Explore app you can see the actual data once you have the URL you are looking for.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I opened feature request to allow user to query for URLs on specific intervals.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Menachem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jan 2020 16:07:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/how-to-detect-beaconing/m-p/307299#M32</guid>
      <dc:creator>mperlman</dc:creator>
      <dc:date>2020-01-20T16:07:58Z</dc:date>
    </item>
  </channel>
</rss>

