<?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 Threat Intelligence External Dynamic Lists vs URL Filtering Security Profile in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/threat-intelligence-external-dynamic-lists-vs-url-filtering/m-p/542331#M1275</link>
    <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Hi All,&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I have security profiles on my main egress firewall rules, and the URL filtering is blocking anything malware, high-risk etc. I have some custom reports setup that report on any blocks that take place as a result of this profile.&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I am reading you can also setup firewall rules to block inbound/outbound traffic using sources and destinations that are External Dynamic Lists of known malicious IP addresses, high-risk IP addresses, bulletproof IP addresses etc. (&lt;A class="_3t5uN8xUmg0TOwRCOGQEcU" href="https://docs.paloaltonetworks.com/best-practices/10-2/internet-gateway-best-practices/best-practice-internet-gateway-security-policy/define-the-initial-internet-gateway-security-policy/step-1-create-rules-based-on-trusted-threat-intelligence-sources" target="_blank" rel="noopener nofollow ugc"&gt;https://docs.paloaltonetworks.com/best-practices/10-2/internet-gateway-best-practices/best-practice-internet-gateway-security-policy/define-the-initial-internet-gateway-security-policy/step-1-create-rules-based-on-trusted-threat-intelligence-sources&lt;/A&gt;)&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Why would I use these rules with EDL's vs URL filtering security profile? Or should both be used for best protection? Am I correct in thinking that the EDL's are a protection at a layer 3 level, and the URL filtering is more of a layer 7 protection?&lt;/P&gt;</description>
    <pubDate>Tue, 16 May 2023 16:45:42 GMT</pubDate>
    <dc:creator>Nick_Davis1639</dc:creator>
    <dc:date>2023-05-16T16:45:42Z</dc:date>
    <item>
      <title>Threat Intelligence External Dynamic Lists vs URL Filtering Security Profile</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/threat-intelligence-external-dynamic-lists-vs-url-filtering/m-p/542331#M1275</link>
      <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Hi All,&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I have security profiles on my main egress firewall rules, and the URL filtering is blocking anything malware, high-risk etc. I have some custom reports setup that report on any blocks that take place as a result of this profile.&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;I am reading you can also setup firewall rules to block inbound/outbound traffic using sources and destinations that are External Dynamic Lists of known malicious IP addresses, high-risk IP addresses, bulletproof IP addresses etc. (&lt;A class="_3t5uN8xUmg0TOwRCOGQEcU" href="https://docs.paloaltonetworks.com/best-practices/10-2/internet-gateway-best-practices/best-practice-internet-gateway-security-policy/define-the-initial-internet-gateway-security-policy/step-1-create-rules-based-on-trusted-threat-intelligence-sources" target="_blank" rel="noopener nofollow ugc"&gt;https://docs.paloaltonetworks.com/best-practices/10-2/internet-gateway-best-practices/best-practice-internet-gateway-security-policy/define-the-initial-internet-gateway-security-policy/step-1-create-rules-based-on-trusted-threat-intelligence-sources&lt;/A&gt;)&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Why would I use these rules with EDL's vs URL filtering security profile? Or should both be used for best protection? Am I correct in thinking that the EDL's are a protection at a layer 3 level, and the URL filtering is more of a layer 7 protection?&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2023 16:45:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/threat-intelligence-external-dynamic-lists-vs-url-filtering/m-p/542331#M1275</guid>
      <dc:creator>Nick_Davis1639</dc:creator>
      <dc:date>2023-05-16T16:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Intelligence External Dynamic Lists vs URL Filtering Security Profile</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/threat-intelligence-external-dynamic-lists-vs-url-filtering/m-p/542552#M1277</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/272320"&gt;@Nick_Davis1639&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is 100% correct.&amp;nbsp; The built-in EDLs are lists of IP addresses (layer 3).&amp;nbsp; You can view the entries (and create exceptions) under Objects &amp;gt; External Dynamic Lists &amp;gt; click on EDL &amp;gt; List Entries and Exceptions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The URL categories are URLs.&amp;nbsp; They work at layer 7, and only work with web-browsing and ssl.&amp;nbsp; The EDLs will block all applications.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The BPA recommends implementing both.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2023 23:14:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/threat-intelligence-external-dynamic-lists-vs-url-filtering/m-p/542552#M1277</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2023-05-17T23:14:18Z</dc:date>
    </item>
  </channel>
</rss>

