FortiGate External Threat Feed Setup: Add an IP Block List Step by Step

Create an IP Address feed, point it at a block list URL, use it in a deny policy, and confirm FortiOS loaded the entries.

Jump to the steps
By CalMax Systems Security Research, founder · Published November 12, 2026 · Checked against the FortiOS 7.6.4 and 7.6.6 Administration Guides, the 7.4.0 guide, and Fortinet technical tips (sources below)

Short answer

A FortiGate threat feed (an external block list; Palo Alto calls it an EDL) is a text file of IP addresses that FortiOS downloads from a URL on a schedule. Create it at Security Fabric > External Connectors > Create New > IP Address, enter the URL and refresh rate, then deny the feed in a policy.

Test first: open the free 200-entry sample. No signup is required.

Naming by version: the FortiOS 7.6 Administration Guide calls the GUI section External Feeds; the 7.4 guide calls it Threat Feeds. Older Fortinet articles say External Block List or Fabric Connectors > Threat Feeds. In the CLI it is always config system external-resource.

What Format Does a FortiGate IP Threat Feed Need?

A plain-text file on an HTTP or HTTPS server that the FortiGate can reach.

  • One IPv4 or IPv6 address, address range, or subnet per line.
  • Comments start with #.
  • FortiOS does not check for duplicate entries.
  • Entry and file-size limits depend on the FortiOS release and model. Entries beyond the limit are not loaded. See FortiGate threat feed limits.

Valid IP feed example

# documentation-only ranges, not a real block list
192.0.2.10
198.51.100.0/24
203.0.113.10-203.0.113.25

A subnet such as 198.51.100.0/24 is one line, so a CIDR-aggregated list covers many addresses per entry.

How to Set Up a FortiGate Threat Feed

Steps 1 to 5 create and check the feed. Steps 6 and 7 enforce it. Replace names, interfaces and IDs with your own.

Step 1

Get the feed URL

Use any HTTPS URL that returns the plain-text list. For ThreatListPro, test with the free sample above, then use the URL from your welcome email:

https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt
Step 2

Create the IP Address feed in the GUI

Go to Security Fabric > External Connectors, click Create New, and select IP Address in the External Feeds (or Threat Feeds) section. Set:

  • Name: for example ThreatListPro.
  • Update method: External Feed (the pull method).
  • URL of external resource: the feed URL. HTTP, HTTPS and STIX are supported.
  • HTTP basic authentication: only if the server needs a username and password. ThreatListPro does not; the key is in the URL.
  • Refresh Rate: in minutes, 1 to 43,200, default 5. Use 60 for a list that republishes every 6 hours.

Click OK. With multiple VDOMs, you can create the feed in the global VDOM or inside one VDOM.

Step 3

Or create it in the CLI

This creates the feed with FortiOS defaults. Certificate checking is an extra line, explained below the example.

config system external-resource
    edit "ThreatListPro"
        set status enable
        set type address
        set resource "https://api.threatlistpro.com/v1/YOUR_API_KEY/blocklist.txt"
        set refresh-rate 60
    next
end

Fortinet recommends server certificate validation: add set server-identity-check full (FortiOS 7.0.8, 7.2.4 or later) inside the edit block, then check that the feed still updates. The documented default is none. Fortinet documents a known issue where validation makes the feed fail with “Server not reachable” on FortiOS 7.4.5 to 7.4.8 and 7.6.1 to 7.6.3, resolved in 7.4.9 and 7.6.4. If the FortiGate must fetch through a specific interface or source address, set interface-select-method, source-ip or source-ip-interface.

Step 4

Check that the entries loaded

Edit the connector and click View Entries; the Last Update field shows when the feed last updated. From the CLI:

diagnose sys external-address-resource list ThreatListPro
diagnose sys external-resource stats
execute update-external-resource ThreatListPro

The first command lists the loaded entries. The second shows valid and error lines for every feed. The third refreshes this one feed now. If the count is zero or an error appears, see FortiGate threat feed limits and errors.

Step 5

Check the list against your own users

Before you enforce any block list, compare it with the source IPs your users and partners connect from. If a trusted network appears, allow it in a policy above the deny policy.

Step 6

Deny the feed in a firewall policy

Go to Policy & Objects > Firewall Policy. The feed appears in the IP ADDRESS FEED section of the address list. To block inbound traffic from listed IPs, put the feed in Source, set Action to DENY, and place the policy above the policies that allow that traffic. A new policy is added at the bottom, so move it with move in the CLI or by dragging it in the GUI.

config firewall policy
    edit <unused-id>
        set name "block-threatlistpro"
        set srcintf "wan1"
        set dstintf "internal"
        set srcaddr "ThreatListPro"
        set dstaddr "all"
        set action deny
        set schedule "always"
        set service "ALL"
        set logtraffic all
        set match-vip enable
    next
    move <deny-id> before <allow-id>
end

match-vip enable matters when servers are published through a VIP: Fortinet explains that a VIP’s destination NAT happens before policy lookup, so a regular deny policy does not block that traffic without it.

Step 7

Protect the FortiGate itself with a local-in policy

Traffic to the FortiGate itself, such as an SSL VPN or IPsec gateway on the WAN interface, is controlled by local-in policies. Fortinet supports an IP feed as the source or destination of a local-in policy from FortiOS 7.2.4 and 7.4.0; the 7.0 series does not support it as a source.

