<?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: incorrect destination zone in threat logs in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/incorrect-destination-zone-in-threat-logs/m-p/331437#M843</link>
    <description>&lt;P&gt;It is possible that the firewall is taking a discard action early, before policy-lookup, where the destination data in the packet is evaluated. Open a Support case to get additional insight.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2020 16:28:02 GMT</pubDate>
    <dc:creator>mivaldi</dc:creator>
    <dc:date>2020-06-03T16:28:02Z</dc:date>
    <item>
      <title>incorrect destination zone in threat logs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/incorrect-destination-zone-in-threat-logs/m-p/331353#M841</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if the firewall is configured with zone protection profiles and the setting "set system setting additional-threat-log on" is configured, i have noticed the destination zone is not correctly (in my example 8.8.8.8 is reachable over the outside zone) displayed in the threat logs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JuergenHolzer_0-1591185185711.png" style="width: 813px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/25990iEE2294639C26F3EF/image-dimensions/813x65/is-moderation-mode/true?v=v2" width="813" height="65" role="button" title="JuergenHolzer_0-1591185185711.png" alt="JuergenHolzer_0-1591185185711.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I noticed it with version 8.1.8, 9.0.8, 9.1.2.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anybody has an explanation for it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 11:57:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/incorrect-destination-zone-in-threat-logs/m-p/331353#M841</guid>
      <dc:creator>JuergenHolzer</dc:creator>
      <dc:date>2020-06-03T11:57:31Z</dc:date>
    </item>
    <item>
      <title>Re: incorrect destination zone in threat logs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/incorrect-destination-zone-in-threat-logs/m-p/331437#M843</link>
      <description>&lt;P&gt;It is possible that the firewall is taking a discard action early, before policy-lookup, where the destination data in the packet is evaluated. Open a Support case to get additional insight.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2020 16:28:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/incorrect-destination-zone-in-threat-logs/m-p/331437#M843</guid>
      <dc:creator>mivaldi</dc:creator>
      <dc:date>2020-06-03T16:28:02Z</dc:date>
    </item>
  </channel>
</rss>

