<?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: URL filtering or tightening up on GlobalProtect security rule? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/url-filtering-or-tightening-up-on-globalprotect-security-rule/m-p/1228292#M5870</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/108539"&gt;@inSync-MarkValpreda&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I would utilize app-id for this and do away with your any application and service rule that you have currently. Also note that if you're security profile is only accounting for 40017 you're missing 16 other signatures related to GlobalProtect. I don't much see a point in maintaining a profile specific to GlobalProtect and trying to manually specify IDs that should be active. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you limit the sources that you're allowing to hit your portal/gateway? You can cut back exposure and scanning/probing by limiting to the regions that you actually need active; while this doesn't prevent a targeted attack by any means it at least cuts back on noise. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/108539"&gt;@inSync-MarkValpreda&lt;/a&gt;&amp;nbsp;wrote:
&lt;P&gt;I do have my home IP address whitelisted on the interface management as a 'just in case' sort of thing....so I don't want to inadvertently kill that. Maybe put my emergency IP addresses into a different security group?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Why? Do you have a static IP at your house or are you just relying on it staying the same?&lt;/P&gt;
&lt;P&gt;Personally this is never something that I would facilitate or allow any of my staff to implement. The risk analysis for this would never have the benefit of this outweigh the risk that is introduced. Things either wait until someone can be onsite and restore things properly, or you implement a proper out-of-band connection. &lt;/P&gt;</description>
    <pubDate>Tue, 06 May 2025 21:13:25 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-05-06T21:13:25Z</dc:date>
    <item>
      <title>URL filtering or tightening up on GlobalProtect security rule?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/url-filtering-or-tightening-up-on-globalprotect-security-rule/m-p/1227990#M5861</link>
      <description>&lt;P&gt;I have a security rule for my GlobalProtect, and want to see if I can make it even tighter....&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Source
&lt;UL&gt;
&lt;LI&gt;Zone: untrust (outside)&lt;/LI&gt;
&lt;LI&gt;Address\User\Device: Any&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Destination
&lt;UL&gt;
&lt;LI&gt;Zone: untrust&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Address: IP of my interface/GlobalProtect IP&lt;/LI&gt;
&lt;LI&gt;Device: Any&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Application
&lt;UL&gt;
&lt;LI&gt;Any&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Service/URL
&lt;UL&gt;
&lt;LI&gt;GP-4501 (4501/udp)&lt;/LI&gt;
&lt;LI&gt;service-https&lt;/LI&gt;
&lt;LI&gt;Category: Any&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Actions
&lt;UL&gt;
&lt;LI&gt;Just a vulnerability group that blocks brute force (40017)&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Thinking there is an opportunity to lock that down even more. Maybe with URL filtering? Maybe with applications? I am only seeing ipsec-esp-udp, ssl, and panos-global-protect as the biggest applications.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I do have my home IP address whitelisted on the interface management as a 'just in case' sort of thing....so I don't want to inadvertently kill that. Maybe put my emergency IP addresses into a different security group?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for any suggestions or criticisms!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 May 2025 15:14:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/url-filtering-or-tightening-up-on-globalprotect-security-rule/m-p/1227990#M5861</guid>
      <dc:creator>inSync-MarkValpreda</dc:creator>
      <dc:date>2025-05-03T15:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: URL filtering or tightening up on GlobalProtect security rule?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/url-filtering-or-tightening-up-on-globalprotect-security-rule/m-p/1228292#M5870</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/108539"&gt;@inSync-MarkValpreda&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I would utilize app-id for this and do away with your any application and service rule that you have currently. Also note that if you're security profile is only accounting for 40017 you're missing 16 other signatures related to GlobalProtect. I don't much see a point in maintaining a profile specific to GlobalProtect and trying to manually specify IDs that should be active. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you limit the sources that you're allowing to hit your portal/gateway? You can cut back exposure and scanning/probing by limiting to the regions that you actually need active; while this doesn't prevent a targeted attack by any means it at least cuts back on noise. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/108539"&gt;@inSync-MarkValpreda&lt;/a&gt;&amp;nbsp;wrote:
&lt;P&gt;I do have my home IP address whitelisted on the interface management as a 'just in case' sort of thing....so I don't want to inadvertently kill that. Maybe put my emergency IP addresses into a different security group?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Why? Do you have a static IP at your house or are you just relying on it staying the same?&lt;/P&gt;
&lt;P&gt;Personally this is never something that I would facilitate or allow any of my staff to implement. The risk analysis for this would never have the benefit of this outweigh the risk that is introduced. Things either wait until someone can be onsite and restore things properly, or you implement a proper out-of-band connection. &lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 21:13:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/url-filtering-or-tightening-up-on-globalprotect-security-rule/m-p/1228292#M5870</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-05-06T21:13:25Z</dc:date>
    </item>
  </channel>
</rss>

