<?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: Is there an API to add IPs to Cortex XDR EDL programmatically? in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/is-there-an-api-to-add-ips-to-cortex-xdr-edl-programmatically/m-p/1253761#M9328</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1329446827"&gt;@N.Majidova&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="105" data-start="0"&gt;Regarding the programmatic management of the Cortex XDR External Dynamic List (EDL).&lt;/P&gt;
&lt;H4 data-end="154" data-start="107" data-section-id="tfir78"&gt;1. Existing API Endpoint for EDL Management:&lt;/H4&gt;
&lt;P data-end="549" data-start="156"&gt;Currently, the Cortex XDR public API does not support the programmatic addition, modification, or management of IP addresses or domains within the hosted External Dynamic List (EDL). The EDL is designed as a distribution point for indicators to be consumed by external devices, primarily Palo Alto Networks firewalls, and entries must be managed manually via the Cortex XDR management console.&lt;/P&gt;
&lt;H4 data-end="586" data-start="551" data-section-id="73rshv"&gt;2. Roadmap and Feature Requests:&lt;/H4&gt;
&lt;P data-end="697" data-start="588"&gt;This is a known product limitation and is actively tracked as a Feature Request (FR) under the following IDs:&lt;/P&gt;
&lt;UL data-end="840" data-start="699"&gt;
&lt;LI data-end="765" data-start="699" data-section-id="1vfotyq"&gt;&lt;CODE data-end="714" data-start="701"&gt;CXDR-I-2208&lt;/CODE&gt;: Ability to manage EDL lists using the public API.&lt;/LI&gt;
&lt;LI data-end="840" data-start="766" data-section-id="17pudz7"&gt;&lt;CODE data-end="781" data-start="768"&gt;CXDR-I-2539&lt;/CODE&gt;: Automation Rules - Ability to add IPs or domains to EDLs.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-end="1078" data-start="842"&gt;There is currently no estimated timeframe (ETA) for the implementation of these features. You are encouraged to contact your Palo Alto Networks Account Team or Sales Engineer to express interest and track the progress of these requests.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;H4 data-end="1117" data-start="1080" data-section-id="fdpx72"&gt;3. Recommended Automated Approach:&lt;/H4&gt;
&lt;P data-end="1231" data-start="1119"&gt;Since direct API management is not available, the following automated or alternative approaches are recommended:&lt;/P&gt;
&lt;H5 data-end="1281" data-start="1233"&gt;PAN-OS API Integration (Direct to Firewall)&lt;/H5&gt;
&lt;P data-end="1529" data-start="1283"&gt;For SOAR platforms, the most effective automated approach is to bypass the XDR-hosted EDL and push the confirmed malicious IPs directly to the Palo Alto Networks Next-Generation Firewall (NGFW) or Panorama using their respective XML or REST APIs.&lt;/P&gt;
&lt;P data-end="1618" data-start="1531"&gt;You can add these IPs to a dedicated Address Group that the firewall uses for blocking.&lt;/P&gt;
&lt;H5 data-end="1647" data-start="1620"&gt;Manual Bulk Management:&lt;/H5&gt;
&lt;P data-end="1849" data-start="1649"&gt;If manual intervention is acceptable for high-volume updates, you can use the &lt;STRONG data-end="1742" data-start="1727"&gt;Upload File&lt;/STRONG&gt; feature in the Action Center. This allows you to import a text file (&lt;CODE data-end="1818" data-start="1812"&gt;.txt&lt;/CODE&gt;) with one IP address per line.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P data-end="1956" data-start="1851"&gt;&lt;STRONG data-end="1860" data-start="1851"&gt;Path:&lt;/STRONG&gt;&lt;BR data-end="1863" data-start="1860" /&gt;&lt;CODE data-end="1956" data-start="1863"&gt;Incident Response → Response → Action Center → New Action → Add to EDL → Select Upload File&lt;BR /&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P data-end="1956" data-start="1851"&gt;&lt;CODE data-end="1956" data-start="1863"&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;H5 data-end="1982" data-start="1958"&gt;Host Firewall Rules:&lt;/H5&gt;
&lt;P data-end="2156" data-start="1984"&gt;You may also consider using Host Firewall rules to block communications directly on supported endpoints, though this is managed via profiles rather than a dynamic list API.&lt;/P&gt;
&lt;H5 data-end="2191" data-start="2158" data-section-id="1ul0c00"&gt;(Important Constraints for EDL)&lt;/H5&gt;
&lt;H4 data-end="2213" data-start="2193"&gt;Public IPs Only&lt;/H4&gt;
&lt;P data-end="2429" data-start="2215"&gt;Cortex XDR EDLs only support public, routable IP addresses. Attempting to add private (RFC 1918) IP addresses (for example, &lt;CODE data-end="2351" data-start="2339"&gt;10.0.0.0/8&lt;/CODE&gt; or &lt;CODE data-end="2371" data-start="2355"&gt;192.168.0.0/16&lt;/CODE&gt;) via the standard EDL interface will result in the error:&amp;nbsp;&lt;CODE style="color: #3e3e3e; font-size: 13px;"&gt;Adding an internal IP address is not supported&lt;/CODE&gt;&lt;/P&gt;
&lt;DIV class="relative w-full mt-4 mb-1"&gt;
&lt;DIV class=""&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class=""&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;SPAN&gt;Format Limitations&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P data-end="2550" data-start="2528"&gt;The EDL only supports:&lt;/P&gt;
&lt;UL data-end="2615" data-start="2551"&gt;
&lt;LI data-end="2576" data-start="2551" data-section-id="on7vw8"&gt;Individual IP addresses&lt;/LI&gt;
&lt;LI data-end="2615" data-start="2577" data-section-id="40df5j"&gt;Fully Qualified Domain Names (FQDNs)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="2659" data-start="2617"&gt;Subnets and CIDR ranges are not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;like&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
    <pubDate>Mon, 11 May 2026 14:26:03 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-05-11T14:26:03Z</dc:date>
    <item>
      <title>Is there an API to add IPs to Cortex XDR EDL programmatically?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/is-there-an-api-to-add-ips-to-cortex-xdr-edl-programmatically/m-p/1253638#M9323</link>
      <description>&lt;P&gt;Hi community,&lt;/P&gt;
