<?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 HTTP/HTTPS access via IP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-http-https-access-via-ip/m-p/520783#M107946</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/256619"&gt;@Robynson&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Couple ways off hand:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* Custom URL Category assigned to the security policy allowing external access - This is by far the most effective way to accomplish what you're attempting to do since you're just trying to do it for your own website(s).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* Blocking the unknown category - Same thing really, but you would assign a URL filtering profile on the external access entry that blocks medium-risk and unknown categories. You'd have to verify what effect this would have with your own URL logs, but direct IP access is always going to be labelled as medium-risk,unknown by the firewall. Blocking access to those would block direct IP access, but could cause issues depending on how your website(s) are actually categorized.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The one thing to be mindful of here is that you'd want to ensure that you actually look through your logs and create a&amp;nbsp;&lt;EM&gt;separate&lt;/EM&gt;&amp;nbsp;URL Filtering profile to assign if you go with that second option. GlobalProtect's hip-check is sent directly to the IP address instead of the FQDN, so you don't want to just block medium-risk and unknown categories on the profile you use for all of your external access rules.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Nov 2022 13:38:02 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2022-11-09T13:38:02Z</dc:date>
    <item>
      <title>Block HTTP/HTTPS access via IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-http-https-access-via-ip/m-p/520772#M107942</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would like to block access to my site (http/https) when it is made via IP.&lt;/P&gt;
&lt;P&gt;I want to only allow access made by name.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ex.: &lt;A href="http://www.mysite.com" target="_blank" rel="noopener"&gt;www.mysite.com&lt;/A&gt;&amp;nbsp;&amp;lt;=&amp;gt; 1.2.3.4&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://1.2.3.4" target="_blank" rel="noopener"&gt;https://1.2.3.4&lt;/A&gt;&amp;nbsp;=&amp;gt; deny&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.mysite.com" target="_blank" rel="noopener"&gt;https://www.mysite.com&lt;/A&gt;&amp;nbsp;=&amp;gt; allow&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="PA-access.by.name.jpg" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/45228i29F71D6555D8AF98/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="PA-access.by.name.jpg" alt="PA-access.by.name.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is that possible with Palo Alto?&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 12:24:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-http-https-access-via-ip/m-p/520772#M107942</guid>
      <dc:creator>Robynson</dc:creator>
      <dc:date>2022-11-09T12:24:01Z</dc:date>
    </item>
    <item>
      <title>Re: Block HTTP/HTTPS access via IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-http-https-access-via-ip/m-p/520783#M107946</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/256619"&gt;@Robynson&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Couple ways off hand:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* Custom URL Category assigned to the security policy allowing external access - This is by far the most effective way to accomplish what you're attempting to do since you're just trying to do it for your own website(s).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;* Blocking the unknown category - Same thing really, but you would assign a URL filtering profile on the external access entry that blocks medium-risk and unknown categories. You'd have to verify what effect this would have with your own URL logs, but direct IP access is always going to be labelled as medium-risk,unknown by the firewall. Blocking access to those would block direct IP access, but could cause issues depending on how your website(s) are actually categorized.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The one thing to be mindful of here is that you'd want to ensure that you actually look through your logs and create a&amp;nbsp;&lt;EM&gt;separate&lt;/EM&gt;&amp;nbsp;URL Filtering profile to assign if you go with that second option. GlobalProtect's hip-check is sent directly to the IP address instead of the FQDN, so you don't want to just block medium-risk and unknown categories on the profile you use for all of your external access rules.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2022 13:38:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-http-https-access-via-ip/m-p/520783#M107946</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2022-11-09T13:38:02Z</dc:date>
    </item>
  </channel>
</rss>

