EDL

Use the Generic Export Indicators Service integration to provide an endpoint with a list of indicators as a service for the system indicators.

The Generic Export Indicators Service integration is a long-running integration. For more information about long-running integrations, see the Cortex XSOAR 8 Cloud, Cortex XSOAR 8 On-prem or Cortex XSIAM documentation.

PAN-OS EDL Management to Export Indicators Service (PAN-OS EDL Service) migration steps

Unlike PAN-OS EDL Management, this integration hosts the EDL on the Cortex XSOAR server. Follow these steps to migrate your EDLs.

1. Convert existing EDL lists to indicators in Cortex XSOAR. This can be done automatically:
   1. Extract your EDL as a text file from the web server it’s currently hosted on.
   2. Upload it as a file to the Playground and use the ExtractIndicatorsFromTextFile automation. e.g., !ExtractIndicatorsFromTextFile entryID=<entry_id>
2. Go to the Indicators page in Cortex XSOAR 6.13, Cortex XSOAR 8 Cloud, Cortex XSOAR 8.7 On-prem, or Cortex XSIAM to find all of the indicators you extracted from the text file.
3. If needed, batch select the indicators and add a tag to the indicators you want to host as a specific EDL. Use this tag in the Indicator Query integration parameter when configuring the integration. For example, if you want to create an allowed list of indicators and a blocked list of indicators.
4. Edit the EDL object on the PAN-OS device to pull from the Export Indicators Service (PAN-OS EDL Service) instance, as explained in Access the Export Indicators Service by Instance Name (HTTPS). You can edit the EDL object using the panorama-edit-edl command in the Palo Alto Networks PAN-OS integration.
5. Commit and push the configuration from the Panorama device to its respective Firewalls using the PAN-OS Commit Configuration playbook.
6. If you have a deployment with 100 firewalls or more, we recommend using your Panorama device and creating an EDL object there, which will be populated from the PAN-OS EDL Service. Then push the EDL object to the respective firewalls.
7. Follow the instructions in the rest of this guide to make sure that the PAN-OS device is connected to the EDL service.

Important Notes:

• EDL uses three consecutive ports: the configured Listen Port, port + 1, and port + 2. NGINX listens on the configured port (public), the Python process listens on port + 1, and NGINX uses port + 2 internally for its fail-fast cache fetch tier. For example, if configured for port 9009, ports 9009, 9010, and 9011 must all be free. Ensure no other instance uses a Listen Port within 2 of another, or an [Errno 98] Address in use error will occur. When running without --network=host, ports + 1 and + 2 are not exposed to the machine.
• If you frequently use different queries for the same EDL instance through the q inline argument, use separate EDL instances (one per query) and set a default query for each to improve performance.
• When using the q inline argument, the number of exported indicators is limited to 100,000 for performance reasons. To export more than 100,000 indicators, create a new integration instance with the desired Indicator Query and List Size.
• Note: After successfully configuring an instance, clicking the ‘Test’ button again may display a failure because the system incorrectly assumes the port is in use. Despite this message, the instance continues to function correctly.
• When the integration is configured with Update list on demand only, the indicator list refreshes based on the value set in the Refresh Rate parameter.

Use Cases

---

1. Export a list of malicious IPs to block via a firewall.
2. Export a list of indicators to a service such as Splunk, using a supported output format.
3. Generate feeds to be used on PAN-OS as External Dynamic Lists.
4. Create External Dynamic Lists (EDLs) of the IP addresses, URLs, and domains used by ransomware, known APT groups, and active malware campaigns for tracking in AutoFocus.
5. Create External Dynamic Lists to track IPs and URLs commonly used by Microsoft Office365 or CDNs and cloud services, or used as tor exit nodes.

Configure Generic Export Indicators Service on Cortex XSOAR

---

1. Navigate to Settings > Integrations > Servers & Services.
2. Search for Generic Export Indicators Service.
3. Click Add instance to create and configure a new integration instance.

