Fortinet Document Library

Version:


Table of Contents

About FortiGate for AWS

Deploying FortiGate on AWS

Deploying auto scaling on AWS

Single FortiGate-VM Deployment

Use Case: High Availability for FortiGate on AWS

Security Fabric Connector Integration with AWS

Resources

Upgrade Path Tool
6.0.0
Copy Link

Setting up the FortiGate(s)

As a FortiGate feature, GuardDuty integration introduces the ability to dynamically import external block lists from an HTTP server. You can use the block lists to enforce your organization's specialized security requirements. This can include long term policies, such as always blocking access to certain websites, or short term requirements to block access to known compromised locations. Since thee lists are dynamically imported, FortiGate instantly imports any changes made to the list.

In this example, FortiGate integrates with AWS GuardDuty to populate a list, which is treated as a "threat feed". You can use a threat feed to deny access to a source or destination IP address in Web Filter and DNS Filter profiles, SSL inspection exemptions, and as a source/destination in proxy policies. The block list is stored as an external resource, which is dynamically imported to the FortiGate at a configured interval/refresh rate to maintain an updated list. The administrator can configure multiple threat feeds in each profile.

  1. To configure a threat feed, navigate to Security Fabric > Fabric Connectors, then click Create New, then IP Address under Threat Feeds.

  2. The following example creates an IP address connector. The resource name appears as an external IP block list in DNS filter profiles and as a source/destination in proxy policies. Configure the following:
    1. URI of external resource: link to an external resource file. The file should be a plain text file with one IP address on each line. In this example, the IP address is https://s3-us-east-1.amazonaws.com/***my-aws-lambda-guardduty***/ip_blocklist. The file size is up to 10 MB or 128000 lines of text, whichever is more restrictive.
    2. Refresh Rate: time interval to refresh the external resource. The rate can be between 1 to 43200 minutes.

  3. Go to Policy & Objects > IPv4 Policy and create/edit a policy. In the Source and Destination fields, you should be able to add the new feed.

Resources

Setting up the FortiGate(s)

As a FortiGate feature, GuardDuty integration introduces the ability to dynamically import external block lists from an HTTP server. You can use the block lists to enforce your organization's specialized security requirements. This can include long term policies, such as always blocking access to certain websites, or short term requirements to block access to known compromised locations. Since thee lists are dynamically imported, FortiGate instantly imports any changes made to the list.

In this example, FortiGate integrates with AWS GuardDuty to populate a list, which is treated as a "threat feed". You can use a threat feed to deny access to a source or destination IP address in Web Filter and DNS Filter profiles, SSL inspection exemptions, and as a source/destination in proxy policies. The block list is stored as an external resource, which is dynamically imported to the FortiGate at a configured interval/refresh rate to maintain an updated list. The administrator can configure multiple threat feeds in each profile.

  1. To configure a threat feed, navigate to Security Fabric > Fabric Connectors, then click Create New, then IP Address under Threat Feeds.

  2. The following example creates an IP address connector. The resource name appears as an external IP block list in DNS filter profiles and as a source/destination in proxy policies. Configure the following:
    1. URI of external resource: link to an external resource file. The file should be a plain text file with one IP address on each line. In this example, the IP address is https://s3-us-east-1.amazonaws.com/***my-aws-lambda-guardduty***/ip_blocklist. The file size is up to 10 MB or 128000 lines of text, whichever is more restrictive.
    2. Refresh Rate: time interval to refresh the external resource. The rate can be between 1 to 43200 minutes.

  3. Go to Policy & Objects > IPv4 Policy and create/edit a policy. In the Source and Destination fields, you should be able to add the new feed.