&lt;P&gt;I'm looking for a way to programmatically add IP addresses to the Cortex XDR External Dynamic List (EDL) via the XDR public API — ideally using a Python script.&lt;/P&gt;
&lt;P&gt;Currently, I can see that the EDL is referenced in the Audit Log API as an AUDIT_ENTITY value, but I cannot find any dedicated API endpoint to add or manage IPs in the EDL directly.&lt;/P&gt;
&lt;P&gt;Our use case: We have a SOAR platform that automatically investigates alerts. When an IP is confirmed malicious, we want to run a Python script that automatically pushes it to the XDR EDL so our Palo Alto firewall can block it — without any manual intervention.&lt;/P&gt;
&lt;P&gt;My questions:&lt;BR /&gt;1. Is there any existing API endpoint to add IPs to the XDR EDL (IP Block List)?&lt;BR /&gt;2. If not, is this on the roadmap?&lt;BR /&gt;3. What is the recommended automated approach for pushing confirmed malicious IPs from a SOAR platform to the XDR EDL?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2026 15:36:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/is-there-an-api-to-add-ips-to-cortex-xdr-edl-programmatically/m-p/1253638#M9323</guid>
      <dc:creator>N.Majidova</dc:creator>
      <dc:date>2026-05-07T15:36:49Z</dc:date>
    </item>
    <item>
      <title>Re: Is there an API to add IPs to Cortex XDR EDL programmatically?</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/is-there-an-api-to-add-ips-to-cortex-xdr-edl-programmatically/m-p/1253761#M9328</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1329446827"&gt;@N.Majidova&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="105" data-start="0"&gt;Regarding the programmatic management of the Cortex XDR External Dynamic List (EDL).&lt;/P&gt;