Parameter	Description	Required
Update list on demand only	Enabling this prevents automatic list refresh.	False
Indicator Query	The query to run to update the indicators list. To view expected results, run the following command from the Cortex XSOAR CLI !findIndicators query=<your query> (Field names in your query should match the Machine name (Cortex XSOAR 6.13) or Machine name (Cortex XSOAR 8 Cloud) or Machine name (Cortex XSOAR 8.7 On-prem) for each field.)	False
Outbound Format	The format of the exported list.	True
Exported Fields	For use with JSON and CSV formats - select specific Cortex XSOAR fields to export. If given the value ‘all’ - all Cortex XSOAR fields are exported. If empty - only value and type are exported.	False
List Size	Maximum number of items in the list.	True
Refresh Rate	How often to refresh the list (e.g., less than 1 minute, 5 minutes, 12 hours, 7 days, 3 months, 1 year). For performance reasons, we do not recommend setting this value at less than 1 minute.	False
Listen Port	Runs the service on this port from within Cortex XSOAR. Requires a unique port for each long-running integration instance. Do not use the same port for multiple instances. Note: If you click the test button more than once, a failure may occur mistakenly indicating that the port is already in use. (For Cortex XSOAR 8 Cloud and Cortex XSIAM) If using an engine, you must enter a Listen Port. If not using an engine, do not enter a Listen Port and an unused port for the Generic Export Indicators Service will automatically be generated when the instance is saved.	True
Certificate (Required for HTTPS)	For use with HTTPS - the certificate that the service should use. Supported for Cortex XSOAR On-prem (6.x or 8) or when using an engine. Cortex XSOAR 8 Cloud tenants and Cortex XSIAM tenants do not support custom certificates.	False
Private Key (Required for HTTPS)	For use with HTTPS - the private key that the service should use. Supported for Cortex XSOAR On-prem (6.x or 8) or when using an engine. Cortex XSOAR 8 Cloud tenants and Cortex XSIAM tenants do not support private keys.	False
Username	Uses basic authentication for accessing the list. If empty, no authentication is enforced.	(For Cortex XSOAR 6.x) False (For Cortex XSOAR 8 and Cortex XSIAM) Optional for engines, otherwise mandatory.
Password	Uses basic authentication for accessing the list. If empty, no authentication is enforced.	(For Cortex XSOAR 6.x) False (For Cortex XSOAR 8 and Cortex XSIAM) Optional for engines, otherwise mandatory.
Add comment to empty list	If selected, add to an empty list the comment “# Empty list”.	False
Strip ports from URLs	If selected, ports in URLs are removed. For example, ‘www.example.com:9999/path’ becomes ‘www.example.com/path’.	False
Strip protocols from URLs	If selected, strips the protocol from URLs (http/https)/.	False
Truncate URL length	If selected, URLs are truncated to no more than 254 characters.	False
Prepend string to list	String to add to beginning of published list. Supports newline characters (\n).	False
Append string to list	String to add to end of published list. Supports newline characters (\n).	False
IP Collapsing	For use with PAN-OS (text) format - collapse method for IPs (none, range, CIDR).	False
PAN-OS: drop invalid URL entries	For use with PAN-OS (text) format - if selected, any URL entry that is not compliant with PAN-OS URL format is dropped instead of rewritten.	False
McAfee Gateway: Indicator List Type	For use with McAfee Web Gateway format - set the indicator list type.	False
Symantec ProxySG: Default Category	For use with Symantec ProxySG format - set the default category for the output.	False
Symantec ProxySG: Listed Categories	For use with Symantec ProxySG format - set the categories that should be listed in the output. If not set, lists all existing categories.	False
Show CSV formats as Text	If selected, CSV format appears in a textual webpage instead of initiating a file download.	False
XSOAR Indicator Page Size	Internal page size used when querying Cortex XSOAR for the indicators.	False
Maximum Size of CIDR Block (by mask bit)	CIDRs with a lower network prefix bits number are not included. For example - if the number is 8, then 0.0.0.0/2 is excluded from the list.	False
Exclude top level domainGlobs	Option to remove top level domainGlobs from the list. For example - *.com.	False
Advanced: NGINX Global Directives	NGINX global directives to be passed on the command line using the -g option. Each directive should end with ;. For example: worker_processes 4; timer_resolution 100ms;. Advanced configuration to be used only if instructed by Cortex XSOAR Support.	False
Advanced: NGINX Server Conf	NGINX server configuration to be used instead of the default NGINX_SERVER_CONF used in the integration code. Advanced configuration to be used only if instructed by Cortex XSOAR Support.	False
Cache Lock Timeout (Deprecated)	The parameter is deprecated and no longer used. Cache locking was replaced by a two-tier fail-fast design that rejects excess concurrent cache-building requests instead of queuing them.	False
Cache Lock Age (Deprecated)	The parameter is deprecated and no longer used. Cache locking was replaced by a two-tier fail-fast design that rejects excess concurrent cache-building requests instead of queuing them.	False
Cache 404 TTL	The TTL for 404 responses in the cache.	False
Cache Default TTL	The default TTL for responses in the cache.	False
Advanced: NGINX Read Timeout	NGNIX read timeout in seconds.	False
Advanced: use legacy queries	When enabled, the integration queries the server using full queries. Advanced configuration to be used only if instructed by Cortex XSOAR Support, or you’ve encountered log errors in the form of: ‘msgpack: invalid code.’	False

