<?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: DNS Sinkhole Intended Destination in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/103940#M44661</link>
    <description>&lt;P&gt;If you reslove the URLs in those DNS queries you will get IPs of C&amp;amp;C servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The original source of the infection will not be so easy to find.&lt;/P&gt;&lt;P&gt;For start check threat logs with IPs of the infected machines as source or destination. You might also want to check URL logs if it&amp;nbsp;visited some of the suspicious categories (malware, unknown..) if these aren't blocked. If you pinpoint the moment of infection from system logs on the infected device maybe check traffic logs as well. That's as much as you can check on FW. But if the source infection was encrypted connection&amp;nbsp;or USB stick you won't find much info on firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Aug 2016 13:58:02 GMT</pubDate>
    <dc:creator>santonic</dc:creator>
    <dc:date>2016-08-17T13:58:02Z</dc:date>
    <item>
      <title>DNS Sinkhole Intended Destination</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/103900#M44657</link>
      <description>&lt;P&gt;I've configured a DNS sinkhole in our PAN firewall, and it's helped our department identify machines that are trying to reach out to malicious domains and such. Is it possible to identify the original, intended, destination that the user was attempting to reach when they became innfected?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 13:10:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/103900#M44657</guid>
      <dc:creator>cleediker</dc:creator>
      <dc:date>2016-08-17T13:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Sinkhole Intended Destination</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/103940#M44661</link>
      <description>&lt;P&gt;If you reslove the URLs in those DNS queries you will get IPs of C&amp;amp;C servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The original source of the infection will not be so easy to find.&lt;/P&gt;&lt;P&gt;For start check threat logs with IPs of the infected machines as source or destination. You might also want to check URL logs if it&amp;nbsp;visited some of the suspicious categories (malware, unknown..) if these aren't blocked. If you pinpoint the moment of infection from system logs on the infected device maybe check traffic logs as well. That's as much as you can check on FW. But if the source infection was encrypted connection&amp;nbsp;or USB stick you won't find much info on firewall.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2016 13:58:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/103940#M44661</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2016-08-17T13:58:02Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Sinkhole Intended Destination</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/106680#M44829</link>
      <description>&lt;P&gt;Thanks for the reply, Santonic.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 12:55:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-intended-destination/m-p/106680#M44829</guid>
      <dc:creator>cleediker</dc:creator>
      <dc:date>2016-08-24T12:55:57Z</dc:date>
    </item>
  </channel>
</rss>