&lt;H4 data-end="154" data-start="107" data-section-id="tfir78"&gt;1. Existing API Endpoint for EDL Management:&lt;/H4&gt;
&lt;P data-end="549" data-start="156"&gt;Currently, the Cortex XDR public API does not support the programmatic addition, modification, or management of IP addresses or domains within the hosted External Dynamic List (EDL). The EDL is designed as a distribution point for indicators to be consumed by external devices, primarily Palo Alto Networks firewalls, and entries must be managed manually via the Cortex XDR management console.&lt;/P&gt;
&lt;H4 data-end="586" data-start="551" data-section-id="73rshv"&gt;2. Roadmap and Feature Requests:&lt;/H4&gt;
&lt;P data-end="697" data-start="588"&gt;This is a known product limitation and is actively tracked as a Feature Request (FR) under the following IDs:&lt;/P&gt;
&lt;UL data-end="840" data-start="699"&gt;
&lt;LI data-end="765" data-start="699" data-section-id="1vfotyq"&gt;&lt;CODE data-end="714" data-start="701"&gt;CXDR-I-2208&lt;/CODE&gt;: Ability to manage EDL lists using the public API.&lt;/LI&gt;
&lt;LI data-end="840" data-start="766" data-section-id="17pudz7"&gt;&lt;CODE data-end="781" data-start="768"&gt;CXDR-I-2539&lt;/CODE&gt;: Automation Rules - Ability to add IPs or domains to EDLs.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-end="1078" data-start="842"&gt;There is currently no estimated timeframe (ETA) for the implementation of these features. You are encouraged to contact your Palo Alto Networks Account Team or Sales Engineer to express interest and track the progress of these requests.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;H4 data-end="1117" data-start="1080" data-section-id="fdpx72"&gt;3. Recommended Automated Approach:&lt;/H4&gt;
&lt;P data-end="1231" data-start="1119"&gt;Since direct API management is not available, the following automated or alternative approaches are recommended:&lt;/P&gt;
&lt;H5 data-end="1281" data-start="1233"&gt;PAN-OS API Integration (Direct to Firewall)&lt;/H5&gt;
&lt;P data-end="1529" data-start="1283"&gt;For SOAR platforms, the most effective automated approach is to bypass the XDR-hosted EDL and push the confirmed malicious IPs directly to the Palo Alto Networks Next-Generation Firewall (NGFW) or Panorama using their respective XML or REST APIs.&lt;/P&gt;
&lt;P data-end="1618" data-start="1531"&gt;You can add these IPs to a dedicated Address Group that the firewall uses for blocking.&lt;/P&gt;
&lt;H5 data-end="1647" data-start="1620"&gt;Manual Bulk Management:&lt;/H5&gt;
&lt;P data-end="1849" data-start="1649"&gt;If manual intervention is acceptable for high-volume updates, you can use the &lt;STRONG data-end="1742" data-start="1727"&gt;Upload File&lt;/STRONG&gt; feature in the Action Center. This allows you to import a text file (&lt;CODE data-end="1818" data-start="1812"&gt;.txt&lt;/CODE&gt;) with one IP address per line.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P data-end="1956" data-start="1851"&gt;&lt;STRONG data-end="1860" data-start="1851"&gt;Path:&lt;/STRONG&gt;&lt;BR data-end="1863" data-start="1860" /&gt;&lt;CODE data-end="1956" data-start="1863"&gt;Incident Response → Response → Action Center → New Action → Add to EDL → Select Upload File&lt;BR /&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P data-end="1956" data-start="1851"&gt;&lt;CODE data-end="1956" data-start="1863"&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;H5 data-end="1982" data-start="1958"&gt;Host Firewall Rules:&lt;/H5&gt;
&lt;P data-end="2156" data-start="1984"&gt;You may also consider using Host Firewall rules to block communications directly on supported endpoints, though this is managed via profiles rather than a dynamic list API.&lt;/P&gt;
&lt;H5 data-end="2191" data-start="2158" data-section-id="1ul0c00"&gt;(Important Constraints for EDL)&lt;/H5&gt;
&lt;H4 data-end="2213" data-start="2193"&gt;Public IPs Only&lt;/H4&gt;
&lt;P data-end="2429" data-start="2215"&gt;Cortex XDR EDLs only support public, routable IP addresses. Attempting to add private (RFC 1918) IP addresses (for example, &lt;CODE data-end="2351" data-start="2339"&gt;10.0.0.0/8&lt;/CODE&gt; or &lt;CODE data-end="2371" data-start="2355"&gt;192.168.0.0/16&lt;/CODE&gt;) via the standard EDL interface will result in the error:&amp;nbsp;&lt;CODE style="color: #3e3e3e; font-size: 13px;"&gt;Adding an internal IP address is not supported&lt;/CODE&gt;&lt;/P&gt;
&lt;DIV class="relative w-full mt-4 mb-1"&gt;
&lt;DIV class=""&gt;
&lt;DIV class="relative"&gt;
&lt;DIV class=""&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;&lt;SPAN&gt;Format Limitations&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P data-end="2550" data-start="2528"&gt;The EDL only supports:&lt;/P&gt;
&lt;UL data-end="2615" data-start="2551"&gt;
&lt;LI data-end="2576" data-start="2551" data-section-id="on7vw8"&gt;Individual IP addresses&lt;/LI&gt;
&lt;LI data-end="2615" data-start="2577" data-section-id="40df5j"&gt;Fully Qualified Domain Names (FQDNs)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="2659" data-start="2617"&gt;Subnets and CIDR ranges are not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;like&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2026 14:26:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/is-there-an-api-to-add-ips-to-cortex-xdr-edl-programmatically/m-p/1253761#M9328</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-05-11T14:26:03Z</dc:date>
    </item>
  </channel>
</rss>