Safeguards

There are two integrations parameters used as safeguards: Maximum CIDR network prefix bits size and Exclude top level domainGlobs.

These parameters prevent the integration from incorrectly inserting unwanted TLDs or a CIDR with a too wide range.

The default value for Maximum CIDR network prefix bits size is 8, which means that CIDRs with a lower network prefix bits number are not included (such as 0.0.0.0/2).

The default value for Exclude top level domainGlobs is off. If enabled, the exported list does not hold indicators such as *.com, *.co.uk, *.org and other top level domains.

Unique Behaviors

domainGlob

When parsing domainGlob indicator types, the parser creates two different inputs (usually how DNS Firewalls work). For example if the domainGlob *.bad.com is parsed, it outputs two lines to the list:

1. *.bad.com
2. bad.com

The DNS also blocks bad.com which does not happen if only *.bad.com is listed.

IP Collapsing

When IP Collapsing is enabled, duplications of IP ranges are removed. For example if there are 2 CIDRs in the list - 1.2.3.0/8 and 1.2.3.0/16 - only 1.2.3.0/8 will be included in the exported list.

Append string to list

Option to add a list of constant values to the exported list.
Expected value is a string, supports newline characters (\n).

PAN-OS: drop invalid URL entries

When PAN-OS: drop invalid URL entries is enabled, any URL entry that is not compliant with PAN-OS URL format is dropped instead of rewritten.

Exported Fields

This applies to the JSON and CSV formats - select specific Cortex XSOAR fields to export.
If given the value all - all of Cortex XSOAR’s available fields will be exported. If set to empty - only the indicator value and type will be exported.

Optional system fields are:

• id
• modified
• sortValues
• comments
• indicator
• value
• source
• sourceInstances
• sourceBrands
• investigationIDs
• lastSeen
• firstSeen
• lastSeenEntryID
• firstSeenEntryID
• CustomFields
• tags
• expirationStatus
• expirationSource
• calculatedTime
• lastReputationRun
• modifiedTime
• aggregatedReliability
• communitynotes

In addition to the system fields, you can also search for custom fields.
In order to get the list of all available fields to search by, you can configure the Exported Fields parameter with the all option and check the list returned.

Access the Export Indicators Service by Instance Name (HTTPS) - For Cortex XSOAR 6.x only

Note:
By default, the route is open without security hardening and might expose you to network risks. Cortex XSOAR recommends that you use credentials to connect to the integration.

To access the Export Indicators service by instance name, make sure Instance execute external is enabled.

1. Navigate to Settings > About > Troubleshooting.
2. In the Server Configuration section, verify that the instance.execute.external key is set to true. If this key does not exist, click + Add Server Configuration and add the instance.execute.external and set the value to true. See this documentation for further information.
3. In a web browser, go to:
   https://<xsoar_address>/instance/execute/<instance_name>

Set up Authentication

EDLs running on tenants in Cortex XSOAR 8 Cloud or Cortex XSIAM require basic authentication. EDLs running on engines do not require basic authentication, but it is recommended.
For Cortex XSOAR On-prem (6.x or 8) or when using engines, you can set up authentication using custom certificates. For more information on setting up a custom certificate for Cortex XSOAR 8 On-prem, see HTTPS with a signed certificate.