config firewall local-in-policy
    edit <unused-id>
        set intf "wan1"
        set srcaddr "ThreatListPro"
        set dstaddr "all"
        set service "ALL"
        set schedule "always"
        set action deny
    next
end

This denies every service on wan1 from listed IPs. To limit it to the VPN service, and for loopback or IPsec setups, follow the FortiGate SSL VPN brute force guide.

Test

Confirm the block on a new session

Fortinet documents that existing sessions are not re-evaluated when a feed updates by default, and that on FortiOS 7.6.7 and later new entries can take several minutes to reach enforcement. Test with a new connection, or have existing sessions re-checked with config system settings, set ext-resource-session-check enable, which Fortinet notes adds CPU load. Fortinet’s local-in example confirms the drop with debug flow:

diagnose debug flow filter addr <listed-ip>
diagnose debug enable
diagnose debug flow trace start 10

A local-in drop shows a message such as iprope_in_check() check failed on policy 1, drop. Run diagnose debug disable when you finish.

FortiGate Threat Feed Not Working? Common Errors

Short checks here; the full error index with debug commands is in FortiGate threat feed limits and errors.

Symptom Likely cause Check
Threat feed update failed Retrieval, authentication, TLS or parsing failed. Run diagnose debug application forticron -1 and diagnose debug enable, then execute update-external-resource <name>, and read the HTTP or TLS result.
Server not reachable after enabling certificate validation The known issue on 7.4.5 to 7.4.8 and 7.6.1 to 7.6.3, or a certificate the FortiGate cannot validate. Upgrade to 7.4.9 or 7.6.4 or later; confirm the server’s certificate chain.
0 entries Wrong feed type, or lines the parser rejects. Confirm the type is IP Address (set type address) and check error lines in diagnose sys external-resource stats.
Loaded but not blocking No policy references the feed, a different policy matches first, or the session existed before the update. Check policy order and direction, use match-vip for VIP traffic, and test a new session.
Entries missing at the end The release or model entry limit was reached and later entries were truncated. Compare valid lines with the limit for your release. See FortiGate limits.
If the server goes down: Fortinet says the feed keeps working with the entries it already has, but it is not updated until the connection is re-established.

Where a VPN Brute Force Block List Fits

ThreatListPro is published in the format an IP Address feed expects.

Each line is one IPv4 address or CIDR. The list covers 5.4M+ IPv4 addresses in a few thousand entries, well under the FortiOS entry limits, and is checked for new attackers every 6 hours. Its source is real attacks on live production Palo Alto GlobalProtect VPN portals in the US.

For SSL VPN or IPsec on a FortiGate, the FortiGate brute force guide shows the local-in policy for the VPN service only. The Palo Alto EDL vs dynamic address group page covers the PAN-OS side.

Limits: a new IP’s first attempt still arrives. The feed is IPv4 only. CIDR ranges include addresses that did not each attack, so check your users’ source IPs first and allow-list trusted networks. A block list does not replace MFA, patching or logging.

FortiGate Threat Feed Setup FAQs

Where is the threat feed setting on a FortiGate?

Go to Security Fabric > External Connectors and click Create New. Select IP Address in the External Feeds section, which the FortiOS 7.4 guide calls Threat Feeds. In the CLI, the same object is config system external-resource with set type address.

What format does a FortiGate IP address threat feed need?

A plain-text file with one IPv4 or IPv6 address, address range, or subnet per line, served over HTTP or HTTPS. Lines starting with # are comments. FortiOS does not remove duplicates, and entries beyond the release and model limit are not loaded.

What refresh rate should a FortiGate threat feed use?

The Refresh Rate is in minutes, from 1 to 43,200, and the default is 5. Match it to how often the list changes. For a list that republishes every 6 hours, such as ThreatListPro, 60 minutes is enough.

Can I use a threat feed in a FortiGate local-in policy?

Yes, from FortiOS 7.2.4 and 7.4.0, as the source or destination address. The FortiOS 7.0 series does not support a feed as a local-in source. Use a local-in policy to protect services on the FortiGate itself, such as an SSL VPN or IPsec gateway on the WAN interface.

How do I check that a FortiGate threat feed loaded?

Edit the connector and click View Entries, or run diagnose sys external-address-resource list followed by the feed name. diagnose sys external-resource stats shows valid and error lines for every feed, and execute update-external-resource followed by the feed name refreshes one feed now.

Why does my threat feed deny policy not block traffic to a VIP?

A VIP translates the destination before the policy lookup, so a regular deny policy does not match that traffic. Fortinet’s fix is to enable match-vip on the deny policy in the CLI. Also confirm the policy sits above the allow policies and test with a new session.

Sources

Block Known Sources Before They Reach Your FortiGate

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed. Yearly is $200. Enterprise is $99.99/month for up to 50 firewalls. Paid plans have a 14-day money-back guarantee.

Start a 14-day free trial Or test 200 entries first: free, no signup

Related Resources

Protect the VPN, size the feed, or compare with Palo Alto.

Stop FortiGate SSL VPN Brute Force FortiGate Threat Feed Limits and Errors FortiGate SSL VPN Log Messages What Is an External Dynamic List? Palo Alto EDL vs Dynamic Address Group Free EDL and Threat Feed URLs