<?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: negate destination IP's in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234406#M67194</link>
    <description>&lt;P&gt;Nope, it means all IPs except those will match that field in rule.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Oct 2018 13:03:00 GMT</pubDate>
    <dc:creator>santonic</dc:creator>
    <dc:date>2018-10-08T13:03:00Z</dc:date>
    <item>
      <title>negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234396#M67191</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Is you create an allow rule and then select to negate the destination IP's does that mean those IP's are blocked?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2018 12:27:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234396#M67191</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-10-08T12:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234406#M67194</link>
      <description>&lt;P&gt;Nope, it means all IPs except those will match that field in rule.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2018 13:03:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234406#M67194</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2018-10-08T13:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234407#M67195</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/10238"&gt;@santonic&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Thats what I thought, they can be picked up by another rule and still be allowed&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2018 13:05:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234407#M67195</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-10-08T13:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234921#M67343</link>
      <description>&lt;P&gt;correct, it simply means "match everything except these"&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 13:51:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234921#M67343</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2018-10-11T13:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234929#M67348</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/10238"&gt;@santonic&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just for curiousity what would be a good use case of using negate instead of just not adding those IP ranges to the rule&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 14:39:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234929#M67348</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-10-11T14:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234946#M67353</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/18719"&gt;@jdprovine&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;When there are specific IPs within a given range that you would want to exclude. For example; If I created a policy that says that everything within my 'GUEST' zone is denied from accessing anything within my 'SERVER' zone I would likely want to negate my switches so they could actually access NTP servers and DHCP services.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 15:41:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234946#M67353</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-10-11T15:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: negate destination IP's</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234954#M67360</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Then those IP's that you negate from that rule can still match on another rule and be allowed. I can see where it might save you time if you have alot of IP's to block and only a few that you don't want blocked on that rule&lt;/P&gt;</description>
      <pubDate>Thu, 11 Oct 2018 16:08:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/negate-destination-ip-s/m-p/234954#M67360</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-10-11T16:08:55Z</dc:date>
    </item>
  </channel>
</rss>