Access EDLs on Cortex XSOAR 8 Cloud and On-prem and Cortex XSIAM

Note:
For Cortex XSOAR 8 On-prem, you need to add the ext- FQDN DNS record to map the Cortex XSOAR DNS name to the external IP address.
For example, ext-xsoar.mycompany.com.

For Cortex XSOAR 8 Cloud, Cortex XSOAR 8 On-prem and Cortex XSIAM, you can only access the Export Indicators Service using a third-party tool such as curl.

• For Cortex XSOAR, if the integration is configured to run on a tenant, use https://ext-<cortex-xsoar-address>/xsoar/instance/execute/<instance-name>.

  For example: curl -v -u user:pass https://ext-mytenant.paloaltonetworks.com/xsoar/instance/execute/edl_instance_01?q=type:ip

• For Cortex XSIAM, if the integration is configured to run on a tenant, you must replace the xdr in the URL with crtx. For example, if the tenant URL is https://platform-test.xdr-qa2-uat.us.example.com/, use https://ext-platform-test.crtx-qa2-uat.us.example.com/.

  For example: curl -v -u user:pass https://ext-platform-test.crtx-qa2-uat.us.example.com/xsoar/instance/execute/edl_instance_01?q=type:ip

• If the integration is configured to run on an engine, use http://<engine-address>:<integration listen port>.

  For example: curl -v -u user:pass http://<engine_address>:<listen_port>?n=50

URL Inline Arguments

Use the following arguments in the URL to change the request:

Argument Name	Description	Example
n	The maximum number of entries in the output. If no value is provided, uses the value specified in the List Size parameter configured in the instance configuration.	https://{server_host}/instance/execute/{instance_name}?n=50
s	The starting entry index from which to export the indicators when index 0 is the first position.	https://{server_host}/instance/execute/{instance_name}?s=10&n=50
v	The output format. Supports PAN-OS (text), CSV, JSON, mwg and proxysg (alias: bluecoat).	https://{server_host}/instance/execute/{instance_name}?v=JSON
q	The query used to retrieve indicators from the system. If you are using this argument, no more than 100,000 can be exported through the EDL.	https://{server_host}/instance/execute/{instance_name}?q="type:ip and sourceBrand:my_source"
t	Only with mwg format. The type indicated on the top of the exported list. Supports: string, applcontrol, dimension, category, ip, mediatype, number and regex.	https://{server_host}/instance/execute/{instance_name}?v=mwg&t=ip
sp	If set, strips ports off URLs.	https://{server_host}/instance/execute/{instance_name}?v=PAN-OS (text)&sp
pr	If set, strips protocol off URLs.	https://{server_host}/instance/execute/{instance_name}?v=text&pr
di	Only with PAN-OS (text) format. If set, ignores URLs which are not compliant with PAN-OS URL format instead of rewriting the URLs.	https://{server_host}/instance/execute/{instance_name}?v=PAN-OS (text)&di
tr	Only with PAN-OS (text)Whether to collapse IPs. 0 - to not collapse, 1 - collapse to ranges or 2 - collapse to CIDRs	https://{server_host}/instance/execute/{instance_name}?q="type:ip and sourceBrand:my_source"&tr=1
cd	Only with proxysg format. The default category for the exported indicators.	https://{server_host}/instance/execute/{instance_name}?v=proxysg&cd=default_category
ca	Only with proxysg format. The categories which are exported. Indicators not falling into these categories are classified as the default category.	https://{server_host}/instance/execute/{instance_name}?v=proxysg&ca=category1,category2
tx	Whether to output CSV format as textual web pages.	https://{server_host}/instance/execute/{instance_name}?v=CSV&tx
mc	Configure max CIDR size.	https://{server_host}/instance/execute/{instance_name}?mc=10
nt	Configure whether to exclude top level domainGlobs.	https://{server_host}/instance/execute/{instance_name}?nt=true

Commands

You can execute these commands from the Cortex XSOAR CLI as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.

export-indicators-list-update

---

Updates values stored in the List (only available On-Demand).

Base Command

export-indicators-list-update

Input

