<?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: Block traffic to ip addresses in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/49#M42</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then it should work if you only specify which categories you wish to allow - sites/ipaddresses not part of this whitelist will then be blocked and you get the effect you seem to be asking for.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Mar 2013 21:33:13 GMT</pubDate>
    <dc:creator>mikand</dc:creator>
    <dc:date>2013-03-29T21:33:13Z</dc:date>
    <item>
      <title>Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/42#M35</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How do you block traffic going directly to ip addresses?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 20:11:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/42#M35</guid>
      <dc:creator>akumar</dc:creator>
      <dc:date>2013-03-27T20:11:13Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/43#M36</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do you mean by directly ip addresses&lt;/P&gt;&lt;P&gt;browsing domains by ip ?&lt;/P&gt;&lt;P&gt;or there is an ip list ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 20:18:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/43#M36</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2013-03-27T20:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/44#M37</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So these Ips don't resolve to host name? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 20:24:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/44#M37</guid>
      <dc:creator>wesa</dc:creator>
      <dc:date>2013-03-27T20:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/45#M38</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A lot of poorly intended code (read malware) are designed to go directly to IP addresses that may or may not resolve to nicely constructed dns names. In my experience, these more most likely to be malicious CNC hosts etc. The best practice here is to deny http/ssl to ip addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blue Coat provides a way to create a filter of the kind http(s)://\d+\.\d+\.\d+\.\d+, but this does not appear to be possible in PA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies for not clarifying this initially. I thought this would be a common question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ash&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 20:46:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/45#M38</guid>
      <dc:creator>akumar</dc:creator>
      <dc:date>2013-03-27T20:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/46#M39</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you can do this yourself with a custom url filter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise the "proper" solution is to create a custom blacklist rule in front of the other rules (maybe put a whitelist rule in front of the blacklist one :smileysilly:) where you block bad dstip's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PANDB should be able to be more granular than the Brightcloud db, but I dunno if the PANDB includes ip addresses as "hostnames" or not - parhaps someone from PA (who is lurking this forum) could answer that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Mar 2013 21:29:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/46#M39</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-03-28T21:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/47#M40</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I heard my name&amp;nbsp; &lt;img id="smileywink" class="emoticon emoticon-smileywink" src="https://live.paloaltonetworks.com/i/smilies/16x16_smiley-wink.png" alt="Smiley Wink" title="Smiley Wink" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PAN-DB does include IP address categorization, though the majority of entries are made up of URLs.&amp;nbsp; While a lot of malware does go directly to IP addresses, we've also noticed that many streaming media applications behave similarly (eg BBC iPlayer).&amp;nbsp; If you would like to safely enable these applications, use App-ID to do so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--Doris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Mar 2013 22:24:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/47#M40</guid>
      <dc:creator>dyang</dc:creator>
      <dc:date>2013-03-28T22:24:32Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/48#M41</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have not considered moving to PAN-DB from the Brightcloud system. Too many unanswered questions such as quality of categorization, performance etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We already permit specific applications upfront.&lt;/P&gt;&lt;P&gt;What we would like to do is block all other traffic to IP addresses and deal with specific exceptions as a safer approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ash&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 15:51:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/48#M41</guid>
      <dc:creator>akumar</dc:creator>
      <dc:date>2013-03-29T15:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic to ip addresses</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/49#M42</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Then it should work if you only specify which categories you wish to allow - sites/ipaddresses not part of this whitelist will then be blocked and you get the effect you seem to be asking for.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 21:33:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-traffic-to-ip-addresses/m-p/49#M42</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-03-29T21:33:13Z</dc:date>
    </item>
  </channel>
</rss>

