<?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: Threat logs from DNS Proxy zone not showing source IP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591577#M117804</link>
    <description>&lt;P&gt;having sinkhole enabled will reveal the source IP as that will connect to the sinkhole IP address&lt;/P&gt;
&lt;P&gt;to detect the malicious DNS looklup from the original client, you'd need to create a security rule from the source subnet to the proxy IP with security profiles enabled, so the original request is intercepted&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jul 2024 10:14:45 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2024-07-10T10:14:45Z</dc:date>
    <item>
      <title>Threat logs from DNS Proxy zone not showing source IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591447#M117779</link>
      <description>&lt;P&gt;We use DNS Proxy on 3 of our zones with the firewall IP as the address that the traffic is proxied to. In other words, the firewall proxies the network traffic with it's own IP address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, in the threat logs, we have some threats that do not show the original source IP and instead show the firewall's IP as the source address, due to the proxy.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How can I get the true source IP?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards and thanks in advance,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;AverageTechnician&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 12:36:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591447#M117779</guid>
      <dc:creator>averageTechnician</dc:creator>
      <dc:date>2024-07-09T12:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: Threat logs from DNS Proxy zone not showing source IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591577#M117804</link>
      <description>&lt;P&gt;having sinkhole enabled will reveal the source IP as that will connect to the sinkhole IP address&lt;/P&gt;
&lt;P&gt;to detect the malicious DNS looklup from the original client, you'd need to create a security rule from the source subnet to the proxy IP with security profiles enabled, so the original request is intercepted&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2024 10:14:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591577#M117804</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2024-07-10T10:14:45Z</dc:date>
    </item>
    <item>
      <title>Re: Threat logs from DNS Proxy zone not showing source IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591597#M117809</link>
      <description>&lt;P&gt;I will go configure this and report back. Thank you very much, I thought nobody would respond.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also read the second edition of your textbook and it was great when I got this job&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jul 2024 14:31:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/threat-logs-from-dns-proxy-zone-not-showing-source-ip/m-p/591597#M117809</guid>
      <dc:creator>averageTechnician</dc:creator>
      <dc:date>2024-07-10T14:31:21Z</dc:date>
    </item>
  </channel>
</rss>