Argument Name	Description	Required
query	The query to run to update the indicators list. To view expected results, run the following command from the Cortex XSOAR CLI !findIndicators query=<your query>. An empty value may load unwanted indicators.	Required
format	The output format.	Optional
edl_size	The maximum number of entries in the output. If no value is provided, uses the value specified in the List Size parameter configured in the instance configuration.	Optional
print_indicators	If set to true, prints the indicators that were saved to the export indicators service.	Required
mwg_type	For use with McAfee Web Gateway format to indicate the list type.	Optional
url_port_stripping	If true, strips the port off URLs.	Optional
url_protocol_stripping	If true, strips the port off URLs.	Optional
drop_invalids	For use with PAN-OS (text) format - if checked any URL entry which is not compliant with PAN-OS EDL URL format is dropped instead of rewritten.	Optional
category_attribute	For use with Symantec ProxySG format - set the categories that should be listed in the output. If not set lists all existing categories.	Optional
category_default	For use with Symantec ProxySG format - set the default category for the output.	Optional
collapse_ips	For use with PAN-OS (text) format - Whether to collapse IPs, and if so - to ranges or CIDRs	Optional
csv_text	If true, outputs csv format as textual web pages	Optional
add_comment_if_empty	If selected, add to an empty List the comment “# Empty List”.	Optional

Context Output

There is no context output for this command.

Command Example

!export-indicators-list-update=type:IP edl_size=2

Human Readable Output

‘EDL will be updated the next time you access it’

Troubleshooting

• Indicators that are passed through the integration undergo formatting and deduplication, which may lead to an apparent loss of indicators.
  For instance, enabling the Strip ports from URLs option may cause two URLs that are similar but use different ports to be merged into a single indicator after formatting, resulting in the removal of one of them as a duplicate.
• In case all fields are selected, there is a potential memory issue when dealing with CSV or JSON format files that exceed 150,000 entries.

Custom HTTP Headers

The response from EDL’s endpoint includes custom headers, starting with the X-EDL prefix, that can be used for debugging purposes.
The headers are:

• X-EDL-Created - The date and time the response was created.
• X-EDL-Query-Time-Secs - The time it took to execute the query and format the response.
• X-EDL-Size - The number of indicators returned in the response.
• X-EDL-Origin-Size - The number of indicators originally fetched before formatting and deduplication.

Execution Time

• 10,000 indicators can take 10-20 seconds.
• 100,000 indicators can take up to 1-3 minutes.
• 1,000,000 indicators can take over half an hour.

In 5 minutes (the default timeout of the integration) the integration can export between 200,000 to 400,000 indicators,
depending on the load of the server, the existing indicators in the server, and the query used.

The NGINX Read Timeout can be set to increase the timeout.

Troubleshooting

504 Gateway error

1. Increase the NGINX Read Timeout in the instance configuration (for 1,000,000 indicators, it is recommended to increase the timeout up to 1 hour).
2. If the issue persists, try to increase the Load Balancer timeout through the Devops team. For 800,000 indicators, it is recommended to increase the timeout up to 1 hour (depending on the indicator query).

429 Too Many Requests error

NGINX prevents concurrent builds of the same cache entry. If multiple requests for the same cache entry (matching the URL and parameters, like q) arrive simultaneously, NGINX builds the entry for the first request and rejects the others with an HTTP 429 Too Many Requests rather than queuing them. Requests for different entries are still processed in parallel. If a request triggers a refresh of an existing cache entry, the previous data is served (HTTP 200) with no 429.

This is expected behavior. Retry the request after a short delay; once the initial build finishes populating the cache, retries are served from the cache (HTTP 200).

Deleted or expired indicators showing in EDL export

Append expirationStatus:active to the end of the query.

EDL Log

To view logs concerning the creation of the indicator list and its current status, add the /log suffix to the list URL.

For Cortex XSOAR Cloud, use https://ext-<cortex-xsoar-address>/xsoar/instance/execute/<instance-name>/log

For Cortex XSOAR On-prem, use https://*<xsoar_address>*/instance/execute/*<instance_name>*/log

For Cortex XSIAM, use https://ext-<cortex-xsiam-address>/xsoar/instance/execute/<instance-name>/log and replace the xdr in the URL with crtx.