<?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 DNS Sinkhole and Honeypot to Record URLs accessed in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-and-honeypot-to-record-urls-accessed/m-p/158982#M52052</link>
    <description>&lt;P&gt;We've set up DNS sinkhole and it works as expected. We're able to find out which IP addresses tried to access malious sites. However, we won't be able to see the URLs these IPs were trying to access. We're thinking of building a honeypot (or maybe something else) to accept access requests from these IPs and set the sinkhole IP addrss to this machine. That way we will be able to record the URLs these IPs try to access. Does anyone know what software we can use to acheive this goal? All we need is to finish three-way handshake and record the URL requested.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 19:13:06 GMT</pubDate>
    <dc:creator>Yang_Chen</dc:creator>
    <dc:date>2017-06-01T19:13:06Z</dc:date>
    <item>
      <title>DNS Sinkhole and Honeypot to Record URLs accessed</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-and-honeypot-to-record-urls-accessed/m-p/158982#M52052</link>
      <description>&lt;P&gt;We've set up DNS sinkhole and it works as expected. We're able to find out which IP addresses tried to access malious sites. However, we won't be able to see the URLs these IPs were trying to access. We're thinking of building a honeypot (or maybe something else) to accept access requests from these IPs and set the sinkhole IP addrss to this machine. That way we will be able to record the URLs these IPs try to access. Does anyone know what software we can use to acheive this goal? All we need is to finish three-way handshake and record the URL requested.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 19:13:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-and-honeypot-to-record-urls-accessed/m-p/158982#M52052</guid>
      <dc:creator>Yang_Chen</dc:creator>
      <dc:date>2017-06-01T19:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Sinkhole and Honeypot to Record URLs accessed</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-and-honeypot-to-record-urls-accessed/m-p/158996#M52054</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/19948"&gt;@Yang_Chen&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;So you don't really need a 'honeypot' in the sense that you are thinking. Any type of Applicaiton Delivery Controller would do this for you, as it would generate an error in it's logs that you wouldn't have a rule allocated to tell it where to send that traffic. I would setup one of these types of devices and set that as your sinkhole. The logs would show the requested URL and indicate that it didn't know where to send it, but it would give you something to actually look at.&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as an actual 'honeypot' for this type of thing I'm sure they are out there, but I can't seem to find any with a quick Google search easily.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 19:21:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-sinkhole-and-honeypot-to-record-urls-accessed/m-p/158996#M52054</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-06-01T19:21:47Z</dc:date>
    </item>
  </channel>
</rss>

