<?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: Cortex XDR EDL in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228291#M5869</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1097754153"&gt;@OrkhanM&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I assume that you can access the EDL with the information that you are using on the firewall? Have you verified that the firewalls traffic to the EDL is actually being allowed through the traffic logs? &lt;/P&gt;</description>
    <pubDate>Tue, 06 May 2025 20:56:19 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-05-06T20:56:19Z</dc:date>
    <item>
      <title>Cortex XDR EDL</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228056#M5866</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to integrate Cortex XDR EDL with PANGFW EDL. We did everything with this guide --&amp;nbsp;&lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-Pro-Administrator-Guide/Manage-External-Dynamic-Lists" target="_blank"&gt;https://docs-cortex.paloaltonetworks.com/r/Cortex-XDR/Cortex-XDR-Pro-Administrator-Guide/Manage-External-Dynamic-Lists&lt;/A&gt;&lt;/P&gt;&lt;P&gt;After finishing setup we initiated test url access and it gave us url access error. In this case PANGFW cannot retrieve EDL added ip and domain names.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone help?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 May 2025 13:09:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228056#M5866</guid>
      <dc:creator>OrkhanM</dc:creator>
      <dc:date>2025-05-05T13:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR EDL</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228291#M5869</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1097754153"&gt;@OrkhanM&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I assume that you can access the EDL with the information that you are using on the firewall? Have you verified that the firewalls traffic to the EDL is actually being allowed through the traffic logs? &lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 20:56:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228291#M5869</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-05-06T20:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR EDL</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228390#M5874</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the problem reason. Problem was the security policy. After creating EDL list in PANGFW you should create block rule for edl inbound to outbound and outbound to inbound. After creating this rule External Dynamic List will reach to the Cortex XDR's EDL and it will retrieve the data (IP and Domain) to Firewall. In our environment Security Policy didn't configured correctly thats why this situation is happened.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your time.&lt;/P&gt;</description>
      <pubDate>Wed, 07 May 2025 12:18:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1228390#M5874</guid>
      <dc:creator>OrkhanM</dc:creator>
      <dc:date>2025-05-07T12:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR EDL</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1240321#M6404</link>
      <description>&lt;P&gt;Hello,&amp;nbsp; we had a similar issue to this and applied the EDL IP list to a current EDL policy and it started to populate.&amp;nbsp; the Test URL error apparently means nothing if it populates.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;However, I do have an ask - now we are unable to add the Domain XDR EDL list to a URL Policy.&amp;nbsp; It doesn't even show up as an option to add.&amp;nbsp; Has anyone experienced this?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Oct 2025 18:26:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/cortex-xdr-edl/m-p/1240321#M6404</guid>
      <dc:creator>Estewanalyst</dc:creator>
      <dc:date>2025-10-20T18:26:00Z</dc:date>
    </item>
  </channel>
</rss>

