<?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: Unknown Source and Unknown Destination IP address showing in monitor logs in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/586846#M3205</link>
    <description>&lt;P&gt;It is really expected, since traffic coming from Internet to the public facing IP of the Firewall is traffic from untrust to untrust. It's advised to enable session logging on intrazone-zone and interzone policies only for troubleshooting reasons, since it might be filling your logs with information not really usefull.&lt;/P&gt;
&lt;P&gt;In summary, it's the firewall doing its job &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2024 21:39:05 GMT</pubDate>
    <dc:creator>jfernandez1</dc:creator>
    <dc:date>2024-05-15T21:39:05Z</dc:date>
    <item>
      <title>Unknown Source and Unknown Destination IP address showing in monitor logs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/586756#M3191</link>
      <description>&lt;P&gt;Hello Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good day to you !!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;++We have one customer he facing issue with&amp;nbsp;Unknown Source and Unknown Destination IP address showing in monitor logs.&lt;/P&gt;
&lt;DIV&gt;++That Unknown Source IP address traffic is showing in monitor traffic logs with unknown destination IP address which does not belongs to your organization&lt;/DIV&gt;
&lt;DIV&gt;++as we can see that there are multiple unknown source IP address traffic with unknown destination IP address traffic in monitor logs with different different country name&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;++most of the traffic are hitting to intrazone-default-rule.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Kindly help me to address the issue.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Regards&lt;/DIV&gt;
&lt;DIV&gt;Sasikumari.&lt;/DIV&gt;</description>
      <pubDate>Wed, 15 May 2024 09:30:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/586756#M3191</guid>
      <dc:creator>Sasikumari</dc:creator>
      <dc:date>2024-05-15T09:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Source and Unknown Destination IP address showing in monitor logs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/586846#M3205</link>
      <description>&lt;P&gt;It is really expected, since traffic coming from Internet to the public facing IP of the Firewall is traffic from untrust to untrust. It's advised to enable session logging on intrazone-zone and interzone policies only for troubleshooting reasons, since it might be filling your logs with information not really usefull.&lt;/P&gt;
&lt;P&gt;In summary, it's the firewall doing its job &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 21:39:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/586846#M3205</guid>
      <dc:creator>jfernandez1</dc:creator>
      <dc:date>2024-05-15T21:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Source and Unknown Destination IP address showing in monitor logs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/587186#M3210</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/285012"&gt;@jfernandez1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it really expected behavior as the Public facing ISP IP is different from what it is showing in traffic logs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Please find the attached screenshot for reference&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We don't know the source and Destination IP's .&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PA.jpg" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/59858iC0C30354B1D6E38E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="PA.jpg" alt="PA.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks and Regards&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Satya Kalyan&lt;/P&gt;</description>
      <pubDate>Sat, 18 May 2024 10:48:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/587186#M3210</guid>
      <dc:creator>Satyak</dc:creator>
      <dc:date>2024-05-18T10:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown Source and Unknown Destination IP address showing in monitor logs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/587282#M3216</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/223445"&gt;@Satyak&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes, internet connections are continuously scanned from external actors, this since attackers may be taking multiple IP prefixes to scan and check if there's a service opened they can exploit, here's the importance of using firewalls &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 13:18:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/unknown-source-and-unknown-destination-ip-address-showing-in/m-p/587282#M3216</guid>
      <dc:creator>jfernandez1</dc:creator>
      <dc:date>2024-05-20T13:18:03Z</dc:date>
    </item>
  </channel>
</rss>

