index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,755
|
Fortinet Security Fabric
d. You now see the fingerprint.
You can configure the following for the fingerprint:
1. Update Interval: The default value is 60 seconds. You can change the value to between 1 and 3600
seconds.
2. Status: Green means that the connector is enabled. You can disable it at any time by toggling the switch.
e. Click OK.
6. Go to Policy & Objects > Addresses and select Address.
7. Click Create new.
8. Configure the address as needed, selecting the OCI connector in the SDN Connector field. The following filters are
supported:
'vm_name=<vm name>': matches VM instance name.
'instance_id=<instance id>': matches instance OCID.
'tag.<key>=<value>': matches freeform tag key and its value.
'definedtag.<namespace>.<key>=<value>': matches a tag namespace, tag key, and its value.
9. Click OK.
To configure an OCI SDN connector in the CLI:
1. Configure an SDN connector:
config system sdn-connector
edit "oci1"
set status enable
set type oci
set tenant-id
"ocid1.tenancy.oc1..aaaaaaaaaaa3aaaaaaaaaaaaaaaaa77xxxxxx54bbbbbb4xxxx35xx55xxxx"
set user-id
"ocid1.user.oc1..aaaaaaaaa2laaaaa3aaaaaaaaaabbbbbbbbbbcccc3ccccccccccxxxxxxxx"
set compartment-id
"ocid1.compartment.oc1..aaaaaaaaaaaaaaaaaa7bbbbbbbbbbcccccccccc6xxx53xxxx7xxxxxxxxxx"
set oci-region "us-ashburn-1"
set oci-region-type commercial
set oci-cert "cert-sha2"
FortiOS 7.6.2 Administration Guide 3756
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,756
|
Fortinet Security Fabric
set update-interval 30
next
end
2. Create a dynamic firewall address for the SDN connector with a supported filter:
config firewall address
edit "oci-address-1"
set type dynamic
set sdn "oci1"
set filter "CompartmentName=DevelopmentEngineering"
next
end
To confirm that dynamic firewall addresses are resolved by the SDN connector:
1. In the CLI, check that the addresses are listed:
config firewall address
edit "oci-address-1"
set type dynamic
set sdn "oci1"
set filter "CompartmentName=DevelopmentEngineering"
config list
edit "10.0.0.11"
next
edit "10.0.0.118"
next
...
next
end
next
end
2. In the GUI, go to Policy & Objects > Addresses and hover the cursor over the address name.
OpenStack SDN connector using node credentials
To configure OpenStack SDN connector using node credentials:
1. Go to Security Fabric > External Connectors.
2. Click Create New, then select OpenStack (Horizon).
FortiOS 7.6.2 Administration Guide 3757
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,757
|
Fortinet Security Fabric
3. Configure the fields as follows:
a. Name: Name the connector as desired.
b. IP: Enter the OpenStack management component's IP address. Generally you can find it in the OpenStack
identity.
c. User name: Enter the specified node's administrator name.
d. Password: Enter the administrator password.
4. Click OK. The SDN connector is now configured.
To configure a dynamic firewall address:
The next step is to create an address that will be used as an address group or single address that acts as the
source/destination for firewall policies. The address is based on IP addresses and contains VM instances' IP addresses.
No matter what changes occur to the instances, the SDN connector populates and updates the changes automatically
based on the specified filtering condition so that administrators do not need to reconfigure the address content manually.
Appropriate firewall policies using the address are applied to instances that are members of the address.
FortiOS 7.6.2 Administration Guide 3758
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,758
|
Fortinet Security Fabric
1. Go to Policy & Objects > Address. Click Create New, then select Address.
2. Configure the address as follows:
a. Name: Name the address as desired.
b. Type: Select Dynamic.
c. Sub Type: Select Fabric Connector Address.
d. SDN Connector: Select openstack.
e. Filter: The SDN connector automatically populates and updates only IP addresses belonging to the specified
filter that matches the condition. OpenStack Horizon connectors support the following filters:
i. id=<instance id>: This matches a VM instance ID.
ii. name=<instance name>: This matches a VM instance name.
iii. flavor=<instance flavor name>: This matches an instance flavor name.
iv. keypair=<key pair name>: This matches a key pair name.
v. network=<net name>: This matches a network name.
vi. project=<project name>: This matches a project name.
vii. availabilityzone=<zone name>: This matches an availability zone name.
viii. servergroup=<group name>: This matches a server group name.
ix. securitygroup=<security group name>: This matches a security group name.
x. metadata.<key>=<value>: This matches metadata with its key and value pair.
You can set filtering conditions using multiple entries with AND ("&") or OR ("|"). When both AND and OR are
specified, AND is interpreted first, then OR.
For example, you could enter flavor=m1.nano&project=admin. In this case, IP addresses of instances that
match both the flavor name and project name are populated. Wildcards (asterisks) are not allowed in values.
In this example, let's use project=admin, assuming the project name is admin.
FortiOS 7.6.2 Administration Guide 3759
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,759
|
Fortinet Security Fabric
3. Click OK after completing all required fields.
4. Ensure that the address was created.
5. After a few minutes, the new address takes effect. Hover your cursor on the address to see a list of IP addresses
and instances with the project name "admin".
FortiOS 7.6.2 Administration Guide 3760
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,760
|
Fortinet Security Fabric
SAP SDN connector
The SAP external Fabric connector allows the FortiGate to connect to an SAP instance to synchronize dynamic address
objects and ports for SAP workloads. These address objects can be used in firewall policies to grant access control to
dynamic SAP workloads.
To configure an SAP connector in the GUI:
1. Configure the SAP SDN connector:
a. Go to Security Fabric > External Connectors and click Create New.
b. In the Private SDN section, select SAP.
c. Enter a Name (sap-s4-docker).
d. Enter the IP for the SAP instance.
e. Enter the Username and Password.
f. Click OK.
2. Configure a network service associated with the configured SAP SDN connector:
a. Go to Policy & Objects > Internet Service Database, select the Network Services tab, and click Create New.
b. Enter a Name (sap-instance1).
c. Set SDN connector to sap-s4-docker.
d. Select a filter, such as InstanceNumber=1. The available filters are for HostName, InstanceNumber, and
ServiceName.
FortiOS 7.6.2 Administration Guide 3761
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,761
|
Fortinet Security Fabric
e. Click OK.
3. Ensure that the SAP SDN connector resolves dynamic network services:
a. Go to Policy & Objects > Internet Service Database, select the Network Services tab.
b. Hover over the sap-instance1 and click View Resolved Entries.
A list of resolved internet services is displayed.
Click OK to close the list.
4. Configure a firewall policy with the resolved dynamic network service as the destination:
a. Go to Policy & Objects >Firewall Policy and click Create New.
b. Set the Destination to the sap-instance1 network service.
c. Configure the other settings as needed.
d. Click OK.
To configure an SAP connector in the CLI:
1. Configure the SAP SDN connector:
config system sdn-connector
edit "sap-s4-docker"
set type sap
set verify-certificate disable
set server "20.124.134.109"
FortiOS 7.6.2 Administration Guide 3762
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,762
|
Fortinet Security Fabric
set server-port 50014
set username "a4hadm"
set password ************
next
end
2. Configure a network service associated with the configured SAP SDN connector (available filters are HostName,
InstanceNumber, and ServiceName):
config firewall network-service-dynamic
edit "sap-instance1"
set sdn "sap-s4-docker"
set filter "InstanceNumber=1"
next
end
3. Ensure that the SAP SDN connector resolves dynamic network services:
# diagnose firewall network-service-dynamic list "sap-instance1"
List internet service in kernel(custom):
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=8101-8101
addr ip range(1): 172.17.0.2-172.17.0.2
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=50114-50114
addr ip range(1): 172.17.0.2-172.17.0.2
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=50113-50113
addr ip range(1): 172.17.0.2-172.17.0.2
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=3901-3901
addr ip range(1): 172.17.0.2-172.17.0.2
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=3601-3601
addr ip range(1): 172.17.0.2-172.17.0.2
name=sap-instance1 id=4294770689 reputation=0 (null) singularity=0 flags=0x0 protocol=6
port=3201-3201
addr ip range(1): 172.17.0.2-172.17.0.2
4. Configure a firewall policy with the resolved dynamic network service as the destination:
config firewall policy
edit 2
set name "FGT97-service-dynamic"
set srcintf "port3"
set dstintf "port10"
set action accept
set srcaddr "all"
set internet-service enable
set network-service-dynamic "sap-instance1"
set schedule "always"
set nat enable
next
end
FortiOS 7.6.2 Administration Guide 3763
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,763
|
Fortinet Security Fabric
VMware ESXi SDN connector using server credentials
Dynamic addresses for VMware ESXi and vCenter servers can be automatically updated by using a VMware ESXi
SDN connector, including mapping the following attributes from VMware ESXi and vCenter objects to dynamic address
groups in FortiOS:
l vmid
l host
l name
l uuid
l vmuuid
l vmnetwork
l guestid
l guestname
l annotation
l datacenter
l tag
To configure VMware ESXi SDN connector using the GUI:
1. Configure the VMware ESXi SDN connector:
a. Go to Security Fabric > External Connectors.
b. Click Create New, and select VMware ESXi.
c. Configure as shown, substituting the server IP address, username, and password for your deployment.
The update interval is in seconds. The password cannot contain single or double quotes.
2. Create a dynamic firewall address for the configured VMware ESXi SDN connector:
a. Go to Policy & Objects > Addresses and select Address.
b. Click Create new.
c. Configure the address as shown, selecting the desired filter in the Filter dropdown list. In this example, the
VMware ESXi fabric connector will automatically populate and update IP addresses only for instances that
FortiOS 7.6.2 Administration Guide 3764
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,764
|
Fortinet Security Fabric
belong to VLAN80:
3. Ensure that the VMware ESXi SDN connector resolves dynamic firewall IP addresses:
a. Go to Policy & Objects > Addresses.
b. Hover over the address created in step 2 to see a list of IP addresses for instances that belong to VLAN80 as
configured in step 2:
To configure VMware ESXi SDN connector using CLI commands:
1. Configure the VMware ESXi SDN connector:
config system sdn-connector
edit "vmware1"
set type vmware
set server "172.17.48.222"
set username "example_username"
set password xxxxx
set update-interval 30
next
end
2. Create a dynamic firewall address for the configured VMware ESXi SDN connector with the supported VMware
ESXi filter. In this example, the VMware ESXi SDN connector will automatically populate and update IP addresses
only for instances that belong to the specified VLAN:
config firewall address
edit "vmware-network"
set type dynamic
set sdn "vmware1"
set filter "vmnetwork=VLAN80"
next
end
3. Confirm that the VMware ESXi SDN connector resolves dynamic firewall IP addresses using the configured filter:
config firewall address
edit "vmware-network"
set type dynamic
set sdn "vmware1"
set filter "vmnetwork=VLAN80"
config list
edit "192.168.8.240"
next
end
next
end
FortiOS 7.6.2 Administration Guide 3765
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,765
|
Fortinet Security Fabric
VMware NSX-T Manager SDN connector using NSX-T Manager credentials
This feature provides SDN connector configuration for VMware NSX-T manager. You can import specific groups, or all
groups from the NSX-T Manager.
To configure SDN connector for NSX-T Manager in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Private SDN section, click VMware NSX.
3. Configure the settings and click OK.
To configure SDN connector for NSX-T Manager in the CLI:
config system sdn-connector
edit "nsx_t24"
set type nsx
set server "172.18.64.205"
set username "admin"
set password xxxxxx
next
end
To import a specific group from the NSX-T Manager:
# execute nsx group import nsx_t24 root csf_ns_group
[1] 336914ba-0660-4840-b0f1-9320f5c5ca5e csf_ns_group:
Name:csf_ns_group
Address:1.1.1.0
Address:1.1.1.1
Address:172.16.10.104
Address:172.16.20.104
Address:172.16.30.104
Address:2.2.2.0
Address:2.2.2.2
Address:4.4.4.0
Address:5.5.5.0
FortiOS 7.6.2 Administration Guide 3766
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,766
|
Fortinet Security Fabric
Address:6.6.6.6
Address:7.7.7.7
To import all groups from NSX-T Manager:
# execute nsx group import nsx_t24 root
[1] 663a7686-b9a3-4659-b06f-b45c908349a0 ServiceInsertion_NSGroup:
Name:ServiceInsertion_NSGroup
Address:10.0.0.2
[2] 336914ba-0660-4840-b0f1-9320f5c5ca5e csf_ns_group:
Name:csf_ns_group
Address:1.1.1.0
Address:1.1.1.1
Address:172.16.10.104
Address:172.16.20.104
Address:172.16.30.104
Address:2.2.2.0
Address:2.2.2.2
Address:4.4.4.0
Address:5.5.5.0
Address:6.6.6.6
Address:7.7.7.7
[3] c462ec4d-d526-4ceb-aeb5-3f168cecd89d charlie_test:
Name:charlie_test
Address:1.1.1.1
Address:2.2.2.2
Address:6.6.6.6
Address:7.7.7.7
[4] ff4dcb08-53cf-46bd-bef4-f7aeda9c0ad9 fgt:
Name:fgt
Address:172.16.10.101
Address:172.16.10.102
Address:172.16.20.102
Address:172.16.30.103
[5] 3dd7df0d-2baa-44e0-b88f-bd21a92eb2e5 yongyu_test:
Name:yongyu_test
Address:1.1.1.0
Address:2.2.2.0
Address:4.4.4.0
Address:5.5.5.0
FortiOS 7.6.2 Administration Guide 3767
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,767
|
Fortinet Security Fabric
To view the dynamic firewall IP addresses that are resolved by the SDN connector in the GUI:
1. Go to Policy & Objects > Addresses to view the IP addresses resolved by an SDN connector.
To view the dynamic firewall IP addresses that are resolved by the SDN connector in the CLI:
# show firewall address csf_ns_group
config firewall address
edit "csf_ns_group"
set uuid ee4a2696-bacd-51e9-f828-59457565b880
set type dynamic
set sdn "nsx_t24"
set obj-id "336914ba-0660-4840-b0f1-9320f5c5ca5e"
config list
edit "1.1.1.0"
next
edit "1.1.1.1"
next
edit "172.16.10.104"
next
edit "172.16.20.104"
next
edit "172.16.30.104"
next
edit "2.2.2.0"
next
edit "2.2.2.2"
next
edit "4.4.4.0"
next
edit "5.5.5.0"
next
edit "6.6.6.6"
next
edit "7.7.7.7"
next
FortiOS 7.6.2 Administration Guide 3768
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,768
|
Fortinet Security Fabric
end
next
end
Multiple concurrent SDN connectors
This guide shows how to configure SDN connectors and resolve dynamic firewall addresses through the configured SDN
connector in FortiOS.
FortiOS supports multiple SDN connectors including public connectors (AWS, Azure, GCP, OCI, AliCloud) and private
connectors (Kubernetes, VMware ESXi, VMware NSX, OpenStack, Cisco ACI, Nuage). FortiOS also supports multiple
instances for each type of SDN connector.
This guide uses an Azure SDN connector as an example. The configuration procedure for all supported SDN connectors
is the same. In the following topology, the FortiGate accesses the Azure public cloud through the Internet:
This process consists of the following:
1. Configure the interface.
2. Configure a static route to connect to the Internet.
3. Configure two Azure SDN connectors with different client IDs.
4. Check the configured SDN connectors.
5. Create two firewall addresses.
6. Check the resolved firewall addresses after the update interval.
7. Run diagnose commands.
To configure the interface:
1. In FortiOS, go to Network > Interfaces.
2. Edit port1:
a. From the Role dropdown list, select WAN.
b. In the IP/Network Mask field, enter 10.6.30.4/255.255.255.0 for the interface connected to the Internet.
To configure a static route to connect to the Internet:
1. Go to Network > Static Routes. Click Create New.
2. In the Destination field, enter 0.0.0.0/0.0.0.0.
3. From the Interface dropdown list, select port1.
4. In the Gateway Address field, enter 10.60.30.254.
FortiOS 7.6.2 Administration Guide 3769
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,769
|
Fortinet Security Fabric
To configure two Azure SDN connectors with different client IDs:
1. Go to Security Fabric > External Connectors.
2. Click Create New. Configure the first SDN connector:
a. Select Microsoft Azure.
b. In the Name field, enter azure1.
c. In the Status field, select Enabled.
d. From the Server region dropdown list, select Global.
e. In the Directory ID field, enter the directory ID. In this example, it is 942b80cd-1b14-42a1-8dcf-4b21dece61ba.
f. In the Application ID field, enter the application ID. In this example, it is 14dbd5c5-307e-4ea4-8133-
68738141feb1.
g. In the Client secret field, enter the client secret.
h. Leave the Resource path disabled.
i. Click OK.
3. Click Create New. Configure the second SDN connector:
a. Select Microsoft Azure.
b. In the Name field, enter azure2.
c. In the Status field, select Enabled.
d. From the Server region dropdown list, select Global.
e. In the Directory ID field, enter the directory ID. In this example, it is 942b80cd-1b14-42a1-8dcf-4b21dece61ba.
f. In the Application ID field, enter the application ID. In this example, it is 3baf0a6c-44ff-4f94-b292-
07f7a2c36be6.
g. In the Client secret field, enter the client secret.
h. Leave the Resource path disabled.
FortiOS 7.6.2 Administration Guide 3770
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,770
|
Fortinet Security Fabric
i. Click OK.
To check the configured SDN connectors:
1. Go to Security Fabric > External Connectors.
2. Click the Refresh icon in the upper right corner of each configured SDN connector. A green up arrow appears in the
lower right corner, meaning that both SDN connectors are connected to the Azure cloud using different client IDs.
To create two firewall addresses:
This process creates two SDN connector firewall addresses to associate with the configured SDN connectors.
1. Go to Policy & Objects > Addresses and select Address.
2. Click Create new. Configure the first SDN connector firewall address:
a. In the Name field, enter azure-address-1.
b. From the Type dropdown list, select Dynamic.
c. From the Sub Type dropdown list, select Fabric Connector address.
d. From the SDN Connector dropdown list, select azure1.
e. For SDN address type, select Private.
f. From the Filter dropdown list, select the desired filter.
g. For Interface, select any.
FortiOS 7.6.2 Administration Guide 3771
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,771
|
Fortinet Security Fabric
h. Click OK.
3. Click Create new. Configure the second SDN connector firewall address:
a. In the Name field, enter azure-address-1.
b. From the Type dropdown list, select Dynamic.
c. From the Sub Type dropdown list, select Fabric Connector address.
d. From the SDN Connector dropdown list, select azure2.
e. For SDN address type, select Private.
f. From the Filter dropdown list, select the desired filter.
g. For Interface, select any.
h. Click OK.
To check the resolved firewall addresses after the update interval:
By default, the update interval is 60 seconds.
1. Go to Policy & Objects > Addresses and select Address.
2. Hover over the created addresses. The firewall address that the configured SDN connectors resolved display.
To run diagnose commands:
Run the show sdn connector status command. Both SDN connectors should appear with a status of connected.
Run the diagnose debug application azd -1 command. The output should look like the following:
Level2-downstream-D # diagnose debug application azd -1
...
azd sdn connector azure1 start updating IP addresses
azd checking firewall address object azure-address-1, vd 0
IP address change, new list:
10.18.0.4
...
To restart the Azure SDN connector daemon, run the diagnose test application azd 99 command.
FortiOS 7.6.2 Administration Guide 3772
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,772
|
Fortinet Security Fabric
Filter lookup in SDN connectors
When configuring dynamic address mappings for filters in SDN connectors for Azure, GCP, OpenStack, Kubernetes,
and AliCloud, FortiGate can query the filters automatically.
To use the filter lookup:
1. Navigate to Policy & Objects > Addresses.
2. Create or edit an SDN connector type dynamic IP address.
Supported SDN connector types include: AWS, Azure, GCP, OpenStack, Kubernetes, and AliCloud. The example
below is for an Azure SDN connector.
3. In the address Filter field, you can perform the following actions:
l List all available filters.
l Search the available filters.
FortiOS 7.6.2 Administration Guide 3773
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,773
|
Fortinet Security Fabric
l Create custom filters.
FortiOS 7.6.2 Administration Guide 3774
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,774
|
Fortinet Security Fabric
l Set filter logic [and|or].
Support for wildcard SDN connectors in filter configurations
Wildcards are supported for SDN connectors when configuring dynamic address filters.
The following SDN connector types are currently supported:
l AWS
l Azure
l Google Cloud Platform
l Kubernetes
l OpenStack
l Oracle Cloud Infrastructure
l VMware ESXi
To configure a dynamic address filter for AWS in the GUI:
1. Create the SDN connector:
a. Go to Security Fabric > External Connectors.
b. Click Create New.
c. In the Public SDN section, click Amazon Web Services (AWS).
d. Configure the settings as needed.
e. Click OK.
2. Create the dynamic firewall address:
a. Go to Policy & Objects > Addresses and select Address.
b. Click Create new.
c. Enter a name for the address, then configure the following settings:
l Set Type to Dynamic.
l Set Sub Type to Fabric Connector Address.
l Set SDN Connector to aws1.
l Set SDN address type to Private.
FortiOS 7.6.2 Administration Guide 3775
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,775
|
Fortinet Security Fabric
l For Filter, click Create, enter Tag.Name=aws*, the click OK.
d. Click OK.
3. In the address table, hover over the address to view what IPs it resolves to.
4. In AWS, verify to confirm the IP addresses match.
To configure a dynamic address filter for AWS in the CLI:
1. Configure the SDN connector:
config firewall address
edit "aws-address-1"
set type dynamic
set sdn "aws1"
set filter "Tag.Name=aws*"
set sdn-addr-type public
next
end
2. Create the dynamic firewall address and verify where the IP addresses resolve to:
config firewall address
edit "aws-address-1"
set type dynamic
set sdn "aws1"
set filter "Tag.Name=aws*"
set sdn-addr-type public
config list
edit "18.234.167.123"
FortiOS 7.6.2 Administration Guide 3776
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,776
|
Fortinet Security Fabric
next
edit "3.81.41.167"
next
edit "52.87.157.127"
next
end
next
end
3. In AWS, verify that the IP addresses match.
Endpoint/Identity connectors
SSO fabric connectors integrate SSO authentication into the network. This allows users to enter their credentials only
once, and have those credentials reused when accessing other network resources through the FortiGate.
The following fabric connectors are available:
l Fortinet single sign-on agent on page 3777
l Poll Active Directory server on page 3778
l Symantec endpoint connector on page 3779
l RADIUS single sign-on agent on page 3786
l Exchange Server connector on page 3789
Fortinet single sign-on agent
To create an FSSO agent connector in the GUI:
1. Go to Security Fabric > External Connectors.
2. Click Create New.
FortiOS 7.6.2 Administration Guide 3777
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,777
|
Fortinet Security Fabric
3. In the Endpoint/Identity section, click FSSO Agent on Windows AD.
4. Fill in the Name, and Primary FSSO Agent server IP address or name and Password.
5. Optionally, add more FSSO agents by clicking the plus icon.
6. Optionally, enable Trusted SSL certificate and select or import a certificate.
7. Select the User group source:
l Collector Agent: User groups will be pushed to the FortiGate from the collector agent. Click Apply & Refresh to
fetch group filters from the collector agent.
l Local: User groups will be specified in the FortiGate unit's configuration. Select the LDAP server from the list,
then click Edit to select the Users, Groups, and Organizational Units. Optionally, enable Proactively retrieve
from LDAP server and configure the Search filter and Interval.
8. Click OK.
Poll Active Directory server
The FortiGate unit can authenticate users and allow them network access based on groups membership in Windows
Active Directory (AD).
To create an AD server connector in the GUI:
1. Go to Security Fabric > External Connectors.
2. Click Create New.
FortiOS 7.6.2 Administration Guide 3778
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,778
|
Fortinet Security Fabric
3. In the Endpoint/Identity section, click Poll Active Directory Server.
4. Fill in the Server IP/Name, User, and Password for the AD server.
5. Select the LDAP server from the list.
6. If necessary, disable Enable Polling. This can be used to temporarily stop the FortiGate from polling security event
logs on the Windows logon server, for troubleshooting purposes.
7. Click OK.
Symantec endpoint connector
With the Fabric connector for Symantec Endpoint Protection Manager (SEPM), you can use the client IP information
from SEPM to assign to dynamic IP addresses on FortiOS.
When communication between FortiGate and SEPM is established, FortiGate polls every minute for updates via TLS
over port 8446. You can use the CLI to change the default one minute polling interval.
For example, you can create a dynamic Fabric Connector IP address subtype and use it in firewall policies as the source
address. The dynamic IP address contains all IP addresses sent by SEPM.
This example shows a dynamic IP address with SEPM and one client PC managed by SEPM using FortiGate as the
default gateway.
To configure SEPM on a managed client PC:
1. In SEPM, create client packages for client hosts and group them into SEPM groups.
You can install packages locally on clients or download them directly from SEPM.
FortiOS 7.6.2 Administration Guide 3779
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,779
|
Fortinet Security Fabric
2. When a package is installed on the client host, the host is considered managed by SEPM.
Even if the host has multiple interfaces, only one IP per host is displayed.
To configure Symantec endpoint connector on FortiGate in the GUI:
1. Go to Security Fabric > External Connectors and click Create New:
a. In the Endpoint/Identity section, click Symantec Endpoint Protection.
b. Fill in the Name, and set the Status and Update Interval.
c. Set Server to the SEPM IP address.
d. Enter the Username and Password for the server.
e. To limit the domain or group that is monitored, enter them in the requisite fields.
f. Click OK.
When the connection is established, you can see a green up arrow in the bottom right of the card. You might
need to refresh your browser to see the established connection.
2. Go to Policy & Objects > Addresses and select Address.
3. Click Create new:
a. Fill in the address Name.
b. Set Type to Dynamic.
c. Set Sub Type to Fabric Connector Address.
FortiOS 7.6.2 Administration Guide 3780
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,780
|
Fortinet Security Fabric
d. Set SDN Connector to the fabric connector that you just created.
e. Add Filters as needed.
f. Click OK.
Filter options are only available for active computers that are configured and registered
in SEPM. Free-form filters can be created manually by clicking Create and entering the
filter, in the format: filter_type=value.
Possible manual filter types are: GroupName, GroupID, ComputerName,
ComputerUUID, and OSName. For example: GroupName=MyGroup.
4. Go to Policy & Objects > Addresses and hover the cursor over the name of the new address to see the resolved IP
addresses of the host.
FortiOS 7.6.2 Administration Guide 3781
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,781
|
Fortinet Security Fabric
5. Go to Policy & Objects > Firewall Policy, click Create New, and add a policy that uses the dynamic IP address.
To verify the configuration:
1. On the client PC, check that it is managed by SEPM to access the Internet.
FortiOS 7.6.2 Administration Guide 3782
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,782
|
Fortinet Security Fabric
2. On the FortiGate, you can check in Dashboard > FortiView Sources and Log & Report > Forward Traffic.
Because this traffic is not authenticated traffic but is based on source IP address only, it is
not shown in the GUI firewall monitor or in the diagnose firewall auth list CLI
command.
To configure Symantec endpoint connector on FortiGate in the CLI:
1. Create the fabric connector:
config system sdn-connector
edit "sepm-217"
set type sepm
set server "172.18.60.217"
set username "admin"
set password *********
set status enable
next
end
2. Create the dynamic IP address:
config firewall address
edit "sepm-ip"
set type dynamic
set sdn "sepm-217"
set filter "ComputerName=win10-1"
config list
edit "10.1.100.187"
next
edit "10.6.30.187"
next
FortiOS 7.6.2 Administration Guide 3783
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,783
|
Fortinet Security Fabric
edit "172.16.200.187"
next
end
next
end
3. Add the dynamic IP address to the firewall policy:
config firewall policy
edit 1
set name "pol1"
set srcintf "port2"
set dstintf "port1"
set srcaddr "sepm-ip"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
set utm-status enable
set ssl-ssh-profile "certificate-inspection"
set av-profile "default"
set logtraffic all
set fsso disable
set nat enable
next
end
To troubleshoot Symantec SD connector in the CLI:
# diagnose debug application sepmd -1
Output is sent every minute (default). All IPv4 learned from SEPM. IPv6 also sent but not
yet supported.
2019-09-09 12:01:09 sepmd sdn connector sepm-217 start updating IP addresses
2019-09-09 12:01:09 sepmd checking firewall address object sepm-ip, vd 0
2019-09-09 12:01:09 sepmd sdn connector sepm-217 finish updating IP addresses
2019-09-09 12:01:09 sepmd reap child pid: 18079
2019-09-09 12:02:09 sepmd sdn connector sepm-217 prepare to update
2019-09-09 12:02:09 sepmd sdn connector sepm-217 start updating
2019-09-09 12:02:09 sepm-217 sdn connector will retrieve token after 9526 secs
2019-09-09 12:02:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 172.16.200.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:02:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 10.6.30.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:02:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 10.1.100.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:02:09 2001:0000:0000:0000:0000:0000:0000:0187 is not in IPv4 presentation
FortiOS 7.6.2 Administration Guide 3784
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,784
|
Fortinet Security Fabric
format
2019-09-09 12:02:09 sepmd sdn connector sepm-217 start updating IP addresses
2019-09-09 12:02:09 sepmd checking firewall address object sepm-ip, vd 0
2019-09-09 12:02:09 sepmd sdn connector sepm-217 finish updating IP addresses
2019-09-09 12:02:09 sepmd reap child pid: 18089
2019-09-09 12:03:09 sepmd sdn connector sepm-217 prepare to update
2019-09-09 12:03:09 sepmd sdn connector sepm-217 start updating
2019-09-09 12:03:09 sepm-217 sdn connector will retrieve token after 9466 secs
2019-09-09 12:03:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 172.16.200.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:03:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 10.6.30.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:03:09 sym_new_ip_addr ComputerName win10-1
ComputerUuid AC894D56-BD86-A786-7DDB-7FD98B718AE0, OsName Windows 10
IP 10.1.100.187
GroupName My Company\Windows-desktops, GroupId E61FDEA2AC10C80E46D0B31BB58D7CB3
DomainName Default, DomainId 6C507580AC10C80E5F3CAED5B1711A8E
2019-09-09 12:03:09 2001:0000:0000:0000:0000:0000:0000:0187 is not in IPv4 presentation
format
To list the SEPM daemon SDN connectors:
# diagnose test application sepmd 1
sepm SDN connector list:
name: sepm-217, status: enabled, updater_interval: 60
To list the SEPM daemon SDN filters:
# diagnose test application sepmd 2
sepm SDN connector sepm-217 filter list:
name: sepm-ip, vd 0, filter 'ComputerName=win10-1'
Using a self-signed certificate
Users can explicitly specify a certificate or series of certificates for FortiGate to trust during the connection to the
Symantec Endpoint Protection Manager (SEPM) server. For example, a self-signed certificate without proper SAN.
The following new options are added in SEPM sdn-connector:
Option Description
server-cert Trust servers that contain this certificate only.
server-ca-cert Trust only those servers whose certificate is directly or indirectly signed by this
certificate.
FortiOS 7.6.2 Administration Guide 3785
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,785
|
Fortinet Security Fabric
When these options are enabled, only the specified certificate or series of certificates will be allowed for SEPM server
connection ensuring some level of security by blocking off all unspecified certificates.
To specify SEPM certificates:
config system sdn-connector
edit "sepm-217"
set type sepm
set server "172.18.60.217"
set username "admin"
set password *********
set status enable
set server-cert "REMOTE_Cert_1”
set server-ca-cert "REMOTE_Cert_2”
next
end
The server-cert and server-ca-cert options are independent of each other and can be
set separately. However, when both options are set, both constraints are applied.
RADIUS single sign-on agent
With RADIUS single sign-on (RSSO), a FortiGate can authenticate users who have authenticated on a remote RADIUS
server. Based on which user group the user belongs to, the security policy applies the appropriate UTM profiles.
The FortiGate does not interact with the remote RADIUS server; it only monitors RADIUS accounting records that the
server forwards (originating from the RADIUS client). These records include the user IP address and user group. The
remote RADIUS server sends the following accounting messages to the FortiGate:
Message Action
Start If the information in the start message matches the RSSO configuration on the
FortiGate, the user is added to the local list of authenticated firewall users.
Stop The user is removed from the local list of authenticated firewall users because the
user session no longer exists on the RADIUS server.
You can configure an RSSO agent connector using the FortiOS GUI; however, in most cases, you will need to use the
CLI. There are some default options you may need to modify that can only be done in the CLI.
config user radius
edit <name>
set rsso enable
set rsso-radius-response enable
set rsso-secret <password>
set rsso-endpoint-attribute <attribute>
set sso-attribute <attribute>
set delimiter {plus | comma}
next
end
FortiOS 7.6.2 Administration Guide 3786
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,786
|
Fortinet Security Fabric
To configure an RSSO agent connector:
1. Create the new connector:
a. Go to Security Fabric > External Connectors.
b. Click Create New.
c. In the Endpoint/Identity section, click RADIUS Single Sign-On Agent. The New Fabric Connector pane opens.
d. Enter the connector name.
e. Enable Use RADIUS Shared Secret.
The value entered in Use RADIUS Shared Secret must be identical to what the remote
RADIUS server uses to authenticate when it sends RADIUS accounting messages to
the FortiGate.
f. Enable Send RADIUS Responses.
You should enable Send RADIUS Responses because some RADIUS servers
continue to send the same RADIUS accounting message several times if there is no
response.
g. Click OK.
2. Edit the network interface:
a. Go to Network > Interfaces.
b. Double-click the interface that will receive the RADIUS accounting messages. The Edit Interface pane opens.
c. In the Administrative Access section, select the RADIUS Accounting checkbox. This will open listening for port
1813 on this interface. The FortiGate will then be ready to receive RADIUS accounting messages.
d. Click OK.
3. Create a local RSSO user group:
a. Go to User & Authentication > User Groups.
b. Click Create New.
c. Enter the group name.
d. For the Type field, click RADIUS Single-Sign-ON (RSSO).
e. Enter a value for RADIUS Attribute Value.
This value by default is the class attribute. The FortiGate uses the content of this attribute in RADIUS
accounting start messages to map a user to a FortiGate group, which then can be used in firewall policies.
In this example configuration, the FortiGate will only add a remote RADIUS user to the local firewall user list if
the class attribute in the RADIUS accounting START message contains the value group1.
FortiOS 7.6.2 Administration Guide 3787
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,787
|
Fortinet Security Fabric
If your users are in multiple groups, you will need to add multiple local RSSO user
group.
If the RADIUS attribute value used to map users to a local RSSO group is different than
the RADIUS attribute in the RADIUS accounting messages forwarded by the server,
you must change it in the CLI.
f. Click OK.
4. Edit the local RSSO agent to modify default options using the CLI.
For example, the default value for rsso-endpoint-attribute might work in common remote access scenarios
where users are identified by their unique Calling-Station-Id, but in other scenarios the user name might be in
a different attribute.
config user radius
edit "Local RSSO Agent"
set rsso-endpoint-attribute <attribute>
set sso-attribute <attribute>
next
end
5. Add the local RSSO user group to a firewall policy.
Verifying the RSSO configuration
Verification requires a working remote RADIUS server configured for RADIUS accounting forwarding and wireless or
wired clients that use RADIUS for user authentication.
For a quick test, you can use one of the publicly available RADIUS test tools to send RADIUS accounting start and stop
messages to the FortiGate. You can also use radclient.
To verify the RSSO configuration:
1. In radclient, enter the RADIUS attributes. These attributes are then executed with the FortiGate IP parameters
(sends accounting messages to port 1813) and shared password you configured. -x is used for verbose output:
root@ControlPC:~# echo "Acct-Status-Type =Start,Framed-Ip-Address=10.1.100.185,UserName=test2,Acct-Session-Id=0211a4ef,Class=group1,Calling-Station-Id=00-0c-29-44-BE-B8" |
radclient -x 10.1.100.1 acct 123456
Sending Accounting-Request of id 180 to 10.1.100.1 port 1813
Acct-Status-Type = Start
Framed-IP-Address = 10.1.100.185
User-Name = "test2"
Acct-Session-Id = "0211a4ef"
Class = 0x67726f757031
FortiOS 7.6.2 Administration Guide 3788
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,788
|
Fortinet Security Fabric
Calling-Station-Id = "00-0c-29-44-BE-B8"
rad_recv: Accounting-Response packet from host 10.1.100.1 port 1813, id=180, length=20
root@ControlPC:~#
2. Verify that the user is in the local firewall user list with the correct type (rsso) and local firewall group (rssogroup1):
# diagnose firewall auth l
10.1.100.185, test2
type: rsso, id: 0, duration: 5, idled: 5
flag(10): radius
server: vdom1
packets: in 0 out 0, bytes: in 0 out 0
group_id: 3
group_name: rsso-group-1
----- 1 listed, 0 filtered ------
Exchange Server connector
FortiGate can collect additional information about authenticated users from corporate Microsoft Exchange Servers. After
a user logs in, the additional information can be viewed in various parts of the GUI.
The Exchange connector must be mapped to the LDAP server that is used for authentication.
The following attributes are retrieved:
USER_INFO_FULL_NAME USER_INFO_COMPANY USER_INFO_CITY
USER_INFO_FIRST_NAME USER_INFO_DEPARTMENT USER_INFO_STATE
USER_INFO_LAST_NAME USER_INFO_GROUP USER_INFO_POSTAL_CODE
USER_INFO_LOGON_NAME USER_INFO_TITLE USER_INFO_COUNTRY
USER_INFO_TELEPHONE USER_INFO_MANAGER USER_INFO_ACCOUNT_EXPIRES
USER_INFO_EMAIL USER_INFO_STREET
USER_INFO_USER_PHOTO USER_INFO_POST_OFFICE_BOX
Kerberos Key Distribution Center (KDC) automatic discovery is enabled by default. The FortiGate must be able to use
DNS to resolve the KDC IP addresses, otherwise the FortiGate will be unable to retrieve additional user information from
the Exchange Server.
KDC automatic discovery can be disabled, and one or more internal IP addresses that the FortiGate can reach can be
configured for KDC.
The Override server IP address is enabled when the IP address of the Exchange server cannot be resolved by DNS and
must be entered manually.
To configure an Exchange connector in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Endpoint/Identity section, click Exchange Server.
3. Set Name to exchange140.
4. Set Exchange account to Administrator@W2K8-SERV1.FORTINET-FSSO.COM.
FortiOS 7.6.2 Administration Guide 3789
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,789
|
Fortinet Security Fabric
Administrator is the username, W2K8-SERV1 is the exchange server name, and FORTINET-FSSO.COM is the
domain name.
5. Set Password to the password.
6. Enable Override server IP address and set it to 10.1.100.140.
7. Ensure that Auto-discover KDC is enabled.
If Auto-discover KDC is disabled, one or more KDC IP addresses can be manually entered.
8. Click OK.
To link the connector to the LDAP server in the GUI:
1. Go to User & Authentication > LDAP Servers.
2. Edit an existing LDAP server, or click Create New to create a new one.
3. Enable Exchange server, and select the connector from the list.
4. Configure the remaining settings as required.
5. Click OK.
To configure an Exchange connector with automatic KDC discovery in the CLI:
config user exchange
edit "exchange140"
set server-name "W2K8-SERV1"
set domain-name "FORTINET-FSSO.COM"
set username "Administrator"
FortiOS 7.6.2 Administration Guide 3790
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,790
|
Fortinet Security Fabric
set password **********
set ip 10.1.100.140
set auto-discover-kdc enable
next
end
To link the connector to the LDAP server in the CLI:
config user ldap
edit "openldap"
set server "172.18.60.213"
set cnid "cn"
set dn "dc=fortinet-fsso,dc=com"
set type regular
set username "cn=Manager,dc=fortinet-fsso,dc=com"
set password **********
set group-member-check group-object
set group-object-filter "(&(objectclass=groupofnames)(member=*))"
set member-attr "member"
set user-info-exchange-server "exchange140"
next
end
Verification
To verify that KDC auto-discovery is working:
# diagnose wad debug enable category all
# diagnose wad debug enable level verbose
# diagnose debug enable
# diagnose wad user exchange test-auto-discover
wad_diag_session_acceptor(3115): diag socket 20 accepted.
__wad_fmem_open(557): fmem=0x12490bd8, fmem_name='cmem 9188 bucket', elm_sz=9188, block_
sz=73728, overhead=0, type=advanced
Starting auto-discover test for all configured user-exchanges.
[NOTE]: If any errors are returned, try manually configuring IPs for the reported errors.
wad_rpc_nspi_test_autodiscover_kdc(1835): Starting DNS SRV request for srv(0x7f938e052050)
query(_kerberos._udp.FORTINET-FSSO.COM)
wad_dns_send_srv_query(705): 1:0: sending DNS SRV request for remote peer _kerberos._
udp.FORTINET-FSSO.COM id=0
1: DNS response received for remote host _kerberos._udp.FORTINET-FSSO.COM req-id=0
wad_dns_parse_srv_resp(409): _kerberos._udp.FORTINET-FSSO.COM: resp_type(SUCCESS)
srv[0]: name(w2k12-serv1.fortinet-fsso.com) port(88) priority(0) weight(100)
addr[0]: 10.1.100.131
addr[1]: 10.6.30.131
addr[2]: 172.16.200.131
addr[3]: 2003::131
addr[4]: 2001::131
srv[1]: name(fsso-core-DC.Fortinet-FSSO.COM) port(88) priority(0) weight(100)
addr[0]: 10.6.30.16
addr[1]: 172.16.200.16
srv[2]: name(w2k12-serv1.Fortinet-FSSO.COM) port(88) priority(0) weight(100)
addr[0]: 10.1.100.131
FortiOS 7.6.2 Administration Guide 3791
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,791
|
Fortinet Security Fabric
addr[1]: 172.16.200.131
addr[2]: 10.6.30.131
addr[3]: 2001::131
addr[4]: 2003::131
wad_rpc_nspi_dns_on_discover_kdc_done(1787): Received response for DNS autodiscover req
(0x7f938dfe8050) query(_kerberos._udp.FORTINET-FSSO.COM) n_rsp(3)
Completed auto-discover test for all configured user-exchanges.
To check the collected information after the user has been authenticated:
1. In the GUI, go to Dashboard > Assets & Identities, expand the Firewall Users widget, and hover over the user name.
2. In the CLI, run the following diagnose command:
# diagnose wad user info 20 test1
'username' = 'test1'
'sourceip' = '10.1.100.185'
'vdom' = 'root'
'cn' = 'test1'
'givenName' = 'test1'
'sn' = 'test101'
'userPrincipalName' = 'test1@Fortinet-FSSO.COM'
'telephoneNumber' = '604-123456'
'mail' = 'test1@fortinet-fsso.com'
'thumbnailPhoto' = '/tmp/wad/user_info/76665fff62ffffffffffffffffffff75ff68fffffffffa'
'company' = 'Fortinet'
'department' = 'Release QA'
'memberOf' = 'CN=group321,OU=Testing,DC=Fortinet-FSSO,DC=COM'
'memberOf' = 'CN=g1,OU=Testing,DC=Fortinet-FSSO,DC=COM'
'memberOf' = 'CN=group21,OU=Testing,DC=Fortinet-FSSO,DC=COM'
'memberOf' = 'CN=group1,OU=Testing,DC=Fortinet-FSSO,DC=COM'
'manager' = 'CN=test6,OU=Testing,DC=Fortinet-FSSO,DC=COM'
'streetAddress' = 'One Backend Street 1901'
'l' = 'Burnaby'
'st' = 'BC'
'postalCode' = '4711'
'co' = 'Canada'
'accountExpires' = '9223372036854
If the results are not as expected, verify what information FortiGate can collect from the Exchanger Server:
# diagnose test application wad 2500
# diagnose test application wad 162
Threat feeds
The FortiGate dynamically imports an external list from an HTTP/HTTPS server in the form of a plain text file. The
imported list is then available as a threat feed, which can be used to enforce special security requirements, such as longterm policies to always allow or block access to certain websites, or short-term requirements to block access to known
compromised locations. The threat feeds are dynamically synchronized and are updated periodically so that any
changes are immediately imported by FortiOS.
FortiOS 7.6.2 Administration Guide 3792
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,792
|
Fortinet Security Fabric
If the FortiGate loses connectivity with the external server, the threat feed will continue to
function despite the Connection Status error or reboot. However, the threat feed will not be
updated and no new entries will be added until the connection is re-established.
FortiOS also supports STIX/TAXII format. See STIX format for external threat feeds on page 3820 for more information.
There are five types of threat feeds:
FortiGuard
Category
The FortiGate dynamically imports a text file from an external server, which contains one URL
per line. See FortiGuard category threat feed on page 3803 for more information.
IP Address The FortiGate dynamically imports a text file from an external server, which contains one IP/IP
range/subnet per line. See IP address threat feed on page 3807 for more information.
Domain Name The FortiGate dynamically imports a text file from an external server, which contains one
domain per line. Simple wildcards are supported. See Domain name threat feed on page
3810 for more information.
MAC Address The FortiGate dynamically imports a text file from an external server, which contains one MAC
address, MAC range, or MAC OUI per line. See MAC address threat feed on page 3812 for
more information.
Malware Hash The FortiGate dynamically imports a text file from an external server, which contains one hash
per line in the format <hex hash> [optional hash description]. Each line supports
MD5, SHA1, and SHA256 hex hashes. See Malware hash threat feed on page 3814 for more
information.
Additionally, the EMS threat feed is integrated with FortiClient EMS, but it is not configured in the same way as the
preceding feeds:
EMS Threat Feed A FortiGate can pull malware threat feeds from FortiClient EMS, which in turn receives
malware hashes detected by FortiClient. The malware hash can be used in an antivirus profile
when AV scanning is enabled with block or monitor actions. See Malware threat feed from
EMS on page 1801 for an example.
FortiManager can host threat feeds. See External resources in the FortiManager Administration Guide.
External resources file format
File format requirements for a HTTP/HTTPS external resources file:
l The file is in plain text format with each URL list, IP address, domain name, or malware hash occupying one line.
Comments can be added by using the number sign, for example: # This is a test.
l The file is limited to a maximum size and entry limit, based on the device model; see External resource entry limit on
page 3795.
l The external resources update period can be set to 1 minute, hourly, daily, weekly, or monthly (43200 min, 30 days).
l The external resources type as category (URL list) and domain (domain name list) share the category number
range 192 to 221 (total of 30 categories).
l There is no duplicated entry validation for the external resources file (entry inside each file or inside different files).
FortiOS 7.6.2 Administration Guide 3793
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,793
|
Fortinet Security Fabric
l If the number of entries exceed the limit, a warning is displayed. Additional entries beyond the threshold will not be
loaded.
For URL list (type = category):
l The scheme is optional, and will be truncated if found; https:// and http:// are not required.
l Wildcards are allowed at the beginning or end or the URL, for example: *.domain.com or domain.com.*.
l IDN and UTF encoding URL are supported .
l The URL can be an IPv4 or IPv6 address. An IPv6 URL must be in [ ] format.
For IP address list (type = address):
l The IP address can be a single IP address, subnet address, or address range. For example, 192.168.1.1,
192.168.10.0/24, or 192.168.100.1-192.168.100.254.
l The address can be an IPv4 or IPv6 address. An IPv6 address does not need to be in [ ] format.
For domain name list (type = domain):
l Simple wildcards are allowed in the domain name list, for example: *.test.com.
l IDN (international domain name) is supported.
For MAC address list (type = mac-address):
l The MAC address can be a single MAC address, MAC OUI, or MAC range. For
example, 01:01:01:01:01:01, 8c:aa:b5, or 01:01:01:01:01:01-01:01:02:50:20:ff.
l The hexadecimal digits in MAC address must only be separated by colons.
For malware hash list (type = malware):
l The malware hash list follows a strict format in order for its contents to be valid. Malware hash signature entries
must be separated into each line. A valid signature must follow this format:
# MD5 Entry with hash description
aa67243f746e5d76f68ec809355ec234 md5_sample1
# SHA1 Entry with hash description
a57983cb39e25ab80d7d3dc05695dd0ee0e49766 sha1_sample2
# SHA256 Entry with hash description
ae9bc0b4c5639d977d720e4271da06b50f7c60d1e2070e9c75cc59ab30e49379 sha256_sample1
# Entry without hash description
0289b0d967cb7b1fb1451339c7b9818a621903090e0020366ab415c549212521
# Invalid entries
7688499dc71b932feb126347289c0b8a_md5_sample2
7614e98badca10b5e2d08f8664c519b7a906fbd5180ea5d04a82fce9796a4b87sha256_sample3
To determine the external resource table size limit for your device:
# print tablesize
...
system.external-resource: 0 256 512 0
...
In this example, a FortiGate 60E has a global limit of 512 and a per-VDOM limit of 256. A FortiGate 60E can configure up
to 512 feeds. The total number of feeds is limited by the available memory on the device.
FortiOS 7.6.2 Administration Guide 3794
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,794
|
Fortinet Security Fabric
External resource entry limit
The external resource entry limit is global, and file size restrictions change according to the device model. If VDOMs are
enabled, global entries are counted first, then VDOM entries in alphabetical order based on the VDOMs' names.
If more than the maximum number of entries are added, the most recently added entries are truncated unless the order
is manually changed. The entry order can be changed using the move CLI command. For example:
config system external-resource
move "entry2" before "entry1"
end
The maximum number of each type of entry and the file size limit for each model range are as follows:
High-End (Data Center) Mid-Range (Campus) Entry-Level (Branch)
Category 2 000 000 300 000 150 000
IP address 300 000 300 000 300 000
Domain 5 000 000 3 000 000 1 000 000
MAC 1 000 000 1 000 000 1 000 000
File size limit (MB) 128 64 32
For example, a FortiGate 601E, a mid-range device, is configured as follows:
l global VDOM: One threat feed, g-category-push, with one entry.
l root VDOM: One threat feed, r-category-push, with one entry.
l vd1 VDOM: Two threat feeds, v-category-300000 with 300000 entries first, and v-category-push with one entry
second.
l vd2 VDOM: One threat feed, z-category-push, with one entry.
There are more than 300000 entries, so some of the entries will be truncated.
l The global VDOM is counted first, so its entry is kept:
FGT (global)# diagnose sys external-resource stats
name: g-category-push; uuid_idx: 606; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 1; total in count file: 1;
l The root VDOM is alphabetically before the vd1 and vd2 VDOMs, so its entry is kept:
FGT (root)# diagnose sys external-resource stats
name: g-category-push; uuid_idx: 606; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 1; total in count file: 1;
name: r-category-push; uuid_idx: 746; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 1; total in count file: 1;
l The vd1 VDOM is next alphabetically. The maximum number of entries is 300000, so 299998 entries from the
v-category-3000000 threat feed are kept, and no entries from the v-category-push feed:
FGT (vd1)# diagnose sys external-resource stats
name: g-category-push; uuid_idx: 606; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 1; total in count file: 1;
name: v-category-300000; uuid_idx: 863; type: category; update_method: feed; truncated
total lines: 300000; valid lines: 299999; error lines: 1; used: no; buildable: 299998;
FortiOS 7.6.2 Administration Guide 3795
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,795
|
Fortinet Security Fabric
total in count file: 300000;
name: v-category-push; uuid_idx: 868; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: yes; buildable: 0; total in count file: 1;
l The vd2 VDOM is last alphabetically and the maximum number of entries has already been reached, so all of its
entries are truncated:
FGT (vd2)# diagnose sys external-resource stats
name: g-category-push; uuid_idx: 606; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 1; total in count file: 1;
name: z-category-push; uuid_idx: 989; type: category; update_method: push; total lines:
1; valid lines: 1; error lines: 0; used: no; buildable: 0; total in count file: 1;
Configuring a threat feed
A threat feed can be configured on the Security Fabric > External Connectors page. After clicking Create New, there are
four threat feed options available: FortiGuard Category, IP Address, Domain Name, and Malware Hash. When
configuring the threat feed settings, the Update method can be either a pull method (External Feed) or a push method
(PUSH API).
This topic includes three example threat feed configurations:
l Configuring a threat feed with an external feed update
l Configuring threat feed authentication
l Configuring a threat feed with a push API update
When multi-VDOM mode is enabled, threat feed external connectors can be defined in the
global VDOM or within a VDOM. See Threat feed connectors per VDOM on page 3817 for
example configurations.
Configuring a threat feed with an external feed update
The threat feed will periodically fetch entries from the URI using HTTP or HTTPS.
To configure the threat feed in the GUI:
1. Go Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, select the required feed type.
FortiOS 7.6.2 Administration Guide 3796
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,796
|
Fortinet Security Fabric
3. Configure the connector settings:
Status Enable/disable the connector.
Name Enter a name for the threat feed connector.
Update method Select External Feed.
URL of external resource Enter the link to the external resource file. HTTP, HTTPS, and STIX protocols
are supported.
HTTP basic authentication Enable/disable basic HTTP authentication. When enabled, enter the
username and password in the requisite fields. See Configuring threat feed
authentication for more information.
Refresh Rate The time interval to refresh the external resource, in minutes (1 - 43200,
default = 5).
The applicable threat feed will be triggered to refresh between 0 minutes and
the configured value. When the refresh is triggered, if another task is being
processed be the schedule worker, the refresh task will be added to the queue.
Comments Optionally, enter a description of the connector.
4. Click OK.
To configure the threat feed in the CLI:
config system external-resource
edit <name>
set status {enable | disable}
set type {category | address | domain | malware}
set category <integer, 192-221>
set update-method {feed | push}
set username <string>
set password <string>
set comments <string>
*set resource <resource-uri>
set user-agent <string>
set server-identity-check {none | basic | full}
set refresh-rate <integer>
set source-ip <ip address>
set interface-select-method {auto | sdwan | specify}
next
end
The parameter marked with an asterisk (*) is mandatory and must be filled in. The category parameter must be set
when the type is either category or domain. Other parameters have either default values or are optional.
To improve the security of the connection, it is recommended to enable server certificate validation (serveridentity-check) either in basic or full mode.
Configuring threat feed authentication
Threat feed external connectors support username and password authentication.
FortiOS 7.6.2 Administration Guide 3797
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,797
|
Fortinet Security Fabric
The HTTP basic authentication field is only visible when the Update method is set to External
Feed.
To enable username and password authentication in a threat feed connector:
1. Go Security Fabric > External Connectors.
2. Click Create New, or edit an existing threat feed connector.
3. Enable HTTP basic authentication.
4. Enter the Username and Password.
5. Click OK.
HTTP header
Additional headers can be included in the user-agent field. Use \r\n to separate the URL headers, for example:
# set user-agent "Firefox\r\nheader1: test1\r\nheader2: test2"
Sample request:
HTTP request: http
GET /filetypes/test.tar.gz HTTP/1.1
Host: 172.17.219.10
User-Agent: Firefox
header1: test1
header2: test2
Accept: */*
Connection: close
Threat feed external connectors use this functionality to support authentication using an API key. The API key
authentication can only be configured in the CLI with the set user-agent command. The API key must be appended
with user-agent in the following format: “user-agent\r\nAPI-Key:SecretAPIkey”. API keys are typically used for
programmatic access to the resource by an authorized requester. See What Is an API Key in the Fortinet Cyber Glossary
for more information.
FortiOS 7.6.2 Administration Guide 3798
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,798
|
Fortinet Security Fabric
To enable API key authentication in a threat feed connector:
1. Configure the threat feed. See Configuring a threat feed with an external feed update on page 3796.
2. Configure the user-agent with an API key:
config system external resources
edit <name>
set user-agent "Firefox\r\nAPI-Key:abcdef12345"
next
end
See Using the AusCERT malicious URL feed with an API key on page 3822 for an example.
Configuring a threat feed with a push API update
The threat feed receives entry updates from webhook requests to the FortiGate REST API. This method provides the
code samples needed to perform add, remove, and snapshot operations.
In the following example, a FortiGuard Category threat feed is used to show the different API push options.
To configure the threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click FortiGuard Category.
3. Enter a name.
4. Set the Update method to Push API.
5. Click OK. The Threat Feed Push API Information pane opens that contains the following fields:
l URL: the FortiGate's API URL to call in order to perform the update.
l API admin key: when an API administrator user is configured on the FortiGate, an API admin key will be
associated with the API administrator. Input the API key to see the final cURL request.
l Push command: select one of three push methods.
l Add: add the specified entries to the threat feed.
l Remove: remove the specified entries from the threat feed.
FortiOS 7.6.2 Administration Guide 3799
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,799
|
Fortinet Security Fabric
l Snapshot: replace the threat feed with all specified entries.
l Entries: enter the entries separated by a comma (,) to be applied to the FortiGuard Category threat feed list.
l Sample cURL request: copy this cURL command to perform the push API update on the FortiGate against the
list (cccccccc).
See REST API administrator on page 2984 for more information.
6. Copy the content in the Sample cURL request field (Add is used in this example).
7. Click OK.
8. On a client, generate the API request for the threat feed.
To configure the threat feed in the CLI:
config system external-resource
edit "cccccccc"
set update-method push
set category 201
next
end
FortiOS 7.6.2 Administration Guide 3800
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,800
|
Fortinet Security Fabric
To use the API in the CLI:
# diagnose system external-resource {push-add | push-remove | push-snapshot} <ext_name>
<entry>
To use the API with a JSON file:
# diagnose sys external-resource push-api-json-commands
{
"commands": [ <Array: Mandatory>
{ <Object: Mandatory>
"name": <String: Mandatory, Example: "AWS_MALWARE_FEED">
"command": <String: mandatory, Options: "add", "remove", "snapshot">,
"entries": [ <Array: Mandatory>
<String: Mandatory, Example: "10.100.1.1">
]
}
]
}
Sample:
# diagnose sys external-resource push-api-json-commands '{"commands":
[{"name":"test","command":"add","entries":["10.10.10.1","10.10.10.2"]},
{"name":"test","command":"whatever","entries":["10.10.10.3","10.10.10.4"]}]}'
command returned: EXT_RESOURCE_PUSH_CMD_RETURN_OK
Returned json:
[
{
"name":"test",
"command":"add",
"status":"success"
},
{
"name":"test",
"command":"whatever",
"error":"Invalid command.",
"status":"error"
}
]
To use the API with a Postman REST client:
1. Create an API administrator in FortiOS with write access.
2. Ensure the API token is generated.
3. Configure the external resource list as needed.
4. In the Postman client, create a new request, set the HTTP method to POST, enter the URL.
5. Configure the access token using one of the following methods:
l To use the bearer token: click the Authorization tab, set the Type to Bearer, and enter the REST API
administrator token.
l To use the access_token parameter: click the Params tab and enter the access_token key-value pair (access_
token and <key>).
6. Click the Body tab and configure the following:
FortiOS 7.6.2 Administration Guide 3801
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,801
|
Fortinet Security Fabric
a. Select raw and set the input type to JSON.
b. Insert the JSON data payload.
7. Click Send to send the POST request. If there is a response, the response body appears. For example,
POST https://172.18.52.153/api/v2/monitor/system/external-resource/dynamic?access_
token=g1mnfs8bzxk5hf8Qwcz4kx7yn3jHmG&vdom=vd1
Content-Type: application/json
User-Agent: PostmanRuntime/7.29.2
Accept: */*
Postman-Token: 04e10736-190e-4119-92e1-04e91bf99c10
Host: 172.18.52.153
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 485
{
"commands":[
{
"name":"ip",
"command":"add",
"entries":[
"10.10.10.1",
"10.10.10.2"
]
},
{
"name":"fqdn",
"command":"remove",
"entries":[
"10.10.10.1",
"10.10.10.2"
]
},
{
"name":"fortiguard",
"command":"snapshot",
"entries":[
"10.10.10.1",
"10.10.10.2"
]
}
]
}
HTTP/1.1 200 OK
date: Fri, 22 Jul 2022 21:10:39 GMT
x-frame-options: SAMEORIGIN
content-security-policy: frame-ancestors 'self'
x-xss-protection: 1; mode=block
cache-control: no-cache, must-revalidate
content-length: 480
content-type: application/json
Connection: keep-alive
{
"http_method":"POST",
FortiOS 7.6.2 Administration Guide 3802
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,802
|
Fortinet Security Fabric
"results":[
{
"name":"ip",
"command":"add",
"status":"success"
},
{
"name":"fqdn",
"command":"remove",
"status":"success"
},
{
"name":"fortiguard",
"command":"snapshot",
"status":"success"
}
],
"vdom":"vd1",
"path":"system",
"name":"external-resource",
"action":"dynamic",
"status":"success",
"serial":"FG6H1E5819900000",
"version":"v7.2.1",
"build":1254
}
Viewing the update history
To review the update history of a threat feed, go to Security Fabric > External Connectors, select a feed, and click Edit.
The Last Update field shows the date and time that the feed was last updated.
Click View Entries to view the current entries in the list.
FortiGuard category threat feed
A FortiGuard category threat feed is a dynamic list that contains URLs and is periodically updated from an external
server. The list is stored in text file format on an external server. After the FortiGate imports this list, it becomes available
as a category in the Remote Categories group of web filter profiles that can be used to block or monitor URLs matching
FortiOS 7.6.2 Administration Guide 3803
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,803
|
Fortinet Security Fabric
this category. A category threat feed can also be used solely or grouped with other categories to be used for exemptions
within an SSL/SSH profile that performs full SSL inspection.
Multiple custom categories can be defined by creating a FortiGuard Category threat feed for each category.
Text file example:
http://example/com.url
https://example.com/url
http://example.com:8080/url
The file contains one URL per line. See External resources file format for more information about the URL list formatting
style.
Example configuration
In this example, a list of URLs is imported using the FortiGuard category threat feed. The newly created threat feed is set
to block in the web filter profile, and the web filter profile is applied to a firewall policy. Any traffic that passes through the
FortiGate and matches the URLs in the threat feed list will be dropped.
To configure a FortiGuard category threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click FortiGuard Category.
3. Set the Name to Custom-Remote-FGD.
4. Set the Update method to External Feed.
5. Set the URL of external resource to https://192.168.10.13/Override_URLs.txt.
6. Configure the remaining settings as needed, then click OK.
7. Edit the connector, then click View Entries to view the URL in the feed, which is https://www.facebook.com.
FortiOS 7.6.2 Administration Guide 3804
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,804
|
Fortinet Security Fabric
To configure a FortiGuard category threat feed in the CLI:
config system external-resource
edit "Custom-Remote-FGD"
set type category
set category 192
set resource "https://192.168.10.13/Override_URLs.txt"
set server-identity-check {none | basic | full}
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, it is set to
none.
To apply a FortiGuard category threat feed in a web filter profile:
1. Go to Security Profiles > Web Filter and create a new web filter profile, or edit an existing one.
2. Enable FortiGuard Category Based Filter.
3. In the Remote Categories group, set the action for the Custom-Remote-FGD category to Block.
4. Configure the remaining settings as needed, then click OK.
Selecting the Allow action for the FortiGuard Category Based Filter does not actually allow
the category. It merely implies that no filter has been applied.
We recommend avoid using the Allow action for remote categories, as it will not override
the original action specified in the FortiGuard Category Based Filter.
The Monitor and Block actions for remote categories can override the original action
specified in the FortiGuard Category Based Filter.
To apply the web filter profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, enable Web Filter and select the profile used in the previous procedure.
4. Enable Log Allowed Traffic.
5. Click OK.
URLs that match the FortiGuard category threat feed list are rated as the FortiGuard category threat feed, overriding
their original domain rating. Use the FortiGuard Web Filter Lookup to check the original category of a URL.
To view the web filer logs:
1. Go to Log & Report > Security Events and select Web Filter.
2. View the log details in the GUI, or download the log file:
1: date=2023-02-06 time=09:31:04 eventtime=1675704664795395841 tz="-0800"
logid="0316013056" type="utm" subtype="webfilter" eventtype="ftgd_blk" level="warning"
vd="root" policyid=1 poluuid="e8b310ba-914f-51ed-9014-7b2a116f29ad" policytype="policy"
FortiOS 7.6.2 Administration Guide 3805
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,805
|
Fortinet Security Fabric
sessionid=509983 srcip=172.20.120.13 srcport=54645 srccountry="Reserved" srcintf="port2"
srcintfrole="undefined" srcuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec"
dstip=157.240.3.35 dstport=443 dstcountry="United States" dstintf="port3"
dstintfrole="wan" dstuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec" proto=6
httpmethod="GET" service="HTTPS" hostname="www.facebook.com" agent="Mozilla/5.0 (Windows
NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140
Safari/537.36 Edge/18.17763" profile="default" action="blocked" reqtype="referral"
url="https://www.facebook.com/"
referralurl="https://www.google.com/url?url=https://www.facebook.com/&q=facebook&rct=j&s
a=X&source=suggest&ct=res&oi=suggest_nav&usg=AOvVaw3XzIKieZECH5KqZaBe775&oq=facebook&gs_l=heirloomhp..0.5j0i512i433i131i10l3j0i512i433i10l3j0i512i433i131i10l2j0i512i433i10.1716.3397.0.58
24.8.8.0.0.0.0.85.609.8.8.0....0...1ac.1.34.heirloom-hp..0.8.608.798UUeJkbN0"
sentbyte=527 rcvdbyte=0 direction="outgoing" msg="URL belongs to a denied category in
policy" ratemethod="domain" cat=192 catdesc="Custom-Remote-FGD"
Note that facebook.com, which was originally in the Social Networking category with a default action set to allow in
the FortiGuard Category Based Filter, has been overridden by the block action of the remote category.
Applying a FortiGuard category threat feed in an SSL/SSH profile
A FortiGuard category threat feed can be applied in an SSL/SSH profile where full SSL inspection mode is used. The
threat feed category can be selected in the exempt category list. HTTPS requests that match the URLs in the threat feed
list will be exempted from SSL deep inspection. This example uses the Custom-Remote-FGD threat feed configured in
the previous example.
To configure the SSL/SSH profile:
1. Go to Security Profiles > SSL/SSH Inspection and create a new profile, or edit an existing one.
2. Set the Inspection method to Full SSL Inspection.
3. In the Exempt from SSL Inspection section, locate Web categories. Click the + and add Custom-Remote-FGD in the
FORTIGUARD CATEGORY THREAT FEED section.
4. Enable Log SSL exemptions.
5. Click OK.
To apply the SSL/SSH inspection profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, set SSL Inspection to the profile used in the previous procedure.
4. Enable Log Allowed Traffic.
5. Click OK.
URLs that match the FortiGuard category threat feed list are rated as the FortiGuard category threat feed, overriding
their original domain rating. Use the FortiGuard Web Filter Lookup to check the original category of a URL.
To view the SSL logs:
1. Go to Log & Report > Security Events and select SSL.
2. View the log details in the GUI, or download the log file:
FortiOS 7.6.2 Administration Guide 3806
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,806
|
Fortinet Security Fabric
1: date=2023-02-06 time=11:23:54 eventtime=1675711434094550877 tz="-0800"
logid="1701062009" type="utm" subtype="ssl" eventtype="ssl-exempt" level="notice"
vd="root" action="exempt" policyid=1 poluuid="e8b310ba-914f-51ed-9014-7b2a116f29ad"
policytype="policy" sessionid=531331 service="SSL" profile="custom-deep-inspection"
srcip=172.20.120.13 srcport=52805 srccountry="Reserved" dstip=157.240.3.35 dstport=443
dstcountry="United States" srcintf="port2" srcintfrole="undefined" dstintf="port3"
dstintfrole="wan" srcuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec" dstuuid="3342cb44-9140-
51ed-5dbe-8e0787bedeec" proto=17 tlsver="tls1.3" sni="www.facebook.com" cipher="0x1301"
authalgo="ecdsa" kxproto="ecdhe" eventsubtype="user-category" cat=192 catdesc="CustomRemote-FGD" hostname="www.facebook.com" msg="SSL connection is exempted based on user
category rating.
IP address threat feed
An IP address threat feed is a dynamic list that contains IPv4 and IPv6 addresses, address ranges, and subnets. The list
is periodically updated from an external server and stored in text file format on an external server. After the FortiGate
imports this list, it can be used as a source or destination in firewall policies, proxy policies, local-in policies, and ZTNA
rules. It can also be used as an external IP block list in DNS filter profiles.
Text file example:
192.168.2.100
172.200.1.4/16
172.16.1.2/24
172.16.8.1-172.16.8.100
2001:0db8::eade:27ff:fe04:9a01/120
2001:0db8::eade:27ff:fe04:aa01-2001:0db8::eade:27ff:fe04:ab01
The file contains one IPv4 or IPv6 address, address range, or subnet per line. See External resources file format for
more information about the IP list formatting style.
Example configuration
In this example, a list of destination IP addresses is imported using the IP address threat feed. The newly created threat
feed is then used as a destination in a firewall policy with the action set to deny. Any traffic that passes through the
FortiGate and matches the defined firewall policy will be dropped.
Please note that the URI provided in the example is solely for demonstration purposes and
does not represent a reliable list of well-maintained IP addresses. It is recommended that you
utilize a URI of a reputable external IP list that is regularly updated.
To configure an IP address threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click IP Address.
3. Set the Name to AWS_IP_Blocklist.
4. Set the Update method to External Feed.
5. Set the URL of external resource to https://blocklist-example.com/ip-blocklist/ip.txt.
6. Configure the remaining settings as required, then click OK.
FortiOS 7.6.2 Administration Guide 3807
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,807
|
Fortinet Security Fabric
7. Edit the connector, then click View Entries to view the IP addresses in the feed.
To configure an IP address threat feed in the CLI:
config system external-resource
edit "AWS_IP_Blocklist"
set type address
set resource "https://blocklist-example.com/ip-blocklist/ip.txt"
set server-identity-check {none | basic | full}
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, it is set to
none.
To apply an IP address threat feed in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. In the Destination field, click the + and select AWS_IP_Blocklist from the list (in the IP ADDRESS FEED section).
4. Set Action to DENY.
5. Enable Log Allowed Traffic.
6. Click OK.
Applying an IP address threat feed as an external IP block list in a DNS filter profile
An IP address threat feed can be applied by enabling External IP Block Lists in a DNS filter profile. Any DNS query that
passes through the FortiGate and resolves to any of the IP addresses in the threat feed list will be dropped.
FortiOS 7.6.2 Administration Guide 3808
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,808
|
Fortinet Security Fabric
To configure the DNS filter profile:
1. Go to Security Profiles > DNS Filter and create a new profile, or edit an existing one.
2. Enable External IP Block Lists.
3. Click the + and select AWS_IP_Blocklist from the list.
4. Click OK.
To apply the DNS filter profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, enable DNS Filter and select the profile used in the previous procedure.
4. Enable Log Allowed Traffic.
5. Click OK.
IP addresses that match the IP address threat feed list will be blocked.
To view the DNS query logs:
1. Go to Log & Report > Security Events and select DNS Query.
2. View the log details in the GUI, or download the log file:
1: date=2023-02-06 time=15:06:50 eventtime=1675724810452621179 tz="-0800"
logid="1501054400" type="utm" subtype="dns" eventtype="dns-response" level="warning"
vd="root" policyid=0 sessionid=555999 srcip=172.20.120.13 srcport=59602
srccountry="Reserved" srcintf="port2" srcintfrole="undefined" dstip=172.20.120.12
dstport=53 dstcountry="Reserved" dstintf="root" dstintfrole="undefined" proto=17
profile="default" xid=24532 qname="dns.google" qtype="A" qtypeval=1 qclass="IN"
ipaddr="208.91.112.55" msg="Domain was blocked because it is in the domain-filter list"
action="redirect" domainfilteridx=0 domainfilterlist="AWS_IP_Block_list"
Applying an IP address threat feed in a local-in policy
An IP address threat feed can be applied as a source or destination in a local-in policy.
In this example, a previously created IP address threat feed named AWS_IP_Blocklist is used as a source address in a
local-in-policy. Any traffic originating from any of the IP addresses in the threat feed list and destined for the FortiGate will
be dropped.
To apply an IP address threat feed in a local-in policy:
config firewall local-in-policy
edit 1
set intf "any"
set srcaddr "AWS_IP_Blocklist"
set dstaddr "all"
set service "ALL"
set schedule "always"
next
end
FortiOS 7.6.2 Administration Guide 3809
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,809
|
Fortinet Security Fabric
To test the configuration:
1. From one of the IP addresses listed in IP address threat feed (in this case 172.16.200.2), start a continuous ping to
port1:
ping 172.16.200.1 –t
2. On the FortiGate, enable debug flow:
# diagnose debug flow filter addr 172.16.200.2
# diagnose debug flow filter proto 1
# diagnose debug enable
# diagnose debug flow trace start 10
3. The output of the debug flow shows that traffic is dropped by local-in policy 1:
id=65308 trace_id=11 func=print_pkt_detail line=5939 msg="vd-root:0 received a packet
(proto=1, 172.16.200.2:0->172.16.200.1:2048) tun_id=0.0.0.0 from port1. type=8, code=0,
id=0, seq=0."
id=65308 trace_id=11 func=init_ip_session_common line=6121 msg="allocate a new session0002f318, tun_id=0.0.0.0"
id=65308 trace_id=11 func=__vf_ip_route_input_rcu line=2012 msg="find a route:
flag=80000000 gw-0.0.0.0 via root"
id=65308 trace_id=11 func=fw_local_in_handler line=545 msg="iprope_in_check() check
failed on policy 1, drop"
Domain name threat feed
A domain name threat feed is a dynamic list that contains domains and periodically updates from an external server. The
list is stored in a text file format on an external server. After the FortiGate imports this list, it becomes available as a
category in the Remote Categories group of DNS filter profiles that can be used to block or monitor domains matching
this category. Multiple custom categories can be defined by creating a domain name threat feed for each category.
Text file example:
mail.*.example.com
*-special.example.com
www.*example.com
example.com
The file contains one domain name per line. See External resources file format for more information about the domain list
formatting style.
Example configuration
In this example, a list of domain names is imported using the domain name threat feed. The newly created threat feed is
set to monitor in the DNS filter profile, and the DNS filter profile is applied to a firewall policy. Any traffic that passes
through the FortiGate and matches any of the domain names in the threat feed list will be monitored.
To configure a domain name threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click Domain Name.
3. Set the Name to Domain_monitor_list.
FortiOS 7.6.2 Administration Guide 3810
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,810
|
Fortinet Security Fabric
4. Set the Update method to External Feed.
5. Set the URL of external resource to https://192.168.10.13/external_domain_list.txt.
6. Configure the remaining settings as required, then click OK.
7. Edit the connector, then click View Entries to view the domain names in the feed (fortinet.com and example.com).
To configure a domain name threat feed in the CLI:
config system external-resource
edit "Domain_monitor_list”
set type domain
set category 194
set resource "http://192.168.10.13/external_domain_list.txt"
set server-identity-check {none | basic | full}
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, it is set to
none.
To apply a domain name threat feed in a DNS filter profile:
1. Go to Security Profiles > DNS Filter and create a new DNS filter profile, or edit an existing one.
2. Enable FortiGuard Category Based Filter.
3. In the Remote Categories group, set the action for the Domain_monitor_list category to Monitor.
FortiOS 7.6.2 Administration Guide 3811
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,811
|
Fortinet Security Fabric
4. Configure the remaining settings as needed, then click OK.
Selecting the Allow action for the FortiGuard Category Based Filter does not actually allow
the category. It merely implies that no filter has been applied.
We recommend avoid using the Allow action for remote categories, as it will not override
the original action specified in the FortiGuard Category Based Filter.
The Monitor and Block actions for remote categories can override the original action
specified in the FortiGuard Category Based Filter.
To apply the DNS filter profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, enable DNS Filter and select the profile used in the previous procedure.
4. Enable Log Allowed Traffic.
5. Click OK.
Domains that match the domain threat feed list are rated as domain threat feed, overriding their original domain rating.
Use the FortiGuard Secure DNS Service to check the original category of a domain name.
To view the DNS query logs:
1. Go to Log & Report > Security Events and select DNS Query.
2. View the log details in the GUI, or download the log file:
1: date=2023-02-03 time=10:44:16 eventtime=1675449856658521042 tz="-0800"
logid="1501054802" type="utm" subtype="dns" eventtype="dns-response" level="notice"
vd="root" policyid=0 sessionid=265870 srcip=172.20.120.13 srcport=59662
srccountry="Reserved" srcintf="port2" srcintfrole="undefined" dstip=172.20.120.12
dstport=53 dstcountry="Reserved" dstintf="root" dstintfrole="undefined" proto=17
profile="default" xid=35624 qname="example.com" qtype="A" qtypeval=1 qclass="IN"
ipaddr="93.184.216.34" msg="Domain is monitored" action="pass" cat=194 catdesc="Domain_
monitor_list"
2: date=2023-02-03 time=10:44:08 eventtime=1675449848683418535 tz="-0800"
logid="1501054802" type="utm" subtype="dns" eventtype="dns-response" level="notice"
vd="root" policyid=0 sessionid=265537 srcip=172.20.120.13 srcport=57434
srccountry="Reserved" srcintf="port2" srcintfrole="undefined" dstip=172.20.120.12
dstport=53 dstcountry="Reserved" dstintf="root" dstintfrole="undefined" proto=17
profile="default" xid=31194 qname="fortinet.com" qtype="A" qtypeval=1 qclass="IN"
ipaddr="3.1.92.70, 52.220.222.172" msg="Domain is monitored" action="pass" cat=194
catdesc="Domain_monitor_list"
Note that fortinet.com, which was originally in the Information Technology category with a default action set to allow
in the FortiGuard Category Based Filter, has been overridden by the monitor action of the remote category.
MAC address threat feed
A MAC address threat feed is a dynamic list that contains MAC addresses, MAC ranges, and MAC OUIs. The list is
periodically updated from an external server and stored in text file format on an external server. After the FortiGate
FortiOS 7.6.2 Administration Guide 3812
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,812
|
Fortinet Security Fabric
imports this list, it can be used as a source in firewall policies, proxy policies, and ZTNA rules. For policies in transparent
mode or virtual wire pair policies, the MAC address threat feed can be used as a source or destination address.
Text file example:
01:01:01:01:01:01
01:01:01:01:01:01-01:01:02:50:20:ff
8c:aa:b5
The file contains one MAC address, MAC range, or MAC OUI per line. See External resources file format for more
information about the MAC list formatting style.
Example configuration
In this example, a list of MAC addresses is imported using the MAC address threat feed. The newly created threat feed is
then used as a source in a firewall policy with the action set to accept. Any traffic from the client MAC addresses that
match the defined firewall policy will be allowed.
To configure a MAC address threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click MAC Address.
3. Set the Name to MAC_List.
4. Set the Update method to External Feed.
5. Set the URL of external resource to http://172.16.200.55/external-resources/Ext-Resource-Type-as-Address-mac1.txt.
6. Configure the remaining settings as required, then click OK.
7. Edit the connector, then click View Entries to view the MAC addresses in the feed.
To configure a MAC address threat feed in the CLI:
config system external-resource
edit "MAC_List"
set type mac-address
set resource "http://172.16.200.55/external-resources/Ext-Resource-Type-as-AddressFortiOS 7.6.2 Administration Guide 3813
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,813
|
Fortinet Security Fabric
mac-1.txt"
set server-identity-check {none | basic | full}
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, it is set to
none.
To apply a MAC address threat feed in a firewall policy in the GUI:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. In the Source field, click the + and select MAC_List from the list (in the MAC ADDRESS FEED section).
4. Set Action to ACCEPT.
5. Click OK.
To apply a MAC address threat feed in a firewall policy in the CLI:
config firewall policy
edit 1
set name "MAC-traffic"
set srcintf "port2"
set dstintf "port1"
set action accept
set srcaddr "MAC_List"
set dstaddr "all"
set srcaddr6 "all"
set dstaddr6 "all"
set schedule "always"
set service "ALL"
set utm-status enable
set profile-protocol-options "protocol"
set nat enable
next
end
To verify the MAC addresses used in the firewall policy:
# diagnose sys external-mac-resource list MAC_List
MAC ranges of uuid-idx 574 (num=1)
be:d1:6b:0d:20:61-be:d1:6b:0d:20:61
Malware hash threat feed
A malware hash threat feed is a dynamic list that contains malware hashes and periodically updates from an external
server. The list is stored in text file format on an external server. After the FortiGate imports this list, it is automatically
used for virus outbreak prevention on antivirus profiles when Use external malware block list is enabled. Similar to
FortiGuard outbreak prevention, the malware hash threat feed is not supported in AV quick scan mode.
Text file example:
FortiOS 7.6.2 Administration Guide 3814
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,814
|
Fortinet Security Fabric
292b2e6bb027cd4ff4d24e338f5c48de
dda37961870ce079defbf185eeeef905 Trojan-Ransom.Win32.Locky.abfl
3fa86717650a17d075d856a41b3874265f8e9eab Trojan-Ransom.Win32.Locky.abfl
c35f705df9e475305c0984b05991d444450809c35dd1d96106bb8e7128b9082f TrojanRansom.Win32.Locky.abfl
The file contains one malware hash per line. See External resources file format for more information about the malware
hash list formatting style.
For optimal performance, do not mix different hashes in the list. Only use one MD5, SHA1, or
SHA256.
Example configuration
In this example, a list of malware hashes is imported using the malware threat feed. The newly created threat feed is
applied to an antivirus profile, and the antivirus profile is applied to a firewall policy. Any traffic that passes through the
FortiGate and matches the malware hashes in the threat feed list will be dropped.
To configure a malware hash threat feed in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click Malware Hash.
3. Set the Name to AWS_Malware_Hash.
4. Set the Update method to External Feed.
5. Set the URL of external resource to https://s3.us-west-2.amazonaws.com/malware.txt.
6. Configure the remaining settings as required, then click OK.
7. Edit the connector, then click View Entries to view the hash list.
To configure a malware hash threat feed in the CLI:
config system external-resource
edit "AWS_Malware_Hash"
set type malware
FortiOS 7.6.2 Administration Guide 3815
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,815
|
Fortinet Security Fabric
set resource "https://s3.us-west-2.amazonaws.com/malware.txt"
set server-identity-check {none | basic | full}
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, it is set to
none.
To apply a malware hash threat feed in an antivirus profile:
1. Go to Security Profiles > AntiVirus and create a new web filter profile, or edit an existing one.
2. Enable Use external malware block list.
3. Click the + and select AWS_Malware_Hash from the list.
4. Configure the remaining settings as needed, then click OK.
To apply the antivirus profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, enable AntiVirus and select the profile used in the previous procedure.
4. Set SSL Inspection to deep-inspection to inspect HTTPS traffic.
5. Enable Log Allowed Traffic.
6. Click OK.
To view the antivirus logs:
1. Go to Log & Report > Security Events and select AntiVirus.
2. View the log details in the GUI, or download the log file:
1: date=2023-02-03 time=15:42:41 eventtime=1675467761491047388 tz="-0800"
logid="0207008212" type="utm" subtype="virus" eventtype="malware-list" level="warning"
vd="root" policyid=1 poluuid="e8b310ba-914f-51ed-9014-7b2a116f29ad" policytype="policy"
msg="Blocked by local malware list." action="blocked" service="HTTP" sessionid=293915
srcip=172.20.120.13 dstip=192.168.10.13 srcport=53515 dstport=80 srccountry="Reserved"
dstcountry="Reserved" srcintf="port2" srcintfrole="undefined" dstintf="port3"
dstintfrole="wan" srcuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec" dstuuid="3342cb44-9140-
51ed-5dbe-8e0787bedeec" proto=6 direction="incoming" filename="test.jpg"
quarskip="Quarantine-disabled" virus="a1a74a39788854b75d454dc9c83c612b" viruscat="File
Hash" dtype="external-blocklist" filehash="a1a74a39788854b75d454dc9c83c612b"
filehashsrc="AWS_Malware_Hash" url="http://192.168.10.13/test.jpg" profile="default"
agent="curl/7.55.1" httpmethod="GET" analyticssubmit="false" crscore=10 craction=2
crlevel="medium"
To verify the scanunit daemon:
# diagnose sys scanunit file-hash list
malware 'a1a74a39788854b75d454dc9c83c612b' vf_id 0 uuid 15752 profile 'AWS_Malware_Hash'
description ''
The list of external hashes has been updated.
FortiOS 7.6.2 Administration Guide 3816
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,816
|
Fortinet Security Fabric
Threat feed connectors per VDOM
When multi-VDOM mode is enabled, a threat feed external connector can be defined in global or within a VDOM. Global
threat feeds can be used in any VDOM, but cannot be edited within the VDOM. FortiGuard category and domain namebased external feeds have an added category number field to identify the threat feed. The threat feed name in global
must start with g-. Threat feed names in VDOMs cannot start with g-.
FortiGuard category and domain name-based external feed entries must have a number assigned to them that ranges
from 192 to 221. This number can be assigned to both external feed types. However, when a category number is used
under a global entry, such as 192 with the name g-cat-192, this category number cannot be used in any other global or
VDOM entries. If a category is used under a VDOM entry, such as 192 under VDOM1 with the name cat-192, the
category 192 can be used in another VDOM or root with the name cat-192.
A threat feed connector can only be used in profiles in the VDOM that it was created in. Global connectors can be used in
all VDOMs.
Each VDOM can have a maximum of 256 threat feed entries. But in total, a FortiGate can only have 511 threat feed
entries.
To improve the security of the connection, it is recommended to enable server certificate validation (serveridentity-check) either in basic or full mode.
To configure a FortiGuard category threat feed connector under global in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click FortiGuard Category.
3. Enter a name that begins with g-.
4. Configure the other settings as needed.
5. Click OK.
To configure a FortiGuard category threat feed connector under global in the CLI:
config global
config system external-resource
edit "g-category"
set status enable
set type category
set category 192
set comments ''
set resource "http://172.16.200.55/external-resource-test/513-FDGCategory.txt"
set server-identity-check {none | basic | full}
set refresh-rate 5
next
end
end
To configure a domain name threat feed connector under a VDOM in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, click Domain Name.
3. Enter a name that does not begin with g-.
4. Configure the other settings as needed.
FortiOS 7.6.2 Administration Guide 3817
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,817
|
Fortinet Security Fabric
5. Click OK. The threat feed connector created under global also appears, but it is not editable.
To configure a domain name threat feed connector under a VDOM in the CLI:
config vdom
edit vd1
config system external-resource
edit "vd1-domain"
set status enable
set type domain
set category 193
set comments ''
set resource "http://172.16.200.55/external-resource-test/513-Domain.txt"
set server-identity-check {none | basic | full}
set refresh-rate 5
next
end
next
end
To use an IP address threat feed in a policy in the GUI:
1. Configure an IP address connector in global:
a. Go to Security Fabric > External Connectors and click Create New.
b. In the Threat Feeds section, click IP Address.
c. Enter a name that begins with g-.
d. Configure the other settings as needed.
e. Click OK.
2. Configure an IP address connector in the VDOM (vd1):
a. Go to Security Fabric > External Connectors and click Create New.
b. In the Threat Feeds section, click IP Address.
c. Enter a name that does not begin with g-.
d. Configure the other settings as needed.
FortiOS 7.6.2 Administration Guide 3818
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,818
|
Fortinet Security Fabric
e. Click OK. The threat feed connectors created under global also appear, but they are not editable.
3. Configure the firewall policy in the VDOM (vd1):
a. Go to Policy & Objects > Firewall Policy and click Create New.
b. For Destination, select vd1-address. Since this policy is configured under vd1, g-address can also be set as the
destination.
c. Configure the other settings as needed.
d. Click OK.
To use an IP address threat feed in a policy in the CLI:
1. Configure the IP address connectors:
config global
config system external-resource
edit "g-address"
set status enable
set type address
set username ''
set comments ''
set resource "http://172.16.200.55/external-resource-test/513-IP.txt"
set server-identity-check {none | basic | full}
set refresh-rate 5
next
FortiOS 7.6.2 Administration Guide 3819
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,819
|
Fortinet Security Fabric
end
end
config vdom
edit vd1
config system external-resource
edit "vd1-address"
set status enable
set type address
set comments ''
set resource "http://172.16.200.55/external-resource-test/513-IP.txt"
set user-agent "curl/7.58.0"
set server-identity-check {none | basic | full}
set refresh-rate 5
next
end
next
end
2. In the VDOM, configure a firewall policy with the external address as the destination address:
config vdom
edit vd1
config firewall policy
edit 1
set name "test"
set srcintf "port10"
set dstintf "port9"
set srcaddr "all"
set dstaddr "vd1-address"
set action accept
set schedule "always"
set service "ALL"
set profile-protocol-options "protocol"
set nat enable
next
end
next
end
Since this firewall policy is configured under vd1, g-address can also be set as the
dstaddr.
STIX format for external threat feeds
The FortiGate's external threat feeds support feeds that are in the STIX/TAXII format. Use the stix:// prefix in the URI
to denote the protocol.
All external threat feeds support the STIX format. In this example, a FortiGuard Category threat feed in the STIX format
is configured.
FortiOS 7.6.2 Administration Guide 3820
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,820
|
Fortinet Security Fabric
To configure a FortiGuard Category threat feed in the STIX format in the GUI:
1. Go to Security Fabric > External Connectors and click Create New.
2. Select FortiGuard Category from the Threat Feeds section.
3. Configure the connector:
l Name: category-taxii
l Update method: External Feed
l URL of external resource: stix://limo.anomali.com/api/v1/taxii2/feeds/collections/200/objects/
l HTTP basic authentication: Enable and enter the username and password, such as guest and guest.
4. Click OK.
5. Edit the connector, and click View Entries in the right side bar to view the retrieved entries.
FortiOS 7.6.2 Administration Guide 3821
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,821
|
Fortinet Security Fabric
To configure a FortiGuard Category threat feed in the STIX format in the CLI:
config system external-resource
edit "category-taxii"
set category 194
set username "guest"
set password guest
set resource "stix://limo.anomali.com/api/v1/taxii2/feeds/collections/200/objects/"
set server-identity-check {none| basic | full}
set update-method feed
next
end
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) either in basic or full mode. By default, serveridentity-check is set to none.
If the connector is used in webfilter that blocks category 194, the traffic that matches the retrieved URLs, such as
rsiuk.co.uk, is blocked:
1: date=2021-10-06 time=18:07:46 eventtime=1633568867163763708 tz="-0700" logid="0316013056"
type="utm" subtype="webfilter" eventtype="ftgd_blk" level="warning" vd="vd1" policyid=1
sessionid=174974 srcip=10.1.100.12 srcport=48284 srcintf="port2" srcintfrole="undefined"
srcuuid="c6753ba2-231b-51ec-1675-090f2b5f1384" dstip=78.129.255.151 dstport=443
dstintf="port1" dstintfrole="undefined" dstuuid="c6753ba2-231b-51ec-1675-090f2b5f1384"
proto=6 service="HTTPS" hostname="rsiuk.co.uk" profile="test" action="blocked"
reqtype="direct" url="https://rsiuk.co.uk/" sentbyte=75 rcvdbyte=0 direction="outgoing"
msg="URL belongs to a denied category in policy" method="domain" cat=194 catdesc="categorytaxii"
Using the AusCERT malicious URL feed with an API key
In this example, a list of malicious URLs is imported from AUSCERT, an Australian not for profit organization. See
AUSCERT for more information.
The FortiGuard threat feed is used to import the malicious URL feed by appending the API key to the user-agent. See
HTTP header on page 3798 for more information. The newly created threat feed is set to block in the web filter profile,
and the web filter profile is applied to a firewall policy. Any traffic that passes through the FortiGate and matches the
URLs in the threat feed list will be dropped, and a replacement message will be shown.
To configure the FortiGuard category threat feed in the GUI:
1. Go Security Fabric > External Connectors and click Create New.
2. In the Threat Feeds section, select FortiGuard Category.
3. Configure the following settings:
Status Enabled
Name AusCERT_Feed
Update method External Feed
URL of external resource https://www.auscert.org.au/api/v1/malurl/combo-7-txt/
FortiOS 7.6.2 Administration Guide 3822
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,822
|
Fortinet Security Fabric
4. Click OK.
5. In the CLI, enter the following:
config system external-resource
edit "AusCERT_Feed"
set user-agent "Firefox\r\nAPI-Key:SECRETAPIKEY"
next
end
6. In the GUI, edit the connector and configure the remaining settings as needed, then click OK.
7. Edit the connector again, and click View Entries in the right pane to view the URL list.
To configure the FortiGuard category threat feed in the CLI:
config system external-resource
edit "AusCERT_Feed"
set category 194
set resource "https://www.auscert.org.au/api/v1/malurl/combo-7-txt/"
set user-agent "Firefox\r\nAPI-Key:SECRETAPIKEY"
next
end
When configuring a FortiGuard category threat feed in the GUI, the category is set
automatically. When configuring a the threat feed in the CLI, the category must be set
manually. The category must be unique and in the range of 192 - 221.
To improve the security of the connection, it is recommended to enable server certificate
validation (server-identity-check) in either basic or full mode. By default, it is set to
none.
To apply the FortiGuard category threat feed to a web filter profile:
1. Go to Security Profiles > Web Filter and create a new web filter profile, or edit an existing one.
2. Enable FortiGuard category based filter.
3. In the Remote Categories group, set the action for the AusCERT_Feed category to Block.
4. Configure the remaining settings as needed, then click OK.
To apply the web filter profile in a firewall policy:
1. Go to Policy & Objects > Firewall Policy and create a new policy, or edit an existing one.
2. Configure the policy fields as required.
3. Under Security Profiles, enable Web Filter and select the profile used in the previous procedure.
4. Enable Log Allowed Traffic.
5. Click OK.
URLs that match the FortiGuard category threat feed list are rated as the category matching the corresponding
FortiGuard category threat feed, overriding their original domain rating.
FortiOS 7.6.2 Administration Guide 3823
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,823
|
Fortinet Security Fabric
To verify that FortiGate is blocking URLs from the AusCERT feed list:
1. Visit one of the URLs from the AusCERT_Feed list.
A replacement message should be shown.
2. Go to Log & Report > Security Events and select Web Filter.
3. View the log details in the GUI, or download the log file:
1: date=2023-04-11 time=14:18:02 eventtime=1681247882561766251 tz="-0700"
logid="0316013056" type="utm" subtype="webfilter" eventtype="ftgd_blk" level="warning"
vd="root" policyid=1 poluuid="26540ed0-ae54-51ed-80eb-89af8af4d53f" policytype="policy"
sessionid=3275 srcip=172.20.120.13 srcport=64151 srccountry="Reserved" srcintf="port2"
srcintfrole="undefined" srcuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec"
dstip=114.142.162.65 dstport=80 dstcountry="Australia" dstintf="port3" dstintfrole="wan"
dstuuid="3342cb44-9140-51ed-5dbe-8e0787bedeec" proto=6 httpmethod="GET" service="HTTP"
hostname="pcmach.co.nz" agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36" profile="default"
action="blocked" reqtype="direct" url="http://pcmach.co.nz/" sentbyte=427 rcvdbyte=0
direction="outgoing" msg="URL belongs to a denied category in policy"
ratemethod="domain" cat=194 catdesc="AusCERT_Feed"
Troubleshooting a threat feed
In this example, the user entered the URL of external resource without the trailing slash. The following commands can be
used to troubleshoot connectivity issues between a FortiGate and external resource:
diagnose debug app dnsproxy -1
diagnose debug app forticron -1
diagnose debug enable
This output shows that the DNS resolution is successful, indicating that the FortiGate has connectivity to the external
server:
#diagnose debug app dnsproxy -1
[worker 0] dns_local_lookup()-2476: vfid=0, real_vfid=0, qname=www.auscert.org.au, qtype=1,
qclass=1, offset=36, map#=4 max_sz=512
[worker 0] dns_lookup_aa_zone()-608: vfid=0, fqdn=www.auscert.org.au
[worker 0] dns_send_request()-1398
[worker 0] dns_send_resol_request()-1234: orig id: 0xa002 local id: 0xa002
domain=www.auscert.org.au
[worker 0] dns_find_best_server()-595: found server: 96.45.46.46
…
id:0xa002 domain=www.auscert.org.au active
FortiOS 7.6.2 Administration Guide 3824
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,824
|
Fortinet Security Fabric
This output shows that the requested resource was missing a trailing slash:
#diagnose debug app forticron -1
fcron_timer_func()-23: Timer ext_upd fired
6745-before-init: fd=-1 name='ext-root.AusCERT_Feed' http_1=0 loc=0 state=send.body info=0-
DNS fail chunk=0 content-0=0 etag=0 csum=0 done=0 closed=0
sync-0(len=0 note=0 err=0) buf-1(sz=8192 data=179 free=8013 pos=0 end=179 max=10485760)
6745-init-as: fd=-1 name='ext-root.AusCERT_Feed' http_1=0 loc=0 state=send.body info=0-None
chunk=0 content-0=0 etag=0 csum=0 done=0 closed=0
sync-0(len=0 note=0 err=0) buf-1(sz=8192 data=0 free=8192 pos=0 end=0 max=10485760)
http_request_make()-2066: HTTP request: https
GET /api/v1/malurl/combo-7-txt HTTP/1.1
Host: www.auscert.org.au
User-Agent: Firefox
API-Key: <obfuscated>
Accept: */*
Connection: close
http_request_make()-2101: fcron_get_addr(www.auscert.org.au)
__update_ext()-187: Updating EXT 'AusCERT_Feed' with HTTP
fcron_update_ext_func()-611: update ver: 0
fcron_timer_func()-32: Timer ext_upd done
fcron_epoll_before_handle()-297: BEFORE READ fd 11 handle event 0x01 read 0xc55a40 epoll
events 0x01
dns_parse_resp()-102: DNS www.auscert.org.au -> 54.253.78.74
dns_parse_resp()-102: DNS www.auscert.org.au -> 13.54.251.23
…
HTTP/1.1 301 Moved Permanently
…
Location: /api/v1/malurl/combo-7-txt/
After adding a trailing slash to the external resource URL, the connection is now working:
#diagnose debug app forticron -1
fcron_timer_func()-23: Timer ext_upd fired
2832-before-init: fd=-1 name='ext-root.AusCERT_Feed' http_1=0 loc=0 state=send.header
info=0-None chunk=0 content-0=0 etag=0 csum=0 done=0 closed=0
sync-0(len=0 note=0 err=0) buf-0(sz=0 data=0 free=0 pos=0 end=0 max=10485760)
2832-init-as: fd=-1 name='ext-root.AusCERT_Feed' http_1=0 loc=0 state=send.header info=0-
None chunk=0 content-0=0 etag=0 csum=0 done=0 closed=0
sync-0(len=0 note=0 err=0) buf-1(sz=8192 data=0 free=8192 pos=0 end=0 max=10485760)
http_request_make()-2066: HTTP request: https
GET /api/v1/malurl/combo-7-txt/ HTTP/1.1
Host: www.auscert.org.au
User-Agent: Firefox
API-Key: <obfuscated>
Accept: */*
Connection: close
…
HTTP/1.1 200 OK
These troubleshooting commands can be used to resolve a variety of issues. they are not
limited to this specific use case.
FortiOS 7.6.2 Administration Guide 3825
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,825
|
Fortinet Security Fabric
Apply threat feed connectors as source addresses in central SNAT
FortiOS allows an IP address threat feed to be applied as a source address in central SNAT. This enhancement allows
for more dynamic and responsive network security configuration.
The IP address threat feed can be applied in the GUI and the CLI:
l In the GUI, select a threat feed object from the IP Address Threat Feed section when creating and editing a policy.
l In the CLI, the IP address threat feed connector can be applied when configuring the central-snat-map.
Example
In the following example, an external IP list threat feed object will be created and used in a central SNAT map as the
source address.
To apply a threat feed connector in central SNAT:
1. Create a threat feed IP list object:
config system external-resource
edit "External-iplist-central-snat"
set type address
set resource "http://172.16.200.55/ip_list_test/test-external-iplist-centralFortiOS 7.6.2 Administration Guide 3826
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,826
|
Fortinet Security Fabric
snat.txt"
next
end
The threat feed list is as follows:
10.1.100.22
10.1.100.41
2000:10:1:100::22
2000:10:1:100::41
See IP address threat feed on page 3807 for more information.
2. Apply the threat feed connector in a central SNAT map as the source address:
config firewall central-snat-map
edit 1
set type ipv6
set srcintf "port2"
set dstintf "port1"
set orig-addr6 "External-iplist-central-snat"
set dst-addr6 "all"
next
edit 2
set srcintf "port2"
set dstintf "port1"
set orig-addr "External-iplist-central-snat"
set dst-addr "all"
next
end
3. Verify that the threat feed connector has been applied and taken effect:
# diagnose firewall iprope list 10000d
policy index=2 uuid_idx=8391 action=accept
flag (8041100): nat sport use_src pol_stats
flag3 (80): best-route
flag4 (200): port-preserve
schedule()
cos_fwd=0 cos_rev=0
group=0010000d av=00000000 au=00000000 split=00000000
host=0 chk_client_info=0x0 app_list=0 ips_view=0
misc=0
zone(1): 8 -> zone(1): 7
dest(1): 0.0.0.0-255.255.255.255, uuid_idx=8031,
source external ip pool(1): 8390
service(1):
[0:0x0:0/(0,65535)->(0,65535)] flags:0 helper:auto
# diagnose firewall iprope6 list 10000d
policy id: 1, group: 0010000d, uuid_idx=8163
action: accept, schedule:
cos_fwd=0 cos_rev=0
flag (08041100): nat sport use_src pol_stats
flag3(00000080): best-route
shapers: / per_ip=
sub_groups: av 00000000 auth 00000000 split 00000000 misc 00000000
app_list: 0 ips_view: 0
FortiOS 7.6.2 Administration Guide 3827
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,827
|
Fortinet Security Fabric
vdom_id: 0
zone_from(1): 8
zone_to(1): 7
address_dst(1):
all uuid_idx=8045
source external ip pool(1):
8390
service(1):
[0:0x0:0/(0,65535)->(0,65535)] helper:auto
nat(0):
nat_64(0):
The source external IP pool is attached.
# diagnose sys external-address-resource list
List of external address resources:
name:External-iplist-central-snat, uuid-idx:8390, num of ipv4/ipv6 ranges:2/2, used:yes
# diagnose sys external-address-resource list External-iplist-central-snat
IPv4 ranges of uuid-idx 8390 (num=2)
10.1.100.22-10.1.100.22
10.1.100.41-10.1.100.41
IPv6 ranges of uuid-idx 8390 (num=2)
2000:10:1:100::22-2000:10:1:100::22
2000:10:1:100::41-2000:10:1:100::41
The external IP list UUID index matches.
4. Verify that sending packets from IP addresses included in the IP list will hit the central SNAT map and that SNAT will
take effect:
a. Send packets from an IPv4 address that is included in the IP list. In this example, the packets are sent from
10.1.100.41.
# diagnose sniffer packet any icmp 4
interfaces=[any]
filters=[icmp]
7.269689 port2 in 10.1.100.41 -> 172.16.200.55: icmp: echo request
7.269727 port1 out 172.16.200.6 -> 172.16.200.55: icmp: echo request
7.269850 port1 in 172.16.200.55 -> 172.16.200.6: icmp: echo reply
7.269861 port2 out 172.16.200.55 -> 10.1.100.41: icmp: echo reply
...
8 packets received by filter
0 packets dropped by kernel
SNAT will take effect. The outgoing packet is SNAT'd to the IP address of the port1 interface.
b. Send packets from an IPv4 address that is not included in the IP list. In this example, the packets are sent from
10.1.100.11.
# diagnose sniffer packet any icmp 4
interfaces=[any]
filters=[icmp]
2.323329 port2 in 10.1.100.11 -> 172.16.200.55: icmp: echo request
2.323362 port1 out 10.1.100.11 -> 172.16.200.55: icmp: echo request
...
4 packets received by filter
0 packets dropped by kernel
SNAT will not take effect.
FortiOS 7.6.2 Administration Guide 3828
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,828
|
Fortinet Security Fabric
c. Send packets from an IPv6 address that is included in the IP list. In this example, the packets are sent from
2000:10:1:100::41.
# diagnose sniffer packet any icmp6 4
interfaces=[any]
filters=[icmp6]
2.105798 port2 in 2000:10:1:100::41 -> 2000:172:16:200::55: icmp6: echo request seq 1
[flowlabel 0x204d4]
2.105844 port1 out 2000:172:16:200::6 -> 2000:172:16:200::55: icmp6: echo request seq
1 [flowlabel 0x204d4]
2.105959 port1 in 2000:172:16:200::55 -> 2000:172:16:200::6: icmp6: echo reply seq 1
[flowlabel 0xebd44]
2.105971 port2 out 2000:172:16:200::55 -> 2000:10:1:100::41: icmp6: echo reply seq 1
[flowlabel 0xebd44]
...
8 packets received by filter
0 packets dropped by kernel
SNAT will take effect. The outgoing packet is SNAT'd to the IPv6 address of the port1 interface.
d. Send packets from an IPv6 address that is not included in the IP list. In this example, the packets are sent from
2000:10:1:100::11.
# diagnose sniffer packet any icmp6 4
interfaces=[any]
filters=[icmp6]
1.917946 port2 in 2000:10:1:100::11 -> 2000:172:16:200::55: icmp6: echo request seq 1
1.917979 port1 out 2000:10:1:100::11 -> 2000:172:16:200::55: icmp6: echo request seq
1
...
8 packets received by filter
0 packets dropped by kernel
SNAT will not take effect.
Generic connector for importing addresses
This features allows for seamless integration with any third-party database using a JSON based REST API. Each JSON
entry is converted into an address object on the FortiGate, which can be used in policies like any other address.
Each dynamic firewall address can parse up to 100,000 IP addresses and 3,000 MAC addresses. IPv6 addresses are
not supported.
When VDOMs are enabled, a generic connector that is created in the Global VDOM must have g- prepended to it's
name. The connector and imported addresses are synchronized to all VDOMs. A generic connector that is created in a
specific VDOM is not synchronized to other VDOMs, and the address objects are only imported to that VDOM.
When VDOMs are not enabled, generic connectors cannot use the g- prefix in their name.
External feed update method example
In this example, the FortiGate pulls updates from an external resource: a REST API interface created using JSONBIN.io.
FortiOS 7.6.2 Administration Guide 3829
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,829
|
Fortinet Security Fabric
To create the REST API interface:
1. Go to JSONBIN.io and click Quick Create JSON.
2. Enter a name for the JSON file and select when it expires.
3. Copy in the following JSON then click Create Bin:
{
"addresses": [
{
"name": "ip_address",
"value": [
"172.16.200.1-172.16.200.254",
"192.168.4.1-192.168.4.254"
],
"description": "generic object IP Address"
},
{
"name": "mac_address",
"value": [
"00:0c:29:1b:40:c9",
"00:0c:29:f6:0d:49",
"00:0c:29:63:40:09"
],
"description": "generic object MAC Address"
}
]
}
4. Copy the generated Access URL.
To create and test a generic connector that uses the external feed update method in the GUI:
1. On the FortiGate, go to Security Fabric > External Connectors and click Create New.
2. Enter a name for the connector, such as gen_obj_range.
3. Set Update method to External feed.
4. Set the URL of external resource to the Access URL copied from JSONBIN.io.
5. In the JSON Mapping, change the Path to address object to record.addresses.
FortiOS 7.6.2 Administration Guide 3830
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,830
|
Fortinet Security Fabric
6. Click OK.
The connector imports the IP and MAC addresses and automatically creates address objects on the FortiGate. The
address object names are a combination of the connector name and the name of the content, for example gen_obj_
range_ip_address.
7. Edit the address object then select View Matched Addresses from the right side bar, or hover over the object name
then select View Matched Addresses in the popup message.
FortiOS 7.6.2 Administration Guide 3831
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,831
|
Fortinet Security Fabric
To create a generic connector that uses the external feed update method in the CLI:
1. Create the generic connector:
config system external-resource
edit "gen_obj_range"
set type generic-address
set namespace "gen_obj_range"
set object-array-path "$.record.addresses"
set resource "https://api.jsonbin.io/v3/qs/6748a04dacd3cb34a8b09811"
next
end
2. Check the matched IP addresses:
# show firewall address gen_obj_range_ip_address
config firewall address
edit "gen_obj_range_ip_address"
set uuid 711443a0-a6cc-51ef-9a0c-0db7194a28d7
set type dynamic
set sub-type external-resource
set comment "generic object IP Address"
set obj-tag "ip_address"
set tag-type "classification"
next
end
# diagnose firewall dynamic list gen_obj_range_ip_address
CMDB name: gen_obj_range_ip_address
gen_obj_range_ip_address: ID(88)
RANGE(172.16.200.1-172.16.200.254)
RANGE(192.168.4.1-192.168.4.254)
Total IP dynamic range blocks: 2.
Total IP dynamic addresses: 508.
3. Check the matched MAC addresses:
# show firewall address gen_obj_range_mac_address
config firewall address
edit "gen_obj_range_mac_address"
set uuid 7114802c-a6cc-51ef-c4d3-c98a769ccf33
set type dynamic
set sub-type external-resource
set comment "generic object MAC Address"
set obj-tag "mac_address"
set obj-type mac
FortiOS 7.6.2 Administration Guide 3832
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,832
|
Fortinet Security Fabric
set tag-type "classification"
next
end
# diagnose firewall dynamic list gen_obj_range_mac_address
CMDB name: gen_obj_range_mac_address
gen_obj_range_mac_address: ID(220)
MAC(00:0c:29:1b:40:c9)
MAC(00:0c:29:f6:0d:49)
MAC(00:0c:29:63:40:09)
Total MAC dynamic addresses: 3.
Push API update method example
In this example, an external resource update is pushed to the FortiGate through the FortiGate's REST API. A Linux PC is
connected to the FortiGate and used as the external resource.
To create and test a generic connector that uses the push API update method in the GUI:
1. On the FortiGate, go to Security Fabric > External Connectors and click Create New.
2. Enter a name for the connector, such as gen_push_range.
3. Set Update method to Push API.
4. Click OK.
The External Feed Push API Information pane opens.
FortiOS 7.6.2 Administration Guide 3833
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,833
|
Fortinet Security Fabric
5. Copy the Sample cURL request and edit the entries, such as API key, IP Address, and son on.
In this example, the cURL request is:
curl -k -X POST -H 'Authorization: Bearer xxxxxxxxxxx' --data '{"mkey": "gen_push_
range", "data": {"addresses":[{"name":"ip_address","value":["172.16.200.1-
172.16.200.254","192.168.4.1-192.168.4.254"],"description":"generic object IP Address"},
{"name":"mac_address","value":
["00:0c:29:1b:40:c9","00:0c:29:f6:0d:49","00:0c:29:63:40:09"],"description":"generic
object MAC Address"}]}}' "https://172.16.116.210:48182/api/v2/monitor/system/externalresource/generic-address"
6. Send the JSON request to the FortiGate through the Linux PC.
The connector imports the IP and MAC addresses and automatically creates address objects on the FortiGate. The
address object names are a combination of the connector name and the name of the content, for example gen_obj_
push_ip_address.
7. Edit the address object then select View Matched Addresses from the right side bar, or hover over the object name
then select View Matched Addresses in the popup message.
FortiOS 7.6.2 Administration Guide 3834
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,834
|
Fortinet Security Fabric
To create and test a generic connector that uses the push API update method in the CLI:
1. Create the generic connector:
config system external-resource
edit "gen_push_range"
set type generic-address
set namespace "gen_push_range"
set update-method push
set comments "test gen_push_range"
next
end
2. Send the JSON request to the FortiGate through the Linux client used in this example.
curl -k -X POST -H 'Authorization: Bearer xxxxxxxxxxx' --data '{"mkey": "gen_push_
range", "data": {"addresses":[{"name":"ip_address","value":["172.16.200.1-
172.16.200.254","192.168.4.1-192.168.4.254"],"description":"generic object IP Address"},
{"name":"mac_address","value":
["00:0c:29:1b:40:c9","00:0c:29:f6:0d:49","00:0c:29:63:40:09"],"description":"generic
object MAC Address"}]}}' "https://172.16.116.210:48182/api/v2/monitor/system/externalresource/generic-address"
3. Check the matched IP addresses:
# show firewall address gen_push_range_ip_address
config firewall address
edit "gen_push_range_ip_address"
set uuid b2012094-ac5e-51ef-354d-cd13120322c4
set type dynamic
set sub-type external-resource
set comment "generic object IP Address"
FortiOS 7.6.2 Administration Guide 3835
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,835
|
Fortinet Security Fabric
set obj-tag "ip_address"
set tag-type "classification"
next
end
# diagnose firewall dynamic list gen_push_range_ip_address
CMDB name: gen_push_range_ip_address
gen_push_range_ip_address: ID(254)
RANGE(172.16.200.1-172.16.200.254)
RANGE(192.168.4.1-192.168.4.254)
Total IP dynamic range blocks: 2.
Total IP dynamic addresses: 508.
4. Check the matched MAC addresses:
# show firewall address gen_push_range_mac_address
config firewall address
edit "gen_push_range_mac_address"
set uuid b2015c62-ac5e-51ef-75ef-8bc7586e5238
set type dynamic
set sub-type external-resource
set comment "generic object MAC Address"
set obj-tag "mac_address"
set obj-type mac
set tag-type "classification"
next
end
# diagnose firewall dynamic list gen_push_range_mac_address
CMDB name: gen_push_range_mac_address
gen_push_range_mac_address: ID(98)
MAC(00:0c:29:1b:40:c9)
MAC(00:0c:29:f6:0d:49)
MAC(00:0c:29:63:40:09)
Total MAC dynamic addresses: 3.
Monitoring the Security Fabric using FortiExplorer for Apple TV
FortiExplorer for Apple TV allows you to use a TV screen to monitor your entire Security Fabric.
FortiExplorer for Apple TV is an analysis tool that provides easy to use NOC and SOC monitoring capabilities. The app
features real-time data traffic, visual alerts, as well as a general overview of hardware devices, operating systems, and
interfaces. The monitor also provides a wireless health summary of your entire network across multiple buildings. If an
access point goes offline, you will be notified about the network's health. After the issues are resolved, you will
immediately see the health update on your screen.
FortiOS 7.6.2 Administration Guide 3836
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,836
|
Fortinet Security Fabric
Getting started with FortiExplorer for Apple TV
Download FortiExplorer for Apple TV from the app store on Apple TV. After the app is installed, add devices using the
Apple TV remote or by sharing a login profile with FortiExplorer. Once the devices are added, you can use FortiExplorer
for Apple TV to view real-time data in the Network Operations Center, Security Operations Center, and Software-Defined
Branch.
To get started with FortiExplorer for Apple TV:
1. Download the app and add devices to FortiExplorer for Apple TV.
You can add devices by sharing a login profile with FortiExplorer or logging into the device directly on FortiExplorer
for Apple TV.
2. View the physical topology of the Fabric to identify risks
3. View the Fabric components as seen on the root FortiGate.
4. View an executive summary of the three largest areas of security focus in the Security Fabric.
5. View data collected by FortiAnalyzer on the endpoints on your network.
6. View vulnerability data collected by FortiClient EMS.
7. Use the Software-Defined Branch module to monitor interface SD-WAN usage and associated service level
agreements.
NOC and SOC example
In this example, you have configured your FortiGates, FortiAnalyzer and other devices in your Security Fabric. Now you
want to use FortiExplorer for Apple TV to display the status of the devices on a TV in your Network Operation Center or
Security Operation Center.
FortiOS 7.6.2 Administration Guide 3837
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,837
|
Fortinet Security Fabric
Topology
This topology has a Headquarter and two Branches. Within the Headquarter is the Enterprise Core and two FortiGates
acting as ISFWs. In addition, an on-premise FortiAnalyzer collects all logging information from the Fabric devices. The
FortiClient EMS manages all the endpoints within the topology.
The two branches are configured with SD-WAN with VPN overlays to the Enterprise Core. Traffic is steered towards the
overlays and underlays based on SD-WAN Rules.
Using FortiExplorer for Apple TV, you will be able to monitor the different components in this topology.
To take advantage of the views in the FortiExplorer for Apple TV, you should configure:
l Security Fabric on all FortiGates. See Configuring the root FortiGate and downstream FortiGates on page 3442.
l FortiAnalyzer Logging. See Configuring FortiAnalyzer on page 3451.
l FortiClient EMS. See Configuring FortiClient EMS on page 3462
Adding the root FortiGate to FortiExplorer for Apple TV
By adding the root FortiGate, you can view the entire topology and navigate to branch FortiGates in the SD-WAN view. If
you are already using FortiExplorer on a mobile device, you can connect the same FortiGate device to Apple TV by
sharing the login credentials on both devices. Alternatively, you can manually connect to your root FortiGate directly from
the app.
To share login credentials between FortiExplorer and FortiExplorer for Apple TV:
1. Connect the FortiExplorer and FortiExplorer for Apple TV devices to the same network.
2. On FortiExplorer for Apple TV, click New FortiGate.
3. In FortiExplorer, go to My Fabric.
FortiOS 7.6.2 Administration Guide 3838
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,838
|
Fortinet Security Fabric
4. Swipe right on the device you want to share, and tap Share Login Profile.
5. Tap Share to Apple TV.
FortiOS 7.6.2 Administration Guide 3839
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,839
|
Fortinet Security Fabric
6. On Apple TV, click Accept. FortiExplorer for Apple TV confirms the request and proceeds to the device main menu.
To add devices to FortiExplorer for Apple TV:
1. In the Devices menu, click New FortiGate. The Login to FortiGate dialog box is displayed.
2. In the IP Address/Host Name field, take one of the following actions:
l Enter the device IP address and port, if not using the default admin port 443
l Enter the full host name including the domain. Enter port if not using the default admin port 443.
3. Enter the Username and Password for the FortiGate device.
4. Click Remember to save time entering the login credentials later.
FortiOS 7.6.2 Administration Guide 3840
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,840
|
Fortinet Security Fabric
5. Click Login. The device is added to FortiExplorer for Apple TV.
If the IP or hostname is not defined in the CN or SAN field of your certificate, you will
receive a prompt that "Your connection is not private". You may choose to continue with
your connection.
Viewing the Fabric Topology monitor
Use the Fabric Topology monitor to view the physical topology of the Fabric to identify risks. FortiGate devices with
version 6.4. and above can drilldown further to see additional information for devices such as FortiGates, FortiAPs, and
FortiSwitches.
To view the Fabric Topology monitor, go to Network Operations Center > Fabric Topology. This monitor displays the
same information as the Physical Topology on the FortiGate
FortiOS 7.6.2 Administration Guide 3841
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,841
|
Fortinet Security Fabric
Use your remote to navigate through the devices in the Fabric topology. Click a device to view the drilldown information.
To return to the default view, click the Menu button.
Viewing the Fabric Overview monitor
Use the Fabric Overview monitor to view the Fabric components as seen on the Dashboard of the Fabric Root FortiGate
in the example topology. Each device must be authorized and be part of the Fabric.
For information about configuring the Security Fabric, see Fortinet Security Fabric on page 3437
To view the Fabric Overview monitor, go to Network Operations Center > Fabric Overview.
FortiOS 7.6.2 Administration Guide 3842
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,842
|
Fortinet Security Fabric
The Security Fabric monitor has multiple panes. To see data populated on the panes, ensure that proper configurations
are applied on the Fabric devices:
Pane Description Configuration
Fabric Connectors Displays external SDN connectors that are
enabled.
Configure Security Fabric > External
Connectors.
Security Fabric
Overview
Displays the number of devices in the
topology.
Configure Security Fabric > Fabric
Connectors.
Attack Surface Displays devices detected by the FortiGate
with a server tag.
Ensure Device Detection is configured on the
interfaces(s). Go to Network > Interfaces.
Device Inventory Displays devices based on Hardware Vendor
and detected OS
Ensure Device Detection is configured on the
interface(s). Go to Network > Interfaces.
Endpoint Coverage Displays the number of online devices and
the percentage of Unscanned, Vulnerable,
and Secured devices.
Ensure Device Detection is configured on the
interface(s). Vulnerability scan results come
from FortiClient EMS. Go to Network >
Interfaces.
Device related information only corresponds to devices local to the FortiGate. Device
information from downstream FortiGates do not propagate to the Upstream FortiGate.
FortiOS 7.6.2 Administration Guide 3843
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,843
|
Fortinet Security Fabric
Viewing the Security Rating monitor
The Security Rating monitor is separated into three major scorecards: Security Posture, Fabric Coverage, and
Optimization, which provide an executive summary of the three largest areas of security focus in the Security Fabric.
To see the Security Rating summary, the root FortiGate and all FortiGates within the Fabric should have the proper
FortiGuard Surface Attack Security Rating license. Security rating is performed on the root FortiGate. Its reports are
generated periodically.
To view the Security Rating monitor, go to Network Operations Center > Security Rating.
The scorecards show an overall score of the performance and sub-categories. The point score represents the net score
for all passed and failed items in that area.
For more information about the Security Rating score, see Security Fabric score on page 3599.
Viewing the Compromised Hosts monitor
The Compromised Hosts monitor leverages the data collected by FortiAnalyzer on the endpoints on your network. To
see compromised hosts, the FortiAnalyzer must have a FortiGuard Indicators of Compromise license. The IOC service
helps identify compromised hosts based on infected websites that it may have visited.
This monitor captures the same information as seen on the Compromised Hosts monitor on the FortiGate.
FortiOS 7.6.2 Administration Guide 3844
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,844
|
Fortinet Security Fabric
To view the Compromised Hosts monitor:
1. Go to Security Operations Center > Compromised Hosts.
2. In the left-hand pane, scroll through the user list. The monitor displays three panes:
l The User Information pane displays the user's contact information and IP address.
l The Topology View pane displays the user's location in the topology.
l The Verdict View pane displays the Malware, Detected Method, and Security Action.
Viewing the Vulnerability Monitor
The Vulnerability Monitor obtains data from FortiClient EMS. It displays vulnerabilities detected by the FortiClient
endpoint, categorized into Critical, High, Medium and Low risk. In this example, an on-premise FortiClient EMS is
connected on the root FortiGate’s Fabric Connector.
This monitor captures the same information as seen on the Top Vulnerable Endpoint Devices monitor on the FortiGate.
FortiOS 7.6.2 Administration Guide 3845
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,845
|
Fortinet Security Fabric
To view the Vulnerability Monitor:
1. Go to Security Operations Center > Vulnerability Monitor. The monitor displays a user list and their vulnerabilities.
2. Use your remote to scroll through the user list. The vulnerability details are displayed on the right side of the monitor.
l The User Information pane displays the user's contact details and IP address.
l The Vulnerability Summary pane displays the number of vulnerabilities categorized into Critical, High, Medium
and Low risk.
l The Topology View pane displays the user's location in the topology.
l The Top Vulnerabilities pane displays the top vulnerabilities by severity.
Using the SD-WAN monitor
In the example topology, the branches are configured to use SD-WAN. You can use the top-right navigation menu in the
SD-WAN monitor to navigate to the Branch FortiGate to display information about the SD-WAN.
To view the SD-WAN monitor, go to Software-Defined Branch > SD-WAN Monitor.
The SD-WAN monitor summarizes the SD-WAN members, Zones, SD-WAN Rules and health checks deployed on the
FortiGate. It shows the interface member's SD-WAN usage and its associated service level agreements. The monitor
contains a chart that shows if the ports are meeting the SLA target for bandwidth, jitter and latency per the health check
in use in each SD-WAN Rule.
FortiOS 7.6.2 Administration Guide 3846
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,846
|
Fortinet Security Fabric
Some of the SD-WAN statistics are only available in FOS 6.4.1 and higher.
To view SD-WAN usage charts:
1. In the SD-WAN Overview area, Use your remote to select the SD-WAN Usage pane.
2. Scroll left and right to view Bandwidth, Volume and Sessions charts for the VIRTUAL-WAN-LINK and Underlay
interfaces in the SD-WAN Zones pane.
To view SLA targets:
1. In the SD-WAN Rules area, use your remote to scroll the rules pane at the left-side of the monitor.
l The Destinations pane displays the destination details.
l The Performance SLA pane displays the SLA targets for the rule.
l The SD-WAN Active Interface pane displays a checkmark next to the active interface.
FortiOS 7.6.2 Administration Guide 3847
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,847
|
Fortinet Security Fabric
2. Use your remote to navigate between the Latency, Jitter, and Packet Loss charts.
To view a branch in the topology:
1. Use your remote to swipe to the top navigation in the monitor. Wait for the topology to load.
2. At the top-right of the monitor, select the current device.
3. Select the device you want to view.
Troubleshooting
The following topics provide troubleshooting information for the Fortinet Security Fabric:
FortiOS 7.6.2 Administration Guide 3848
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,848
|
Fortinet Security Fabric
l Viewing a summary of all connected FortiGates in a Security Fabric on page 3849
l Diagnosing automation stitches on page 3851
Viewing a summary of all connected FortiGates in a Security Fabric
In downstream FortiGates, the diagnose sys csf global command shows a summary of all of the connected
FortiGates in the Security Fabric.
To view a Security Fabric summary on a downstream FortiGate:
# diagnose sys csf global
Current vision:
[
{
"path":"FGVM01TM19000001",
"mgmt_ip_str":"104.196.102.183",
"mgmt_port":10403,
"sync_mode":1,
"saml_role":"identity-provider",
"admin_port":443,
"serial":"FGVM01TM19000001",
"host_name":"admin-root",
"firmware_version_major":6,
"firmware_version_minor":2,
"firmware_version_patch":0,
"firmware_version_build":1010,
"subtree_members":[
{
"serial":"FGVM01TM19000002"
},
{
"serial":"FGVM01TM19000003"
},
{
"serial":"FGVM01TM19000004"
},
{
"serial":"FGVM01TM19000005"
}
]
},
{
"path":"FGVM01TM19000001:FGVM01TM19000002",
"mgmt_ip_str":"104.196.102.183",
"mgmt_port":10423,
"sync_mode":1,
"saml_role":"service-provider",
"admin_port":443,
"serial":"FGVM01TM19000002",
"host_name":"Branch_Office_01",
"firmware_version_major":6,
"firmware_version_minor":2,
"firmware_version_patch":0,
"firmware_version_build":1010,
FortiOS 7.6.2 Administration Guide 3849
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,849
|
Fortinet Security Fabric
"upstream_intf":"Branch-HQ-A",
"upstream_serial":"FGVM01TM19000001",
"parent_serial":"FGVM01TM19000001",
"parent_hostname":"admin-root",
"upstream_status":"Authorized",
"upstream_ip":22569994,
"upstream_ip_str":"10.100.88.1",
"subtree_members":
[
],
"is_discovered":true,
"ip_str":"10.0.10.2",
"downstream_intf":"To-HQ-A",
"idx":1
},{
"path":"FGVM01TM19000001:FGVM01TM19000003",
"mgmt_ip_str":"104.196.102.183",
"mgmt_port":10407,
"sync_mode":1,
"saml_role":"service-provider",
"admin_port":443,
"serial":"FGVM01TM19000003",
"host_name":"Enterprise_Second_Floor",
"firmware_version_major":6,
"firmware_version_minor":2,
"firmware_version_patch":0,
"firmware_version_build":1010,
"upstream_intf":"port3",
"upstream_serial":"FGVM01TM19000001",
"parent_serial":"FGVM01TM19000001",
"parent_hostname":"admin-root",
"upstream_status":"Authorized",
"upstream_ip":22569994,
"upstream_ip_str":"10.100.88.1",
"subtree_members":
[
],
"is_discovered":true,
"ip_str":"10.100.88.102",
"downstream_intf":"port1",
"idx":2
},{
"path":"FGVM01TM19000001:FGVM01TM19000004",
"mgmt_ip_str":"104.196.102.183",
"mgmt_port":10424,
"sync_mode":1,
"saml_role":"service-provider",
"admin_port":443,
"serial":"FGVM01TM19000004",
"host_name":"Branch_Office_02",
"firmware_version_major":6,
"firmware_version_minor":2,
"firmware_version_patch":0,
"firmware_version_build":1010,
"upstream_intf":"HQ-MPLS",
"upstream_serial":"FGVM01TM19000001",
FortiOS 7.6.2 Administration Guide 3850
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,850
|
Fortinet Security Fabric
"parent_serial":"FGVM01TM19000001",
"parent_hostname":"admin-root",
"upstream_status":"Authorized",
"upstream_ip":22569994,
"upstream_ip_str":"10.100.88.1",
"subtree_members":[
],
"is_discovered":true,
"ip_str":"10.0.12.3",
"downstream_intf":"To-HQ-MPLS",
"idx":3
},
{
"path":"FGVM01TM19000001:FGVM01TM19000005",
"mgmt_ip_str":"104.196.102.183",
"mgmt_port":10404,
"sync_mode":1,
"saml_role":"service-provider",
"admin_port":443,
"serial":"FGVM01TM19000005",
"host_name":"Enterprise_First_Floor",
"firmware_version_major":6,
"firmware_version_minor":2,
"firmware_version_patch":0,
"firmware_version_build":1010,
"upstream_intf":"port3",
"upstream_serial":"FGVM01TM19000001",
"parent_serial":"FGVM01TM19000001",
"parent_hostname":"admin-root",
"upstream_status":"Authorized",
"upstream_ip":22569994,
"upstream_ip_str":"10.100.88.1",
"subtree_members":[
],
"is_discovered":true,
"ip_str":"10.100.88.101",
"downstream_intf":"port1",
"idx":4
}
]
Diagnosing automation stitches
Diagnose commands are available to:
l Test an automation stitch
l Enable or disable log dumping for automation stitches
l Display the settings of every automation stitch
l Display statistics on every automation stitch
To test an automation stitch:
diagnose automation test <automation-stitch-name>
Example:
FortiOS 7.6.2 Administration Guide 3851
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,851
|
Fortinet Security Fabric
# diagnose automation test HA-failover
automation test is done. stitch:HA-failover
To toggle log dumping:
diagnose test application autod 1
Examples:
# diagnose test application autod 1
autod log dumping is enabled
# diagnose test application autod 1
autod log dumping is disabled
autod logs dumping summary:
autod dumped total:7 logs, num of logids:4
To display the settings for all of the automation stitches:
diagnose test application autod 2
Example:
# diagnose test application autod 2
csf: enabled root:yes
total stitches activated: 3
stitch: Compromised-IP-Banned
destinations: all
trigger: Compromised-IP-Banned
local hit: 0 relayed to: 0 relayed from: 0
actions:
Compromised-IP-Banned_ban-ip type:ban-ip interval:0
stitch: HA-failover
destinations: HA-failover_ha-cluster_25;
trigger: HA-failover
local hit: 0 relayed to: 0 relayed from: 0
actions:
HA-failover_email type:email interval:0
subject: HA Failover
mailto:admin@example.com;
stitch: rebooot
destinations: all
trigger: reboot
local hit: 0 relayed to: 0 relayed from: 0
actions:
action1 type:alicloud-function interval:0
delay:1 required:yes
Account ID: id
Region: region
Function domain: fc.aliyuncs.com
Version: versoin
FortiOS 7.6.2 Administration Guide 3852
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,852
|
Fortinet Security Fabric
Service name: serv
Function name: funcy
headers:
To display statistic on all of the automation stitches:
diagnose test application autod 3
Example:
stitch: Compromised-IP-Banned
local hit: 0 relayed to: 0 relayed from: 0
last trigger:Wed Dec 31 20:00:00 1969
last relay:Wed Dec 31 20:00:00 1969
actions:
Compromised-IP-Banned_ban-ip:
done: 1 relayed to: 0 relayed from: 0
last trigger:Wed Dec 31 20:00:00 1969
last relay:
stitch: HA-failover
local hit: 0 relayed to: 0 relayed from: 0
last trigger:Thu May 24 11:35:22 2018
last relay:Thu May 24 11:35:22 2018
actions:
HA-failover_email:
done: 1 relayed to: 1 relayed from: 1
last trigger:Thu May 24 11:35:22 2018
last relay:Thu May 24 11:35:22 2018
stitch: rebooot
local hit: 2 relayed to: 1 relayed from: 1
last trigger:Fri May 3 13:30:56 2019
last relay:Fri May 3 13:30:23 2019
actions:
action1
done: 1 relayed to: 0 relayed from: 0
last trigger:Fri May 3 13:30:56 2019
last relay:
logid2stitch mapping:
id:20103 local hit: 0 relayed to: 0 relayed from: 0
License Expiry
lambada
id:32138 local hit: 2 relayed to: 1 relayed from: 1
Compromised-IP-Banned
HA-failover
rebooot
action run cfg&stats:
total:2 cur:0 done:1 drop:1
email:
flags:10
stats: total:1 cur:0 done:1 drop:0
fortiexplorer-notification:
flags:1
FortiOS 7.6.2 Administration Guide 3853
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,853
|
Fortinet Security Fabric
stats: total:0 cur:0 done:0 drop:0
alert:
flags:0
stats: total:0 cur:0 done:0 drop:0
disable-ssid:
flags:7
stats: total:0 cur:0 done:0 drop:0
quarantine:
flags:7
stats: total:0 cur:0 done:0 drop:0
quarantine-forticlient:
flags:4
stats: total:0 cur:0 done:0 drop:0
quarantine-nsx:
flags:4
stats: total:0 cur:0 done:0 drop:0
ban-ip:
flags:7
stats: total:0 cur:0 done:0 drop:0
aws-lambda:
flags:11
stats: total:0 cur:0 done:0 drop:0
webhook:
flags:11
stats: total:0 cur:0 done:0 drop:0
cli-script:
flags:10
stats: total:0 cur:0 done:0 drop:0
azure-function:
flags:11
stats: total:1 cur:0 done:0 drop:1
google-cloud-function:
flags:11
stats: total:0 cur:0 done:0 drop:0
alicloud-function:
flags:11
stats: total:0 cur:0 done:0 drop:0
FortiOS 7.6.2 Administration Guide 3854
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,854
|
Log and Report
Logging and reporting are useful components to help you understand what is happening on your network, and to inform
you about certain network activities, such as the detection of a virus, a visit to an invalid website, an intrusion, a failed log
in attempt, and myriad others.
Logging records the traffic that passes through, starts from, or ends on the FortiGate, and records the actions the
FortiGate took during the traffic scanning process. After this information is recorded in a log message, it is stored in a log
file that is stored on a log device (a central storage location for log messages). FortiGate supports sending all log types to
several log devices, including FortiAnalyzer, FortiAnalyzer Cloud, FortiGate Cloud, and syslog servers. Approximately
5% of memory is used for buffering logs sent to FortiAnalyzer. The FortiGate system memory and local disk can also be
configured to store logs, so it is also considered a log device. See Log settings and targets on page 3870 for more
information.
Reports show the recorded activity in a more readable format. A report gathers all the log information that it needs, then
presents it in a graphical format with a customizable design and automatically generated charts showing what is
happening on the network. Reports can be generated on FortiGate devices with disk logging and on FortiAnalyzer
devices.
FortiView is a more comprehensive network reporting and monitoring tool. It integrates real-time and historical data into
a single view in FortiOS. For more information, see FortiView monitors on page 141.
Performance statistics are not logged to disk. Performance statistics can be received by a
syslog server or by FortiAnalyzer.
The following topics provide information about logging and reporting:
l Viewing event logs on page 3855
l System Events log page on page 3858
l Security Events log page on page 3863
l Reports page on page 3866
l Log settings and targets on page 3870
l Logging to FortiAnalyzer on page 3875
l Advanced and specialized logging on page 3886
l Sample logs by log type on page 3917
l Troubleshooting on page 3938
Viewing event logs
Event log subtypes are available on the Log & Report > System Events page. Not all of the event log subtypes are
available by default. See System Events log page on page 3858 for more information.
FortiOS 7.6.2 Administration Guide 3855
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.