index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,555
|
Fortinet Security Fabric
set allowaccess ping https ssh http fgfm fabric
...
next
end
Downstream FortiGate 2 (Level2-downstream-H)
To configure Level2-downstream-H in the GUI:
1. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
2. In the Settings tab, set the Security Fabric role to Join Existing Fabric.
3. Enter the Upstream FortiGate IP, which is the IP of the root VDOM on Downstream-G (192.168.71.7).
4. Configure the other settings as needed.
5. Click OK.
To configure Level2-downstream-H in the CLI:
config system csf
set status enable
set upstream-ip 192.168.71.7
end
Downstream FortiGate 3 (Level1-downstream-10)
To configure Level1-downstream-10 in the GUI:
1. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
2. In the Settings tab, set the Security Fabric role to Join Existing Fabric.
FortiOS 7.6.2 Administration Guide 3556
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,556
|
Fortinet Security Fabric
3. Enter the Upstream FortiGate IP, which is the IP of the root VDOM on Root-E (192.168.9.5).
4. Configure the other settings as needed.
5. Click OK.
To configure Level1-downstream-10 in the CLI:
config system csf
set status enable
set upstream-ip 192.168.9.5
end
Device authorization and verification
To authorize the downstream devices on the root FortiGate:
1. On Root-E, go to System > Firmware & Registration.
2. Select the unauthorized device and click Authorization > Authorize for each downstream FortiGate.
Once all the devices are authorized, the physical topology page shows the root and downstream FortiGates. The
logical topology page shows the root and downstream FortiGates connected to interfaces in their corresponding
VDOMs.
Other Security Fabric topics
The following topics provide instructions on configuring other Security Fabric use cases:
l Synchronizing objects across the Security Fabric on page 3558
l Group address objects synchronized from FortiManager on page 3564
l Security Fabric over IPsec VPN on page 3566
l Leveraging LLDP to simplify Security Fabric negotiation on page 3572
l Integrate user information from EMS and Exchange connectors in the user store on page 3574
FortiOS 7.6.2 Administration Guide 3557
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,557
|
Fortinet Security Fabric
Synchronizing objects across the Security Fabric
When the Security Fabric is enabled, various objects such as addresses, services, and schedules are synced from the
upstream FortiGate to all downstream devices by default. FortiOS has the following settings for object synchronization
across the Security Fabric:
l Set object synchronization (fabric-object-unification) to default or local on the root FortiGate.
l Set a per object option to toggle whether the specific Fabric object will be synchronized or not. After upgrading from
6.4.3, this option is disabled for supported Fabric objects. The synchronized Fabric objects are kept as locally
created objects on downstream FortiGates.
l Define the number of task workers to handle synchronizations.
The firewall object synchronization wizard helps identify objects that are not synchronized and resolves any conflicts. A
warning message appears in the topology tree if there is a conflict.
Summary of CLI commands
To configure object synchronization:
config system csf
set fabric-object-unification {default | local}
set configuration-sync {default | local}
set fabric-workers <integer>
end
Parameter Description
fabric-object-unification default: Global CMDB objects will be synchronized in the Security Fabric.
local: Global CMDB objects will not be synchronized to and from this device.
This command is available on the root FortiGate. If set to local, the device does
not synchronize objects from the root, but will send the synchronized objects
downstream.
configuration-sync default: Synchronize configuration for FortiAnalyzer, FortiSandbox, and Central
Management to root node.
local: Do not synchronize configuration with root node.
If downstream FortiGates are set to local, the synchronized objects from the root
to downstream are not applied locally. However, the downstream FortiGate will
send the configuration to lower FortiGates.
fabric-workers Define how many task worker process are created to handle synchronizations (1-
4, default = 2). The worker processes dies if there is no task to perform after 60
seconds.
The per object setting can be configured on the root FortiGate as follows:
config firewall <object>
edit <name>
set fabric-object {enable | disable}
next
end
Where:
FortiOS 7.6.2 Administration Guide 3558
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,558
|
Fortinet Security Fabric
l <object> is one of the following: address, address6, addrgrp, addrgrp6, service category, service
custom, service group, schedule group, schedule onetime, or schedule recurring.
l Enabling fabric-object sets the object as a Security Fabric-wide global object that is synchronized to
downstream FortiGates.
l Disabling fabric-object sets the object as local to this Security Fabric member.
l If a device in the Fabric is in multi-VDOM mode, the GUI will not display the Fabric synchronization option. Even if
this is enabled in the CLI, the object will not be synchronized to any downstream devices.
Sample topology
In this Security Fabric, the root FortiGate (FGTA-1) has fabric-object-unification set to default so the Fabric
objects can be synchronized to the downstream FortiGate. The level 1 downstream FortiGate (FGTB-1) has
configuration-sync set to local, so it will not apply the synchronized objects locally. The level 2 downstream
FortiGate (FGTC) has configuration-sync set to default, so it will apply the synchronized objects locally.
In this example, firewall addresses and address groups are used. Other supported Fabric objects have the same
behaviors. The following use cases illustrate common synchronization scenarios:
l If no conflicts exist, firewall addresses and address groups can be synchronized to downstream FortiGates (see
example below).
l If a conflict exists between the root and downstream FortiGates, it can be resolved with the conflict resolution
wizard. After the conflict is resolved, the firewall addresses and address groups can be synchronized to
downstream FortiGates (see example below).
l If set fabric-object (Fabric synchronization option in the GUI) is disabled for firewall addresses and address
groups on the root FortiGate, they will not be synchronized to downstream FortiGates (see example below).
To configure the FortiGates used in this example:
FGTA-1 # config system csf
set status enable
set group-name "fabric"
set fabric-object-unification default
...
end
FGTB-1 # config system csf
set status enable
set upstream-ip 10.2.200.1
set configuration-sync local
...
end
FGTC # config system csf
set status enable
set upstream-ip 192.168.7.2
set configuration-sync default
FortiOS 7.6.2 Administration Guide 3559
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,559
|
Fortinet Security Fabric
...
end
To synchronize a firewall address and address group in the Security Fabric:
1. Configure the firewall address on the root FortiGate:
FGTA-1 # config firewall address
edit "add_subnet_1"
set fabric-object enable
set subnet 22.22.22.0 255.255.255.0
next
end
2. Configure the address group on the root FortiGate:
FGTA-1 # config firewall addrgrp
edit "group_subnet_1"
set member "add_subnet_1"
set fabric-object enable
next
end
3. Check the firewall address and address group on the downstream FortiGates:
FGTB-1 # show firewall address add_subnet_1
entry is not found in table
FGTB-1 # show firewall addrgrp group_subnet_1
entry is not found in table
The synchronized objects are not applied locally on this FortiGate because configuration-sync is set to
local.
FGTC # show firewall address add_subnet_1
config firewall address
edit "add_subnet_1"
set uuid 378a8094-34cb-51eb-ce40-097f298fcfdc
set fabric-object enable
set subnet 22.22.22.0 255.255.255.0
next
end
FGTC # show firewall addrgrp group_subnet_1
config firewall addrgrp
edit "group_subnet_1"
set uuid 4d7a8a52-34cb-51eb-fce7-d93f76915319
set member "add_subnet_1"
set color 19
set fabric-object enable
next
end
The objects are synchronized on this FortiGate because configuration-sync is set to default.
FortiOS 7.6.2 Administration Guide 3560
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,560
|
Fortinet Security Fabric
To resolve a firewall address and address group conflict in the Security Fabric:
1. On FGTC, create a firewall address:
a. Go to Policy & Objects > Addresses and select Address.
b. Click Create new.
c. Configure the following:
Name sync_add_1
IP/Netmask 33.33.33.0 255.255.255.0
d. Click OK.
2. On FGTA-1 (Fabric root), create the firewall address with same name but a different subnet:
a. Go to Policy & Objects > Addresses and select Address.
b. Click Create new.
c. Configure the following:
Name sync_add_1
IP/Netmask 11.11.11.0 255.255.255.0
Fabric synchronization Enable
d. Click OK.
3. Add the address to a different address group than what is configured on FGTC:
a. Go to Policy & Objects > Addresses and select Address Group.
b. Click Create new.
c. Configure the following:
Name sync_group4
Members sync_add_1
Fabric synchronization Enable
d. Click OK.
4. Open the notification center drop dropdown. There is a message that 1 Firewall object is conflict with other
FortiGates in the fabric.
5. Resolve the conflict:
a. Click the message in the notification center drop dropdown. The Firewall Object Synchronization pane opens.
b. Click Rename All Objects. The conflicted object will be renamed on the downstream FortiGate.
FortiOS 7.6.2 Administration Guide 3561
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,561
|
Fortinet Security Fabric
c. The conflict is resolved. Click Close to exit the Firewall Object Synchronization pane.
6. Verify the results on the downstream FortiGates:
a. On FGTB-1, go to Policy & Objects > Addresses.
b. Search for sync_add_1 and sync_group4 in the Address and Group Address pages, respectively. No results
are found. The synchronized objects are not applied locally on this FortiGate because configuration-sync
is set to local.
FortiOS 7.6.2 Administration Guide 3562
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,562
|
Fortinet Security Fabric
c. On FGTC, go to Policy & Objects > Addresses.
d. Search for sync_add_1 in the Address page. The original firewall address sync_add_1 was renamed to sync_
add_1_FGTC by resolving the conflict on FGTA-1. The address sync_add_1 and address group sync_group4
are synchronized from FGTA-1.
To disable Fabric synchronization on the root FortiGate in the GUI:
1. On FGTA-1, create a firewall address:
a. Go to Policy & Objects > Addresses and select Address.
b. Click Create new.
c. Configure the following:
Name add_subnet_3
IP/Netmask 33.33.33.0 255.255.255.0
Fabric synchronization Disable
d. Click OK.
2. Create the firewall address group and add the address:
a. Go to Policy & Objects > Addresses and select Address Group.
b. Click Create new.
c. Configure the following:
Name group_subnet_3
Members add_subnet_3
Fabric synchronization Disable
d. Click OK.
3. On FGTB-1, go to Policy & Objects > Addresses and search for subnet_3. No results are found because Fabric
synchronization is disabled on the root FortiGate (FGTA-1).
4. On FGTC, go to Policy & Objects > Addresses and search for subnet_3. No results are found because Fabric
FortiOS 7.6.2 Administration Guide 3563
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,563
|
Fortinet Security Fabric
synchronization is disabled on the root FortiGate (FGTA-1).
To disable Fabric synchronization on the root FortiGate in the CLI:
1. Configure the firewall address on the root FortiGate:
FGTA-1 # config firewall address
edit "add_subnet_3"
set subnet 33.33.33.0 255.255.255.0
set fabric-object disable
next
end
2. Configure the address group on the root FortiGate:
FGTA-1 # config firewall addrgrp
edit "group_subnet_3"
set member "add_subnet_3"
set fabric-object disable
next
end
3. Check the firewall address and address group on the downstream FortiGates:
FGTB-1 # show firewall address add_subnet_3
entry is not found in table
FGTB-1 # show firewall addrgrp group_subnet_3
entry is not found in table
FGTC # show firewall address add_subnet_3
entry is not found in table
FGTC # show firewall addrgrp group_subnet_3
entry is not found in table
The objects are not synchronized from the root FortiGate (FGTA-1) because the fabric-object setting is
disabled.
Group address objects synchronized from FortiManager
Address objects from external connectors that are learned by FortiManager are synchronized to FortiGate. These
objects can be grouped together with the FortiGate CLI to simplify selecting connector objects in the FortiGate GUI.
Multiple groups can be created.
This option is only available for objects that are synchronized from FortiManager.
To add an object to a connector group:
config user adgrp
edit <object_name>
FortiOS 7.6.2 Administration Guide 3564
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,564
|
Fortinet Security Fabric
set server-name "FortiManager"
set connector-source <group_name>
next
end
Example
In this example, objects learned by the FortiManager from an Aruba ClearPass device are synchronized to the FortiGate.
Some of the objects are then added to a group called ClearPass to make them easier to find in the object list when
creating a firewall policy.
Prior to being grouped, the synchronized objects are listed under the FortiManager heading in the object lists.
To add some of the objects to a group:
config user adgrp
edit "cp_test_FSSOROLE"
set server-name "FortiManager"
set connector-source "ClearPass"
next
edit "cp_test_[AirGroup v2]"
set server-name "FortiManager"
set connector-source "ClearPass"
next
end
The objects are now listed under the ClearPass heading.
FortiOS 7.6.2 Administration Guide 3565
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,565
|
Fortinet Security Fabric
Security Fabric over IPsec VPN
This is an example of configuring Security Fabric over IPsec VPN.
Sample topology
This sample topology shows a downstream FortiGate (HQ2) connected to the root FortiGate (HQ1) over IPsec VPN to
join Security Fabric.
Sample configuration
To configure the root FortiGate (HQ1):
1. Configure the interface:
a. Go to Network > Interfaces.
b. Edit port2:
l Set Role to WAN.
l For the interface connected to the internet, set the IP/Network Mask to 10.2.200.1/255.255.255.0
c. Edit port6:
l Set Role to DMZ.
l For the interface connected to FortiAnalyzer, set the IP/Network Mask to 192.168.8.250/255.255.255.0
2. Configure the static route to connect to the internet:
a. Go to Network > Static Routes and click Create New or Create New > IPv4 Static Route.
l Set Destination to 0.0.0.0/0.0.0.0.
l Set Interface to port2.
FortiOS 7.6.2 Administration Guide 3566
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,566
|
Fortinet Security Fabric
l Set Gateway Address to 10.2.200.2.
b. Click OK.
3. Configure the IPsec VPN:
a. Go to VPN > IPsec Wizard.
l Set Name to To-HQ2.
l Set Template Type to Custom.
l Click Next.
l Set Authentication to Method.
l Set Pre-shared Key to 123456.
b. Leave all other fields in their default values and click OK.
4. Configure the IPsec VPN interface IP address which will be used to form Security Fabric:
a. Go to Network > Interfaces.
b. Edit To-HQ2:
l Set Role to LAN.
l Set the IP/Network Mask to 10.10.10.1/255.255.255.255.
l Set Remote IP/Network Mask to 10.10.10.3/255.255.255.0.
5. Configure the IPsec VPN local and remote subnets:
a. Go to Policy & Objects > Addresses.
b. Click Create New
l Set Name to To-HQ2_remote_subnet_2.
l Set Type to Subnet.
l Set IP/Network Mask to 10.10.10.3/32.
c. Click OK.
d. Click Create New
l Set Name to To-HQ2_local_subnet_1.
l Set Type to Subnet.
l Set IP/Network Mask to 192.168.8.0/24.
e. Click OK.
f. Click Create New
l Set Name to To-HQ2_remote_subnet_1.
l Set Type to Subnet.
l Set IP/Network Mask to 10.1.100.0/24.
g. Click OK.
6. Configure the IPsec VPN static routes:
a. Go to Network > Static Routes.
b. Click Create New or Create New > IPv4 Static Route.
l For Named Address, select Type and select To-HQ2_remote_subnet_1.
l Set Interface to To-HQ2.
Click OK.
c. Click Create New or Create New > IPv4 Static Route.
l For Named Address, select Type and select To-HQ2_remote_subnet_1.
l Set Interface to Blackhole.
FortiOS 7.6.2 Administration Guide 3567
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,567
|
Fortinet Security Fabric
l Set Administrative Distance to 254.
d. Click OK.
7. Configure the IPsec VPN policies:
a. Go to Policy & Objects > Firewall Policy
b. Click Create New.
l Set Name to vpn_To-HQ2_local.
l Set Incoming Interface to port6.
l Set Outgoing Interface to To-HQ2.
l Set Source to To-HQ2_local_subnet_1.
l Set Destination to To-HQ2_remote_subnet_1.
l Set Schedule to Always.
l Set Service to All.
l Disable NAT.
c. Click OK.
d. Click Create New.
l Set Name to vpn_To-HQ2_remote.
l Set Incoming Interface to To-HQ2.
l Set Outgoing Interface to port6.
l Set Source to To-HQ2_remote_subnet_1, To-HQ2_remote_subnet_2.
l Set Destination to To-HQ2_local_subnet_1.
l Set Schedule to Always.
l Set Service to All.
l Enable NAT.
l Set IP Pool Configuration to Use Outgoing Interface Address.
e. Click OK.
8. Configure the Security Fabric:
a. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
b. Select the Settings tab, and set the Security Fabric role to Serve as Fabric Root.
c. Enter a Fabric name, such as Office-Security-Fabric.
d. Ensure Allow other Security Fabric devices to join is enabled and add VPN interface To-HQ2.
e. Click OK.
9. Configure the FortiAnalyzer logging settings:
a. Go to Security Fabric > Fabric Connectors and double-click the Logging & Analytics card.
b. Select the Settings tab, select the FortiAnalyzer tab, and set the Status to Enabled.
c. Enter the FortiAnalyzer IP in the Server field (192.168.8.250). The Upload option is automatically set to Real
Time.
d. Click Refresh. The FortiAnalyzer serial number is verified.
e. Click OK.
FortiOS 7.6.2 Administration Guide 3568
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,568
|
Fortinet Security Fabric
To configure the downstream FortiGate (HQ2):
1. Configure the interface:
a. Go to Network > Interfaces.
b. Edit interface wan1:
l Set Role to WAN.
l For the interface connected to the internet, set the IP/Network Mask to 192.168.7.3/255.255.255.0.
c. Edit interface vlan20:
l Set Role to LAN.
l For the interface connected to local endpoint clients, set the IP/Network Mask to
10.1.100.3/255.255.255.0.
2. Configure the static route to connect to the internet:
a. Go to Network > Static Routes and click Create New or Create New > IPv4 Static Route.
l Set Destination to 0.0.0.0/0.0.0.0.
l Set Interface to wan1.
l Set Gateway Address to 192.168.7.2.
b. Click OK.
3. Configure the IPsec VPN:
a. Go to VPN > IPsec Wizard.
l Set VPN Name to To-HQ1.
l Set Template Type to Custom.
l Click Next.
l In the Network IP Address, enter 10.2.200.1.
l Set Interface to wan1.
l Set Authentication to Method.
l Set Pre-shared Key to 123456.
b. Leave all other fields in their default values and click OK.
4. Configure the IPsec VPN interface IP address which will be used to form Security Fabric:
a. Go to Network > Interfaces.
b. Edit To-HQ1:
l Set Role to WAN.
l Set the IP/Network Mask to 10.10.10.3/255.255.255.255.
l Set Remote IP/Network Mask to 10.10.10.1/255.255.255.0.0.
5. Configure the IPsec VPN local and remote subnets:
a. Go to Policy & Objects > Addresses.
b. Click Create New
l Set Name to To-HQ1_local_subnet_1.
l Set Type to Subnet.
l Set IP/Network Mask to 10.1.100.0/24.
c. Click OK.
d. Click Create New
l Set Name to To-HQ1_remote_subnet_1.
l Set Type to Subnet.
FortiOS 7.6.2 Administration Guide 3569
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,569
|
Fortinet Security Fabric
l Set IP/Network Mask to 192.168.8.0/24.
e. Click OK.
6. Configure the IPsec VPN static routes:
a. Go to Network > Static Routes and click Create New or Create New > IPv4 Static Route.
l For Named Address, select Type and select To-HQ1_remote_subnet_1.
l Set Interface to To-HQ1.
b. Click OK.
c. Click Create New or Create New > IPv4 Static Route.
l For Named Address, select Type and select To-HQ1_remote_subnet_1.
l Set Interface to Blackhole.
l Set Administrative Distance to 254.
d. Click OK.
7. Configure the IPsec VPN policies:
a. Go to Policy & Objects > Firewall Policy and click Create New.
l Set Name to vpn_To-HQ1_local.
l Set Incoming Interface to vlan20.
l Set Outgoing Interface to To-HQ1.
l Set Source to To-HQ1_local_subnet_1.
l Set Destination to To-HQ1_remote_subnet_1.
l Set Schedule to Always.
l Set Service to All.
l Disable NAT.
b. Click OK.
c. Click Create New.
l Set Name to vpn_To-HQ1_remote.
l Set Incoming Interface to To-HQ1.
l Set Outgoing Interface to vlan20.
l Set Source to To-HQ1_remote_subnet_1.
l Set Destination to -HQ1_local_subnet_1.
l Set Schedule to Always.
l Set Service to All.
l Disable NAT.
d. Click OK.
8. Configure the Security Fabric:
a. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
b. In the Settings tab, set the Security Fabric role to Join Existing Fabric.
FortiAnalyzer automatically enables logging. FortiAnalyzer settings will be retrieved when the downstream
FortiGate connects to the root FortiGate.
c. Set the Upstream FortiGate IP to 10.10.10.1.
d. Click OK.
FortiOS 7.6.2 Administration Guide 3570
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,570
|
Fortinet Security Fabric
To authorize the downstream FortiGate (HQ2) on the root FortiGate (HQ1):
1. In the root FortiGate (HQ1), go to System > Firmware & Registration.
The table highlights the connected FortiGate with its serial numbers that is unauthorized.
2. Select the unauthorized device and click Authorization > Authorize.
After authorization, the downstream FortiGate (HQ2) appears in the Security Fabric widget. This means the
downstream FortiGate (HQ2) has successfully joined the Security Fabric.
To check the Security Fabric over IPsec VPN:
1. On the root FortiGate (HQ1), go to Security Fabric > Physical Topology.
The root FortiGate (HQ1) is connected by the downstream FortiGate (HQ2) with VPN icon in the middle.
2. On the root FortiGate (HQ1), go to Security Fabric > Logical Topology.
The root FortiGate (HQ1) VPN interface To-HQ2 is connected by downstream FortiGate (HQ2) VPN interface ToHQ1 with VPN icon in the middle.
To run diagnostics:
1. To view the downstream FortiGate pending authorization on root FortiGate (HQ1):
HQ1 # diagnose sys csf authorization pending-list
Serial IP Address HA-Members
Path
------------------------------------------------------------------------------------
FG101ETK18002187 0.0.0.0
FG3H1E5818900718:FG101ETK18002187
2. To view the downstream FortiGate (HQ2) after it joins the Security Fabric:
HQ1 # diagnose sys csf downstream
1: FG101ETK18002187 (10.10.10.3) Management-IP: 0.0.0.0 Management-port:0 parent:
FG3H1E5818900718
path:FG3H1E5818900718:FG101ETK18002187
data received: Y downstream intf:To-HQ1 upstream intf:To-HQ2 admin-port:443
authorizer:FG3H1E5818900718
3. To view the root FortiGate (HQ1) on the downstream FortiGate (HQ2) after joining the Security Fabric:
HQ2 # diagnose sys csf upstream
Upstream Information:
Serial Number:FG3H1E5818900718
IP:10.10.10.1
FortiOS 7.6.2 Administration Guide 3571
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,571
|
Fortinet Security Fabric
Connecting interface:To-HQ1
Connection status:Authorized
Leveraging LLDP to simplify Security Fabric negotiation
LLDP reception is enabled on WAN interfaces, which prompts FortiGates that are joining the Security Fabric if the
upstream FortiGate asks.
l If the interface role is undefined, LLDP reception and transmission inherit settings from the VDOM.
l If the interface role is WAN, LLDP reception is enabled.
l If the interface role is LAN, LLDP transmission is enabled.
When a FortiGate B's WAN interface detects that FortiGate A's LAN interface is immediately upstream (through the
default gateway), and FortiGate A has Security Fabric enabled, FortiGate B will show a notification on the GUI asking to
join the Security Fabric.
To configure LLDP reception and join a Security Fabric in the GUI:
1. On FortiGate A, go to Network > Interfaces.
2. Configure an interface:
l If the interface's role is undefined, under Administrative Access, set Receive LLDP and Transmit LLDP to Use
VDOM Setting.
l If the interface's role is WAN, under Administrative Access, set Receive LLDP to Enable and Transmit LLDP to
Use VDOM Setting.
FortiOS 7.6.2 Administration Guide 3572
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,572
|
Fortinet Security Fabric
l If the interface's role is LAN, under Administrative Access, set Receive LLDP to Use VDOM Setting and
Transmit LLDP to Enable.
3. Click OK. A notification is shown on FortiGate B, You can connect to a Security Fabric via an upstream FortiGate at
10.10.10.1.
4. Click the notification. The Security Fabric Settings page opens. All the required settings automatically configured.
5. Click OK to apply the settings.
To configure LLDP reception and join a Security Fabric in the CLI:
1. Configure the interface on FortiGate A:
l Undefined role
config system interface
edit "port3"
set lldp-reception vdom
set lldp-transmission vdom
set role undefined
...
next
end
l WAN role
FortiOS 7.6.2 Administration Guide 3573
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,573
|
Fortinet Security Fabric
config system interface
edit "wan1"
set lldp-reception enable
set lldp-transmission vdom
set role wan
...
next
end
l LAN role
config system interface
edit "port2"
set lldp-reception vdom
set lldp-transmission enable
set role lan
...
next
end
2. Edit the Security Fabric settings on FortiGate B:
config system csf
set status enable
set upstream-ip 10.2.200.1
end
Integrate user information from EMS and Exchange connectors in the user store
When a FortiClient endpoint is managed by EMS, logged in user and domain information is shared with FortiOS through
the EMS connector. This information can be joined with the Exchange connector to produce more complete user
information in the user store.
The diagnose user-device-store device memory list command displays detailed device information.
FortiOS 7.6.2 Administration Guide 3574
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,574
|
Fortinet Security Fabric
Example
In this example, the FortiClient PC user (test1) logs on to the AD domain (FORTINET-FSSO.COM), which is also the
same domain as the Exchange server. The user information is pushed to the EMS server that the user is registered to.
The FortiGate synchronizes the information from EMS, and at the same time looks up the user on the Exchange server
under the Exchange connector. If the user exists on the Exchange server, additional information is fetched. These
details are combined in the user store, which is visible in the FortiClient widget in the Status dashboard.
To configure the Exchange server:
config user exchange
edit "exchange-140"
set server-name "W2K8-SERV1"
set domain-name "FORTINET-FSSO.COM"
set username "Administrator"
set password ********
next
end
To configure the EMS server:
config endpoint-control fctems
edit "ems133"
set server "172.18.62.12"
set certificate-fingerprint "4F:A6:76:E2:00:4F:A6:76:E2:00:4F:A6:76:E2:00:E0"
FortiOS 7.6.2 Administration Guide 3575
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,575
|
Fortinet Security Fabric
next
end
To view the user information in the GUI:
1. Go to Dashboard > Status.
2. In the FortiClient widget, hover over a device or user name to view the information.
To view the user information in the CLI:
# diagnose user-device-store device memory list
...
Record #13:
device_info
'ipv4_address' = '10.1.100.185'
'mac' = '00:0c:29:11:5b:6b'
'hardware_vendor' = 'VMware'
'vdom' = 'root'
'os_name' = 'Microsoft'
'os_version' = 'Windows 7 Professional Edition, 32-bit Service Pack 1
(build 7601)'
'hostname' = 'win7-5'
'unauth_user' = 'Administrator'
'last_seen' = '1611356490'
'host_src' = 'forticlient'
'user_info_src' = 'forticlient'
'is_forticlient_endpoint' = 'true'
'unjoined_forticlient_endpoint' = 'false'
'is_forticlient_unauth_user' = 'true'
'avatar_source' = 'OS'
'domain' = 'Fortinet-FSSO.COM'
'forticlient_id' = '********************************'
'forticlient_username' = 'Administrator'
'forticlient_version' = '6.4.2'
'on_net' = 'true'
'quarantined_on_forticlient' = 'false'
'vuln_count' = '0'
'vuln_count_critical' = '0'
'vuln_count_high' = '0'
'vuln_count_info' = '0'
'vuln_count_low' = '0'
'vuln_count_medium' = '0'
'is_online' = 'true'
interface_info
'ipv4_address' = '10.1.100.185'
'mac' = '00:0c:29:11:5b:6b'
'master_mac' = '00:0c:29:11:5b:6b'
'detected_interface' = 'port10'
'last_seen' = '1611356490'
'is_master_device' = 'true'
'is_detected_interface_role_wan' = 'false'
'detected_interface_fortitelemetry' = 'true'
'forticlient_gateway_interface' = 'port10'
'on_net' = 'true'
'is_online' = 'true'
FortiOS 7.6.2 Administration Guide 3576
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,576
|
Fortinet Security Fabric
Configuring the Security Fabric with SAML
Security Assertion Markup Language (SAML) is an open standard for exchanging authentication and authorization data
between one Identity Provider (IdP) and one or more Service Providers (SP). Both parties exchange messages using the
XML protocol as transport. FortiGate firewall devices can be configured as IdPs or SPs.
When the Security Fabric is enabled, you can configure the root FortiGate as the IdP. You can also configure
downstream FortiGates to be automatically configured as SPs, with all links required for SAML communication, when
added to the Security Fabric. Administrators must still be authorized on each device. Credentials are verified by the root
FortiGate, and login credentials are shared between devices. Once authorized, an administrator can move between
Fabric devices without logging in again.
Optionally, the downstream FortiGate can also be manually configured as an SP, and then linked to the root FortiGate.
The authentication service is provided by the root FortiGate using local system admin accounts for authentication. Any of
the administrator account types can be used for SAML log in. After successful authentication, the administrator logs in to
the first downstream FortiGate SP, and can then connect to other downstream FortiGates that have the SSO account
properly configured, without needing to provide credentials again, as long as admins use the same browser session. In
summary, the root FortiGate IdP performs SAML SSO authentication, and individual device administrators define
authorization on FortiGate SPs by using security profiles.
Configuring single-sign-on in the Security Fabric
SAML SSO enables a single FortiGate device to act as the identify provider (IdP), while other FortiGate devices act as
service providers (SP) and redirect logins to the IdP.
Only the root FortiGate can be the identity provider (IdP). The downstream FortiGates can be
configured as service providers (SP).
The process is as follows:
1. Configuring the root FortiGate as the IdP on page 3577
2. Configuring a downstream FortiGate as an SP on page 3578
3. Configuring certificates for SAML SSO on page 3580
4. Verifying the single-sign-on configuration on page 3581
You can also use the CLI. See CLI commands for SAML SSO on page 3582.
Configuring the root FortiGate as the IdP
To configure the root FortiGate as the IdP:
1. Log in to the root FortiGate.
2. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
3. Enable SAML Single Sign-On. The Mode field is automatically populated as Identity Provider (IdP).
4. Enter an IP address in the Management IP/FQDN field.
FortiOS 7.6.2 Administration Guide 3577
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,577
|
Fortinet Security Fabric
5. Enter a management port in the Management port field.
The Management IP/FQDN will be used by the SPs to redirect the login request. The Management IP/FQDN and
Management port must be reachable from the user's device.
6. Select the IdP certificate.
7. Click OK.
Configuring a downstream FortiGate as an SP
There are two ways to configure the downstream FortiGate:
l From the root FortiGate
l From within the downstream device
An SP must be a member of the Security Fabric before you configure it.
To configure the downstream FortiGate from the root FortiGate:
1. Log in to the root FortiGate.
2. Go to Dashboard > Status and locate the Security Fabric widget.
FortiOS 7.6.2 Administration Guide 3578
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,578
|
Fortinet Security Fabric
3. In the topology tree, hover over a FortiGate and click Configure.
The Configure pane opens.
4. Select a SAML Single Sign-On option. Auto sets the device to SP mode. Manual allows you to configure the
SSO settings by clicking Advanced Options.
5. Select a Default login page option.
6. Select one of the following Default admin profile types: prof_admin, super_admin, or super_admin_readonly.
7. Enter an IP address in the Management IP/FQDN field.
8. Enter a management port in the Management port field.
The Management IP/FQDN will be used by the IdP and so other SPs can redirect to each other. The Management
port must be reachable from the user's device.
9. Click OK.
To configure the downstream FortiGate within the device:
1. Log in to the downstream FortiGate.
2. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
3. In the Settings tab, select a SAML Single Sign-On option. Auto sets the device to SP mode. Manual allows you to
configure the SSO settings by clicking Advanced Options.
4. Select a Default login page option.
5. Select one of the following Default admin profile types: prof_admin, admin_no_access, super_admin, or super_
admin_readonly.
FortiOS 7.6.2 Administration Guide 3579
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,579
|
Fortinet Security Fabric
6. Enter an IP address in the Management IP/FQDN field.
7. Enter a management port in the Management port field.
The Management IP/FQDN will be used by the IdP and so other SPs can redirect to each other. The Management
port must be reachable from the user's device.
8. Click OK.
Configuring certificates for SAML SSO
Because communication between the root FortiGate IdP and FortiGate SPs is secured, you must select a local server
certificate in the IdP certificate option on the root FortiGate. When downstream SPs join the IdP (root FortiGate), the SP
automatically obtains the certificate.
In the following SP example, the IdP certificate displays REMOTE_Cert_2, which is the root server certificate for the IdP:
It is possible to manually import a certificate from an SP to the IdP so it can be used for authentication.
To manually import an SP certificate to an IdP:
1. Add the certificate:
a. On the SP, go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
b. Click Advanced Options. The SAML SSO pane opens.
c. Enable SP certificate and select a certificate from the dropdown box.
d. Click Download. The certificate is downloaded on the local file system.
e. Click OK to close the SAML SSO pane.
f. Click OK to close the Security Fabric Setup card.
2. Import the certificate:
a. On the IdP, go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
b. Click Advanced Options. The SAML SSO pane opens.
c. In the Service Providers table, select the SP from step 1 and click Edit.
FortiOS 7.6.2 Administration Guide 3580
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,580
|
Fortinet Security Fabric
d. Enable SP certificate and in the dropdown box, click Import.
The Upload Remote Certificate window opens.
e. Click Upload and select the certificate downloaded in step 1.
f. Select REMOTE_Cert_2.
g. Click OK. The certificate is imported.
h. In the IdP certificate list, select the certificate that you imported.
i. Click OK to close the SAML SSO pane.
j. Click OK to close the Security Fabric Setup card.
Verifying the single-sign-on configuration
After you have logged in to a Security Fabric member using SSO, you can navigate between any Security Fabric
member with SSO configured.
To navigate between Security Fabric members:
1. Log in to a Security Fabric member that is using SSO.
2. In the top banner, click the name of the device you are logged in to. A list of Security Fabric members displays.
FortiOS 7.6.2 Administration Guide 3581
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,581
|
Fortinet Security Fabric
3. Click a Security Fabric member. The login page appears. Click Sign in with Security Fabric.
4. A prompt appears that an SSO administrator account has been created. Click Continue.
You are now logged in to the Security Fabric member with SSO. The letters "SSO" also display beside the user
name in the top banner.
5. Go to System > Administrators > Single-Sign-On Administrator to view the list of SSO admins created.
CLI commands for SAML SSO
To enter a question mark (?) or a tab, Ctrl + V must be entered first. Question marks and tabs cannot be typed or copied
into the CLI Console or some SSH clients.
To configure the IdP:
config system saml
set status enable
set role identity-provider
set cert "Fortinet_Factory"
set server-address "172.16.106.74"
config service-providers
edit "csf_172.16.106.74:12443"
set prefix "csf_ngczjwqxujfsbhgr9ivhehwu37fml20"
set sp-entity-id "http://172.16.106.74/metadata/"
set sp-single-sign-on-url "https://172.16.106.74/saml/?acs"
set sp-single-logout-url "https://172.16.106.74/saml/?sls"
set sp-portal-url "https://172.16.106.74/saml/login/"
config assertion-attributes
edit "username"
next
edit "tdoc@fortinet.com"
set type email
next
end
next
end
end
FortiOS 7.6.2 Administration Guide 3582
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,582
|
Fortinet Security Fabric
To configure an SP:
config system saml
set status enable
set cert "Fortinet_Factory"
set idp-entity-id "http://172.16.106.74/saml-idp/csf_
ngczjwqxujfsbhgr9ivhehwu37fml20/metadata/"
set idp-single-sign-on-url "https://172.16.106.74/csf_
ngczjwqxujfsbhgr9ivhehwu37fml20/login/"
set idp-single-logout-url "https://172.16.106.74/saml-idp/csf_
ngczjwqxujfsbhgr9ivhehwu37fml20/logout/"
set idp-cert "REMOTE_Cert_1"
set server-address "172.16.106.74:12443"
end
To configure an SSO administrator:
config system sso-admin
edit "SSO-admin-name"
set accprofile <SSO admin user access profile>
set vdom <Virtual domain(s) that the administrator can access>
next
end
SAML SSO with pre-authorized FortiGates
You can set up SAML SSO authentication in a Security Fabric environment by starting with a root FortiGate that has one
or more pre-authorized FortiGates.
After the initial configuration, you can add more downstream FortiGates to the Security Fabric, and they are
automatically configured with default values for a service provider.
To set up basic SAML SSO for the Security Fabric:
1. Log in to the root FortiGate of the Security Fabric.
2. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
3. Join two pre-authorized FortiGates to the root FortiGate (see Configuring the root FortiGate and downstream
FortiGates on page 3442).
4. Configure the IdP (see Configuring the root FortiGate as the IdP on page 3577).
5. Configure the SPs (see Configuring a downstream FortiGate as an SP on page 3578).
Navigating between Security Fabric members with SSO
After you have logged in to a Security Fabric member by using SSO, you can navigate between any Security Fabric
member with SSO configured. This can be done using the Security Fabric members dropdown menu or by logging in to a
FortiGate SP from the root FortiGate IdP.
FortiOS 7.6.2 Administration Guide 3583
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,583
|
Fortinet Security Fabric
Security Fabric members dropdown
The Security Fabric members dropdown menu allows you to easily switch between all FortiGate devices that are
connected to the Security Fabric. You can also use this menu to customize a FortiGate in the Security Fabric.
To navigate between Security Fabric members:
1. Log in to a Security Fabric member by using SSO.
2. In the top banner, click the name of the device you are logged into with SSO.
A list of Security Fabric members is displayed.
3. Click the Security Fabric member.
You are logged in to the Security Fabric member without further authentication.
To customize a FortiGate in the Security Fabric:
1. In the Security Fabric members dropdown menu, hover the cursor over a FortiGate so the tooltip is shown.
2. Click Configure. The Configure pane opens.
3. Edit the settings as required.
4. Click OK.
Logging in to an SP from the root IdP
The following example describes how to log in to a root FortiGate IdP, and navigate to other FortiGate SPs in the
Security Fabric without further authentication. The local administrator account is named test3. The local administrator
account must also be available as an SSO administrator account on all downstream FortiGate SPs. Different tabs of the
same browser are used to log in to the various FortiGates.
To log in to a FortiGate SP from a root FortiGate IdP:
1. Log in to the root FortiGate IdP by using the local administrator account.
In this example, the local administrator account is named test3.
2. Go to Dashboard > Status and locate the Security Fabric widget.
3. In the topology tree, click one of the downstream FortiGate SPs, and select Login to <name of FortiGate>. The login
screen is displayed.
4. In the login screen, select Single Sign-On.
By using cookies in your local browser for the already-authenticated SSO administrator, FortiGate logs you in to the
downstream FortiGate SP as the SSO administrator. In this example, the SSO administrator name is test3.
FortiOS 7.6.2 Administration Guide 3584
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,584
|
Fortinet Security Fabric
5. While still logged into the root FortiGate IdP in your browser, go to the browser tab for the root FortiGate IdP, and log
in to another FortiGate SP that is displayed on the Security Fabric widget in the GUI.
SAML SSO login uses SAML_IDP session cookies of already authenticated admin users in your local browser
cache to send to the root FortiGate IdP for authentication. If your browser cache is manually cleared, or you close
your browser, you must authenticate again.
FortiOS 7.6.2 Administration Guide 3585
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,585
|
Fortinet Security Fabric
It is possible to log in to one downstream FortiGate SP in a Security Fabric, and then open
another tab in your browser to connect to another FortiGate SP that is not a member of the
Security Fabric.
This is useful in cases where the SSO administrator and the local system administrator on the
FortiGate SP both have the same login name, but are two different entities.
Integrating FortiAnalyzer management using SAML SSO
When a FortiGate acting as a Security Fabric root is configured as a SAML SSO identity provider (IdP), the FortiAnalyzer
of the Security Fabric can register itself as a service provider (SP). This simplifies the configuration by enabling the
setting in FortiAnalyzer to facilitate Fabric SSO access to the FortiAnalyzer once authenticated to the root FortiGate.
When signed in using SSO, the FortiAnalyzer includes a Security Fabric navigation dropdown, which allows easy
navigation to FortiGates in the Fabric.
To enable FortiAnalyzer as a Fabric SP in the GUI:
1. On the root FortiGate, go to Security Fabric > Physical Topology or Logical Topology.
2. In the topology, click the FortiAnalyzer icon and select Login to FortiAnalyzer.
3. Enter the credentials to log in. A Security Fabric must be configured with the Fabric devices listed under the Fabric
name.
FortiOS 7.6.2 Administration Guide 3586
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,586
|
Fortinet Security Fabric
a. Go to Device Manager to verify the Fabric setup. There is an asterisk beside the root FortiGate.
4. Edit the FortiAnalyzer SAML SSO settings:
a. Go to System Settings > SAML SSO.
b. For Single Sign-On Mode, select Fabric SP and enter the address to access the FortiAnalyzer in Server
Address.
c. Click Apply and log out of the FortiAnalyzer. The FortiAnalyzer will automatically register itself on the FortiGate
and is a visible appliance in the list of SPs.
5. Verify that the FortiAnalyzer registration was successful:
a. In FortiOS, go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
b. In the SAML Single Sign-On section click Advanced Options. There should be an entry for the FortiAnalyzer in
FortiOS 7.6.2 Administration Guide 3587
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,587
|
Fortinet Security Fabric
the Service Providers table.
6. Log in to the FortiAnalyzer. There is a new option to Login with Fabric Single Sign-On.
7. Click Login with Fabric Single Sign-On. A dialog appears to select a Fabric IdP.
8. Select a FortiGate. The ADOM containing that FortiGate opens.
To enable FortiAnalyzer as a Fabric SP in the CLI:
1. In FortiAnalyzer, enable the device as a Fabric SP:
config system saml
set status enable
set role FAB-SP
set server-address "192.168.1.99"
end
FortiAnalyzer will register itself on the FortiGate as an appliance.
FortiOS 7.6.2 Administration Guide 3588
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,588
|
Fortinet Security Fabric
2. Verify the configuration in FortiOS:
show system saml
config system saml
set status enable
set role identity-provider
set cert "fortigate.domain.tld"
set server-address "192.168.1.99"
config service-providers
edit "appliance_192.168.1.103"
set prefix "csf_76sh0bm4e7hf1ty54w42yrrv88tk8uj"
set sp-entity-id "http://192.168.1.103/metadata/"
set sp-single-sign-on-url "https://192.168.1.103/saml/?acs"
set sp-single-logout-url "https://192.168.1.103/saml/?sls"
set sp-portal-url "https://192.168.1.103/saml/login/"
config assertion-attributes
edit "username"
next
edit "profilename"
set type profile-name
next
end
next
end
end
To navigate between devices using SAML SSO in FortiOS:
1. Log in to the root FortiGate.
2. Go to Security Fabric > Physical Topology or Logical Topology.
3. In the topology, click the FortiAnalyzer icon and select Login to FortiAnalyzer.
To navigate between devices using SAML SSO in FortiAnalyzer:
1. Log in to the FortiAnalyzer using SSO.
2. Navigate to the ADOM that contains the root FortiGate of the Security Fabric.
3. In the toolbar, click the Security Fabric name to display a dropdown a list of the Fabric FortiGates.
Integrating FortiManager management using SAML SSO
When a FortiGate is configured as the SAML SSO IdP, FortiManager can be added as an SP.
FortiOS 7.6.2 Administration Guide 3589
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,589
|
Fortinet Security Fabric
To configure FortiManager as a Fabric SP:
1. On the root FortiGate, go to Security Fabric > Fabric Connectors, and edit the Security Fabric Setup connector.
2. In the SAML Single Sign-On section, click Advanced Options.
3. In the Service Providers section, click Create New.
4. Enter a name and a prefix for the SP. FortiOS generates a unique prefix, but you can enter your own.
5. In SP address, enter the FortiManager address including the port number.
6. Click OK.
7. In FortiManager, go to System Settings > SAML SSO and in the Single Sign-On Mode section, click Service
Provider (SP).
8. Configure the IdP Settings:
a. For IdP Type, click Fortinet.
b. For IdP Address, enter the root FortiGate address including the port number.
c. Enter the Prefix of the SP.
d. For IdP Certificate, import the same certificate used on the root FortiGate.
e. Click Apply.
FortiOS 7.6.2 Administration Guide 3590
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,590
|
Fortinet Security Fabric
9. To verify that the configuration works, log out of FortiManager and log in using the Login via Single-Sign-On link.
Advanced option - FortiGate SP changes
From a root FortiGate IdP, you can edit each of the FortiGate SPs. For example, you can edit a FortiGate SP to generate
a new prefix, or you can add or modify SAML attributes. When you generate a new prefix value, it is propagated to the
respective downstream FortiGates.
To edit an SP from the root FortiGate (IdP):
1. Go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
2. Click Advanced Options. The SAML SSO pane opens.
3. In the Service Providers table, select a device and click Edit. The Edit Service Provider pane opens.
4. Edit the settings as needed.
5. Click OK.
FortiOS 7.6.2 Administration Guide 3591
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,591
|
Fortinet Security Fabric
Security rating
The security rating uses real-time monitoring to analyze your Security Fabric deployment, identify potential
vulnerabilities, highlight best practices that can be used to improve the security and performance of your network, and
calculate Security Fabric scores.
The Security Fabric > Security Rating page contains the following tabs:
l Security Controls on page 3592
l Vulnerabilities on page 3596
This section also includes:
l Security Fabric score on page 3599
l Security rating insights on page 3600
l Logging the security rating on page 3601
l Security rating visibility on page 3602
Security Controls
On the Security Fabric > Security Rating page, the Security Controls tab displays the results for all security rating
checks:
l A summary chart identifies of how many items passed, failed, or are exempt from security rating checks.
l Categories against which the security rating tests were run are identified (such as Uncategorized, Audit Logging &
Monitoring, Data Protection, and so on) and the assigned grade for each category is displayed (such as A, B, F, and
so on).
The letter grade is calculated based on the percent of tests in a category that passed:
l A = 90% and above
l B = 80% to <90%
l C = 70% to <80%
l D = 60% to <70%
FortiOS 7.6.2 Administration Guide 3592
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,592
|
Fortinet Security Fabric
l E = 50% to <60%
l F = Less than 50%
For example, if eight out of ten tests in a category passed, then 80% of the tests passed, and the category would be
given a B grade.
l A report of details that is organized in the following security rating categories: Fabric Coverage (available for
devices in a Security Fabric), Optimization, Security Posture, and Uncategorized. Expand each category to display
rows of test details. Click each row to display the Test Details pane.
The following licensing options are available for security rating checks:
l A base set of free checks
l A licensed set that requires a FortiGuard Security Rating Service subscription
The base set can be run locally on any FortiGate and on all other devices in the Security
Fabric. For a list of base and licensed security rating checks, see FortiGuard Security Rating
Service.
For more information about security ratings, and details about each of the checks that are performed, go to Security Best
Practices & Security Rating Feature.
To view security controls:
1. On the root FortiGate, go to Security Fabric > Security Rating. The Security Controls pane opens.
2. For the graded test categories, hover the cursor over a test category to view the calculation breakdown.
3. For the summary chart, click the Passed, Failed, or Exempt words or associated colors in the chart to filter the report
results.
For example, click Failed to display only failed tests in the report.
Click Result to remove the filter, or click the X beside the filter in the Search bar
4. Expand each security rating category in the report to view its details.
5. In the report, click each row to view its Test details pane, which includes two tabs: Results and Info & Compliance.
Click Details to hide and display the Test details pane for a selected row in the report.
FortiOS 7.6.2 Administration Guide 3593
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,593
|
Fortinet Security Fabric
If a test category failed, the Results section includes a link to the GUI page where you can resolve the problem.
The Info & Compliance tab includes the security controls used for the test and links to specific FSBP, PCI, or CIS
compliance policies.
6. Select FSBP, PCI, or CIS to filter the report for the selected compliance policy.
The FortiGate must have a valid Attack Surface Security Rating license to view security
ratings grouped by CIS.
7. Click Export to export the report to a CSV or JSON file.
8. Click the gear icon to customize the report table by adding more columns.
To exit the current view, click the x beside the search item to return to the summary view.
FortiOS 7.6.2 Administration Guide 3594
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,594
|
Fortinet Security Fabric
Multi-VDOM mode
In multi-VDOM mode, security rating reports can be generated in the Global VDOM for all of the VDOMs on the device.
Administrators with read/write access can run the security rating report in the Global VDOM. Administrators with readonly access can only view the report.
On the report scorecards, the Scope column shows the VDOMs that the check was run on.
Global scope:
VDOM scope:
The security rating event log is available on the root VDOM.
FortiOS 7.6.2 Administration Guide 3595
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,595
|
Fortinet Security Fabric
Security rating check scheduling
By default, security rating checks are scheduled to run automatically every eight hours.
The security rating also runs automatically for only the specific check when the relevant configuration changes are
made.
Vulnerabilities
On the Security Fabric > Security Rating page, the Vulnerabilities tab displays PSIRT advisory and Outbreak detection
entries that are included in the downloaded Security Rating package:
PSIRT-related notifications
On a FortiGate with a valid Firmware license, the separate Security Rating package downloaded from FortiGuard
supports PSIRT vulnerabilities, which are highlighted in security rating results. PSIRT Package Definitions are part of the
Firmware entitlement.
To verify the FortiGuard license entitlement in the GUI:
1. Go to System > FortiGuard and expand the License Information table.
2. Expand the Firmware & General Updates section.
FortiOS 7.6.2 Administration Guide 3596
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,596
|
Fortinet Security Fabric
3. Check that PSIRT Check definitions appears in the list and the license is valid.
To verify the FortiGuard license entitlement in the CLI:
# diagnose autoupdate versions
...
Security Rating Data Package
---------
Version: 5.00022
Contract Expiry Date: Fri Nov 24 2023
Last Updated using scheduled update on Mon Sep 11 09:44:21 2023
Last Update Attempt: Tue Sep 12 16:29:10 2023
Result: No Updates
The following notifications are visible in the GUI.
l Warning message: if the security rating result indicates a vulnerability with a critical severity, then the FortiOS GUI
displays a warning message in the header and a new notification under the bell icon. The View Vulnerability link
appears in the header for global administrators.
Clicking the warning message redirects to the System > Firmware & Registration page, where administrators are
encouraged to update any affected Fortinet Fabric devices to the latest firmware releases to resolve the critical
vulnerabilities.
l Tooltip: a tooltip for the critical vulnerability label on the System > Firmware & Registration page lists the
vulnerability, and it links to the Security Fabric > Security Rating page where more details about the vulnerability are
FortiOS 7.6.2 Administration Guide 3597
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,597
|
Fortinet Security Fabric
displayed.
To view vulnerability results after performing security rating scan:
# diagnose report-runner vuln-read
Index: 0
Name: FG-IR-23-001: FortiOS / FortiManager / FortiAnalyzer / FortiWeb / FortiProxy /
FortiSwitchManager - Heap buffer underflow in administrative interface
FortiGate Serial: FGVM02TM23000000
To clear the vulnerability result:
# diagnose report-runner vuln-clean
Deleted temporary critical vulnerability file
FortiGuard IoT vulnerability-related checks
There are two rating checks in the Security Posture report related to IoT vulnerabilities:
l The FortiGuard IoT Detection Subscription rating check will pass if the System > FortiGuard page shows that the
IoT Detection Definitions (under the Attack Surface Security Rating entitlement) is licensed. In this example, the
result is marked as Passed because the license is valid.
FortiOS 7.6.2 Administration Guide 3598
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,598
|
Fortinet Security Fabric
l The FortiGuard IoT Vulnerability rating check will fail if any IoT vulnerabilities are found.
Hover over the device name to display the tooltip, which includes an option to View IoT Vulnerabilities.
To detect IoT vulnerabilities, the FortiGate must have a valid IoT Definitions license, device
detection must be configured on a LAN interface used by IoT devices, and a firewall policy with
an application control sensor must be configured.
Security Fabric score
The Security Fabric score is calculated when a security rating check is run, based on the severity level of the checks that
are passed or failed. A higher scores represents a more secure network. Points are added for passed checks and
removed for failed checks.
Severity level Weight (points)
Critical 50
High 25
Medium 10
Low 5
To calculate the number of points awarded to a device for a passed check, the following equation is used:
score =
<severity level weight>
× <secure FortiGate multiplier>
<# of FortiGates>
The secure FortiGate multiplier is determined using logarithms and the number of FortiGate devices in the Security
Fabric.
For example, if there are four FortiGate devices in the Security Fabric that all pass the compatible firmware check, the
score for each FortiGate device is calculated with the following equation:
50
× 1.292 = 16.15 points
4
All of the FortiGate devices in the Security Fabric must pass the check in order to receive the points. If any one of the
FortiGate devices fails a check, the devices that passed are not awarded any points. For the device that failed the check,
the following equation is used to calculated the number of points that are lost:
score = <severity level weight> x <secure FortiGate multiplier>
For example, if the check finds two critical FortiClient vulnerabilities, the score is calculated with the following equation:
-50 × 2 = -100 points
Scores are not affected by checks that do not apply to your network. For example, if there are no FortiAP devices in the
Security Fabric, no points will be added or subtracted for the FortiAP firmware version check.
FortiOS 7.6.2 Administration Guide 3599
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,599
|
Fortinet Security Fabric
Security rating insights
Objects, such as firewall policies or interfaces, with security rating recommendations are highlighted in the GUI. Hover
over highlighted objects to display a Security Rating Insights tooltip. A Security Rating Insights button also displays at the
bottom of the table.
Dismissed issues are unique for each administrator. Hashes for dismissed notifications are saved in local storage. If a
user clears the local storage, all issues will show up again as not dismissed.
Once an issue is resolved, the notification disappears after the next security rating report runs.
To view security rating insights for firewall policies:
1. Go to Policy & Objects > Firewall Policy.
Objects with security rating recommendations are highlighted.
2. Hover over any highlighted object to display a tooltip that shows Security Rating Insights:
3. Below the table, click Security Rating Insights to display relevant issues.
4. Select an issue, such as Unused Policies to display a banner and filter that you can use to filter down to the
applicable entries.
5. Click the X in the banner to close the issue.
FortiOS 7.6.2 Administration Guide 3600
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,600
|
Fortinet Security Fabric
To view security rating insights for network interfaces:
1. Go to Network > Interfaces.
Objects with security rating recommendations are highlighted.
2. Hover over any highlighted object to display a tooltip that shows Security Rating Insights:
3. Below the table, click Security Rating Insights to display relevant issues.
4. Select an issue to display a banner and filter that you can use to filter down to the applicable entries.
5. Click the X in the banner to close the issue.
Logging the security rating
The results of past security checks are available on the Log & Report > System Events page. Click the Security Rating
Events card to see the detailed log.
An event filter subtype can be created for the Security Fabric rating so event logs are created on the root FortiGate that
summarize the results and show detailed information for the individual tests.
To configure security rating logging using the CLI:
config log eventfilter
set security-rating enable
end
FortiOS 7.6.2 Administration Guide 3601
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,601
|
Fortinet Security Fabric
Security rating visibility
Security ratings tests that are not relevant can be hidden, streamlining the user experience by displaying only pertinent
information.
A Security Fabric is not required for this feature. If multiple FortiGates are in a Security Fabric, hidden security ratings
can be synchronized from the root FortiGate device to downstream FortiGate devices, or overridden locally on the
downstream devices.
To disable showing a security rating control in the default report:
1. Go to Security Fabric > Security Rating.
2. Find Unsecure Protocol - Telnet in the table, right-click on it, and select Report Visibility > Hide.
The Unsecure Protocol - Telnet control is no longer shown in the list.
3. Change the View to All to show the Unsecure Protocol - Telnet control in the table when Report Visibility is set to
Hide.
FortiOS 7.6.2 Administration Guide 3602
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,602
|
Fortinet Security Fabric
All hidden controls are then shown in the table.
The Visibility column is not shown by default. Edit the column settings to show it in the table.
See Column settings on page 44 for details.
To disable showing a security rating control as an insight across the GUI:
1. Go to Network > Interfaces.
2. Edit an interface to enable TELNET administrative access.
3. Click on the Security Rating Insights, or hover over the interface name to see the Unsecure Protocol - Telnet
warning.
FortiOS 7.6.2 Administration Guide 3603
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,603
|
Fortinet Security Fabric
4. Go to Security Fabric > Security Rating.
5. Find Unsecure Protocol - Telnet in the table, right-click on it, and select Insight Visibility > Hide.
6. Go to Network > Interfaces.
7. Click on the Security Rating Insights, or hover over the interface name to see that the Unsecure Protocol - Telnet
warning is no longer shown.
FortiOS 7.6.2 Administration Guide 3604
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,604
|
Fortinet Security Fabric
To configure security rating control in the CLI:
config system security-rating controls
edit <control name>
set display-report {enable | disable}
set display-insight {enable | disable}
next
end
Variable Description
display-report {enable |
disable}
Enable/disable displaying the Security Rating control in the default report (default
= enable).
display-insight {enable |
disable}
Enable/disable displaying the Security Rating control as an insight across the GUI
(default = enable).
Security rating control names are hidden in the CLI until they are configured.
To configure synchronizing security rating visibility settings on downstream devices in a Security
Fabric:
config system csf
set configuration-sync {default | local}
end
config system security-rating settings
set override-sync {enable | disable}
end
Variable Description
configuration-sync
{default | local}
Configuration sync mode.
l default: Synchronize configuration for IPAM, FortiAnalyzer, FortiSandbox,
and Central Management to root node (default).
l local: Do not synchronize configuration with root node.
override-sync {enable |
disable}
Enable/disable overriding Security Rating control settings that are synchronized
from the Security Fabric's root FortiGate (default = disable).
When configuration-sync is set to local, the system security-rating settings command is not
available.
Automation stitches
Automation stitches automate the activities between the different components in the Security Fabric, which decreases
the response times to security events. Events from any source in the Security Fabric can be monitored, and action
responses can be set up to any destination.
FortiOS 7.6.2 Administration Guide 3605
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,605
|
Fortinet Security Fabric
The automation settings can be synchronized within the Security Fabric, or can only apply to an individual FortiGate in
the Security Fabric. Automation stitches can only be created on the root FortiGate in a Security Fabric.
To configure automation setting synchronization in a Security Fabric:
config automation setting
set fabric-sync {enable | disable}
end
Automation stitches can also be used on FortiGates that are not part of a Security Fabric.
An automation stitch consists of two parts: the trigger and the actions. The trigger is the condition or event on the
FortiGate that activates the action, for example, a specific log, or a failed log in attempt. The action is what the FortiGate
does in response to the trigger.
Automation stitches that use cloud-based actions (AWS Lambda, Azure Function, Google Cloud Function, and AliCloud
Function) have the option to delay an action after the previous action is completed.
Diagnose commands are available in the CLI to test, log, and display the stitch history and settings.
Creating automation stitches
To create an automation stitch, a trigger event and a response action or actions are selected. Automation stitches can be
tested after they are created.
In the GUI, go to Security Fabric > Automation and click Create New. Automation stitches, actions, and triggers are
configured in separate dialogs.
The stitch Action execution can be set to either Sequential or Parallel. In sequential execution, actions will execute one
after another with a delay (if specified). If one action fails, then the action chain stops. This is the default setting. In
parallel execution, all actions will execute immediately when the stitch is triggered.
When creating a stitch, clicking Add Trigger and Add Action displays a list of available triggers and actions, and the
option to create a new one.
FortiOS 7.6.2 Administration Guide 3606
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,606
|
Fortinet Security Fabric
Once the stitch is configured, a process diagram of the trigger, actions, and delays is displayed. A delay can be added
before an action if Sequential action execution is used. Executing the next action can be delayed by up to 3600 seconds
(one hour).
Triggers and actions can be configured separately, and then added to an automation stitch.
The maximum number of automation stitches that are allowed to run concurrently can be configured in the CLI (32 - 256,
default = 128).
To configure the maximum number of concurrent automation stitches:
config automation setting
set max-concurrent-stitches <integer>
end
Tabs on the Automation page
On the Security Fabric > Automation page, there are tabs for Stitch, Trigger, and Action. The Stitch tab is the default view
that lists the trigger and actions used in each stitch. Individual triggers and actions can be created or edited in the
corresponding tabs.
FortiOS 7.6.2 Administration Guide 3607
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,607
|
Fortinet Security Fabric
Click Trigger to view the list of triggers.
Click Action to view the list of actions.
FortiOS 7.6.2 Administration Guide 3608
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,608
|
Fortinet Security Fabric
Sample configuration
The following example shows how to configure an automation stitch with an Any Security Rating Notification trigger with
AWS Lambda and Email actions. There is a 60-second delay before the Email action.
To configure the automation stitch in the GUI:
1. Go to Security Fabric > Automation and click Create New.
2. Enter the stitch name and description.
3. Configure the trigger:
a. Click Add Trigger.
b. Select Any Security Rating Notification.
c. Click Apply.
4. Configure the AWS Lambda function action:
a. Click Add Action.
b. Click Create and select AWS Lambda.
c. Enter the following:
Name aws_no_delay
URL Enter the request API URI
API key Enter the API key
HTTP header header2 : header2_value
FortiOS 7.6.2 Administration Guide 3609
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,609
|
Fortinet Security Fabric
d. Click OK.
e. Select the action in the list and click Apply.
5. Configure the Email notification action:
a. Click Add Action.
b. Click Create and select Email.
c. Enter the following:
Name email_action
To Enter an email address
Subject email action for test
Replacement message Enable
d. Click OK.
e. Select the action in the list and click Apply.
6. Click the Add delay located between both actions. Enter 60 and click OK.
7. Click OK.
FortiOS 7.6.2 Administration Guide 3610
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,610
|
Fortinet Security Fabric
To configure the automation stitch in the CLI:
1. Configure the trigger:
config system automation-trigger
edit "Any Security Rating Notification"
set event-type security-rating-summary
set report-type any
next
end
2. Configure the actions:
config system automation-action
edit "aws_no_delay"
set action-type aws-lambda
set aws-api-key xxxxxxxxxxxx
set uri "xxxxxxxxxx.execute-api.us-east-1.amazonaws.com/xxxxxxxxxx"
config http-headers
edit 1
set key "header2"
set value "header2_value"
next
end
next
edit "email_action"
set action-type email
set email-to "test@fortinet.com"
set email-subject "email action for test"
set replacement-message enable
next
end
3. Configure the stitch:
config system automation-stitch
edit "aws_no_delay"
set description "aws action test"
set trigger "Any Security Rating Notification"
config actions
edit 1
set action "aws_no_delay"
set required enable
next
edit 2
set action "email_action"
set delay 60
set required enable
next
end
next
end
Testing automation stitches
In the GUI, go to Security Fabric > Automation, right-click on the automation stitch and select Test Automation Stitch.
In the CLI, enter diagnose automation test <automation-stitch name>.
FortiOS 7.6.2 Administration Guide 3611
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,611
|
Fortinet Security Fabric
Default automation stitches
The following default automation stitches are included in FortiOS:
l Compromised Host Quarantine
l Firmware upgrade notification
l FortiAnalyzer Connection Down
l Network Down
l HA Failover
l Incoming Webhook Quarantine
l License Expired Notification
l Reboot
l Security Rating Notification
To view and edit the automation stitches in the GUI, go to Security Fabric > Automation.
CLI configurations
Compromised Host Quarantine
config system automation-action
edit "Access Layer Quarantine"
set description "Quarantine the MAC address on access layer devices (FortiSwitch and
FortiAP)."
set action-type quarantine
next
edit "FortiClient Quarantine"
set description "Use FortiClient EMS to quarantine the endpoint device."
set action-type quarantine-forticlient
FortiOS 7.6.2 Administration Guide 3612
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,612
|
Fortinet Security Fabric
next
end
config system automation-trigger
edit "Compromised Host"
set description "An incident of compromise has been detected on a host endpoint."
next
end
config system automation-stitch
edit "Compromised Host Quarantine"
set description "Quarantine a compromised host on FortiAPs, FortiSwitches, and
FortiClient EMS."
set status disable
set trigger "Compromised Host"
config actions
edit 1
set action "Access Layer Quarantine"
next
edit 2
set action "FortiClient Quarantine"
next
end
next
end
Firmware upgrade notification
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "Auto Firmware upgrade"
set description "Automatic firmware upgrade."
set trigger-type event-based
set event-type event-log
set logid 22094 22095 32263
next
end
config system automation-stitch
edit "Firmware upgrade notification"
set description "Automatic firmware upgrade notification."
set status enable
set trigger "Auto Firmware upgrade"
config actions
edit 1
set action "Email Notification"
set delay 0
set required disable
next
FortiOS 7.6.2 Administration Guide 3613
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,613
|
Fortinet Security Fabric
end
next
end
FortiAnalyzer Connection Down
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "FortiAnalyzer Connection Down"
set description "A FortiAnalyzer connection is down."
set event-type event-log
set logid 22902
next
end
config system automation-stitch
edit "FortiAnalyzer Connection Down"
set description "Send a email notification when the connection to FortiAnalyzer is
lost."
set status disable
set trigger "FortiAnalyzer Connection Down"
config actions
edit 1
set action "Email Notification"
next
end
next
end
Network Down
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "Network Down"
set description "A network connection is down."
set event-type event-log
set logid 20099
config fields
edit 1
FortiOS 7.6.2 Administration Guide 3614
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,614
|
Fortinet Security Fabric
set name "status"
set value "DOWN"
next
end
next
end
config system automation-stitch
edit "Network Down"
set description "Send an email when a network goes down."
set status disable
set trigger "Network Down"
config actions
edit 1
set action "Email Notification"
next
end
next
end
HA Failover
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "HA Failover"
set description "A HA failover has occurred."
set event-type ha-failover
next
end
config system automation-stitch
edit "HA Failover"
set description "Send an email when a HA failover is detected."
set status disable
set trigger "HA Failover"
config actions
edit 1
set action "Email Notification"
next
end
next
end
Incoming Webhook Quarantine
config system automation-action
edit "Access Layer Quarantine"
set description "Quarantine the MAC address on access layer devices (FortiSwitch and
FortiOS 7.6.2 Administration Guide 3615
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,615
|
Fortinet Security Fabric
FortiAP)."
set action-type quarantine
next
edit "FortiClient Quarantine"
set description "Use FortiClient EMS to quarantine the endpoint device."
set action-type quarantine-forticlient
next
end
config system automation-trigger
edit "Incoming Webhook Call"
set description "An incoming webhook call is received"
set event-type incoming-webhook
next
end
config system automation-stitch
edit "Incoming Webhook Quarantine"
set description "Quarantine a provided MAC address on FortiAPs, FortiSwitches, and
FortiClient EMS using an Incoming Webhook."
set status disable
set trigger "Incoming Webhook Call"
config actions
edit 1
set action "Access Layer Quarantine"
next
edit 2
set action "FortiClient Quarantine"
next
end
next
end
License Expired Notification
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "License Expiry"
set description "A FortiGate license is near expiration."
set event-type license-near-expiry
set license-type any
next
end
config system automation-stitch
edit "License Expired Notification"
set description "Send a email notification when a license is near expiration."
set status disable
set trigger "License Expiry"
FortiOS 7.6.2 Administration Guide 3616
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,616
|
Fortinet Security Fabric
config actions
edit 1
set action "Email Notification"
next
end
next
Reboot
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "Reboot"
set description "A FortiGate is rebooted."
set event-type reboot
next
end
config system automation-stitch
edit "Reboot"
set description "Send an email when a FortiGate is rebooted."
set status disable
set trigger "Reboot"
config actions
edit 1
set action "Email Notification"
next
end
next
end
Security Rating Notification
config system automation-action
edit "Email Notification"
set description "Send a custom email to the specified recipient(s)."
set action-type email
set forticare-email enable
set email-subject "%%log.logdesc%%"
set message "%%log%%"
next
end
config system automation-trigger
edit "Any Security Rating Notification"
set description "A security rating summary report has been generated."
set event-type security-rating-summary
set report-type any
FortiOS 7.6.2 Administration Guide 3617
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,617
|
Fortinet Security Fabric
next
end
config system automation-stitch
edit "Security Rating Notification"
set description "Send a email notification when a new Security Rating report is
available."
set status disable
set trigger "Any Security Rating Notification"
config actions
edit 1
set action "Email Notification"
next
end
next
end
Incoming Webhook Quarantine stitch
The Incoming Webhook Quarantine stitch for API calls to the FortiGate accepts multiple parameters (MAC address and
FortiClient UUID) from an Incoming Webhook trigger, which enacts either the Access Layer Quarantine action (MAC
address) or the FortiClient Quarantine action (FortiClient UUID). This is a default automation stitch included in FortiOS.
To trigger the Incoming Webhook Quarantine stitch in the GUI:
1. Create a new API user:
a. Go to System > Administrators.
b. Click Create New > REST API Admin.
c. Configure the New REST API Admin settings, and copy the API key to the clipboard.
2. Enable the stitch:
a. Go to Security Fabric > Automation.
b. Under Incoming Webhook, right-click Incoming Webhook Quarantine, and select Select Status > Enable.
3. Get the sample cURL request:
a. Click the Trigger trigger tab.
b. Under Incoming Webhook, right-click Incoming Webhook Call, and select Edit.
c. In the API admin key field, enter the API key you recorded previously. The Sample cURL request field updates.
FortiOS 7.6.2 Administration Guide 3618
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,618
|
Fortinet Security Fabric
d. Copy the Sample cURL request to the clipboard.
e. Click OK.
4. Execute the request:
a. Edit the sample cURL request you just copied.
b. Add parameters to the data field ("mac" and "fctuid"), and then execute the request.
root@pc:~# curl -k -X POST -H 'Authorization: Bearer
cfgtct1mmx3fQxr4khb994p7swdfmk' --data '{ "mac":"0c:0a:00:0c:ce:b0", "fctuid":
"0000BB0B0ABD0D00B0D0A0B0E0F0B00B"}'
https://172.16.116.226/api/v2/monitor/system/automationstitch/webhook/Incoming%20Webhook%20Quarantine
{
"http_method":"POST",
"status":"success",
"http_status":200,
"serial":"FGT00E0Q00000000",
"version":"v6.4.0",
"build":1545
Encode spaces in the automation stitch name with %20. For example,
Incoming%20Webhook%20Quarantine
Once the automation stitch is triggered, the MAC address is quarantined by the FortiGate, and an event log is
created. The FortiClient UUID is quarantined on the EMS server side.
To trigger the Incoming Webhook Quarantine stitch in the CLI:
1. Create a new API user and note the API key:
config system api-user
FortiOS 7.6.2 Administration Guide 3619
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,619
|
Fortinet Security Fabric
2. Enable the automation stitch:
config system api-user
edit "api"
set api-key ************
set accprofile "api_profile"
set vdom "root"
config trusthost
edit 1
set ipv4-trusthost 10.6.30.0 200.200.200.0
next
end
next
end
3. Edit the cURL request to include parameters in the data field ("mac" and "fctuid"), then execute the request:
root@pc56:~# curl -k -X POST -H 'Authorization: Bearer
cfgtct1mmx0fQxr4khb000p70wdfmk' --data '{ "mac":"0c:0a:00:0c:ce:b0", "fctuid":
"3000BB0B0ABD0D00B0D0A0B0E0F0B00B"}'
https://100.10.100.200/api/v2/monitor/system/automationstitch/webhook/Incoming%20Webhook%20Quarantine
{
"http_method":"POST",
"status":"success",
"http_status":200,
"serial":"FGT80E0Q00000000",
"version":"v6.4.0",
"build":1545
Encode spaces in the automation stitch name with %20. For example,
Incoming%20Webhook%20Quarantine.
Once the automation stitch is triggered, the MAC address is quarantined by the FortiGate, and an event log is
created. The FortiClient UUID is quarantined on the EMS server side.
Sample log
date=2020-02-14 time=15:37:48 logid="0100046600" type="event" subtype="system"
level="notice" vd="root" eventtime=1581723468644200712 tz="-0800" logdesc="Automation
stitch triggered" stitch="Incoming Webhook Quarantine" trigger="Incoming Webhook
Quarantine" stitchaction="Compromised Host Quarantine_quarantine,Compromised Host
Quarantine_quarantine-forticlient" from="log" msg="stitch:Incoming Webhook Quarantine is
triggered."
Triggers
There are two types of automation triggers that can be configured in automation stitches: static and dynamic.
Static automation triggers are included in FortiOS by default. They require only a name, description, and one setting.
Static automation triggers can be edited, but they cannot be deleted.
FortiOS 7.6.2 Administration Guide 3620
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,620
|
Fortinet Security Fabric
Dynamic automation triggers require multiple settings to be configured. Dynamic automation triggers can be created by
clicking the Create New button on the Trigger tab, or clicking Create within the Create Automation Stitch page.
The following table outlines the available static triggers.
Trigger Description
Anomaly Logs An anomalous event has occurred. See Event log category triggers on page 3635
for an example.
Any Security Rating
Notification
A summary is available for a recently run Security Rating report. The default
report type is Any. Other available options include:
l Security Posture
l Fabric Coverage
l Optimization
AV & IPS DB Update The antivirus and IPS database is updating.
Compromised Host An indicator of compromise (IoC) is detected on a host endpoint.
Additional actions are available only for Compromised Host triggers:
l Access Layer Quarantine
l FortiClient Quarantine
l VMware NSX Security Tag
l IP Ban
Configuration Change A FortiGate configuration change has occurred.
Conserve Mode A FortiGate entered conserve mode due to low memory. See Execute a CLI script
based on memory and CPU thresholds on page 3682 for an example.
FortiGate Cloud-Based IOC IOC detection from the FortiGate Cloud IOC service.
This option requires an IOC license, a web filter license, and FortiCloud logging
must be enabled.
HA Failover An HA failover is occurring.
High CPU A FortiGate has high CPU usage. See Execute a CLI script based on memory and
CPU thresholds on page 3682 for an example.
IPS Logs An IPS event has occurred.
License Expiry A FortiGuard license is expiring. The default license type is Any. Other available
options include:
The license type must be selected. Options include:
l FortiCare Support
l FortiGuard Web Filter
l FortiGuard AntiSpam
l FortiGuard AntiVirus
l FortiGuard IPS
l FortiGuard Management Service
l FortiGate Cloud
Local Certificate Expiry A local certificate is about to expire. See Certificate expiration trigger on page
3639 for an example.
FortiOS 7.6.2 Administration Guide 3621
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,621
|
Fortinet Security Fabric
Trigger Description
Reboot A FortiGate is rebooting.
SSH Logs An SSH event has occurred.
Traffic Violation A traffic policy has been violated.
Virus Logs A virus event has occurred.
Web Filter Violation A web filter policy has been violated.
The following table outlines the available dynamic triggers.
Category Trigger Description
Security Fabric
Fabric Connector Event An event has occurred on a specific Fabric connector. See Fabric
connector event trigger on page 3627 for details.
FortiAnalyzer Event
Handler
The specified FortiAnalyzer event handler has occurred. See
FortiAnalyzer event handler trigger on page 3622 for details.
FortiGate Cloud Event
Handler
The specified FortiGate Cloud event handler has occurred.
This option requires a FortiGate Cloud log retention license.
Miscellaneous
FortiOS Event Log The specified FortiOS log has occurred.
Multiple event log IDs can be selected, and log field filters can be
applied. See FortiOS event log trigger on page 3632 for an example.
Incoming Webhook An incoming webhook is triggered.
Schedule A scheduled monthly, weekly, daily, hourly, or one-time trigger. Set to
occur on a specific minute of an specific hour on a specific day. When
using the one-time trigger, set to occur on specific date and time in
the future. See Schedule trigger on page 3641 for an example.
FortiAnalyzer event handler trigger
You can trigger automation stitches based on FortiAnalyzer event handlers. This allows you to define rules based on
complex correlations across devices, log types, frequencies, and other criteria.
To set up a FortiAnalyzer event handler trigger:
1. Configure a FortiGate event handler on the FortiAnalyzer
2. Configure FortiAnalyzer logging on the FortiGate on page 3623
3. Configure an automation stitch that is triggered by a FortiAnalyzer event handler on page 3624
Configure a FortiGate event handler on the FortiAnalyzer
On the FortiAnalyzer, configure an event handler for the automation stitch. In this example, the event handler is triggered
when an administrator logs in to the FortiGate. See Creating a custom event handler in the FortiAnalyzer Administration
FortiOS 7.6.2 Administration Guide 3622
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,622
|
Fortinet Security Fabric
Guide for more information.
To configure an event handler on the FortiAnalyzer:
1. Go to FortiSoC > Handlers > FortiGate Event Handlers, and click Create New.
2. Configure an event handler with two conditions for the automation stitch:
Log Type Event Log
Log Subtype System
Group By Device ID
Logs match Any of the following conditions
Log Field Level
Match Criteria Equal To
Value Information
Log Field Action
Match Criteria Equal To
Value login
3. Configure the other settings as needed.
4. Click OK.
Configure FortiAnalyzer logging on the FortiGate
See Configuring FortiAnalyzer on page 3451 for more information.
FortiOS 7.6.2 Administration Guide 3623
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,623
|
Fortinet Security Fabric
To configure FortiAnalyzer logging in the GUI:
1. Go to Security Fabric > Fabric Connectors and double-click the FortiAnalyzer Logging card.
2. In the Settings > FortiAnalyzer tab, ensure the Status is Enabled, and configure the settings as needed.
3. Click OK.
To configure FortiAnalyzer logging in the CLI:
config log fortianalyzer setting
set status enable
set server "10.6.30.250"
set serial "FL-4HET000000000"
set upload-option realtime
set reliable enable
end
Configure an automation stitch that is triggered by a FortiAnalyzer event handler
When a FortiAnalyzer event handler is triggered, it sends a notification to the FortiGate automation framework, which
generates a log and triggers the automation stitch.
To configure an automation stitch that is triggered by a FortiAnalyzer event handler in the GUI:
1. Go to Security Fabric > Automation and click Create New.
2. Enter the stitch name, auto-faz-1.
FortiOS 7.6.2 Administration Guide 3624
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,624
|
Fortinet Security Fabric
3. Configure the trigger:
a. Click Add Trigger.
b. Click Create and select FortiAnalyzer Event Handler.
c. Enter the following:
Name auto-faz-1
Event handler name system-log-handler2
Event severity Medium
Event tag User login successful
d. Click OK.
e. Select the trigger in the list and click Apply.
4. Configure the Email notification action:
a. Click Add Action.
b. Click Create and select Email.
c. Enter the following:
Name auto-faz-1_email
To Enter an email address
Subject CSF stitch alert
Body User login FortiGate successfully.
FortiOS 7.6.2 Administration Guide 3625
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,625
|
Fortinet Security Fabric
d. Click OK.
e. Select the action in the list and click Apply.
5. Click OK.
To configure an automation stitch that is triggered by a FortiAnalyzer event handler in the CLI:
1. Create an automation trigger:
config system automation-trigger
edit "auto-faz-1"
set event-type faz-event
set faz-event-name "system-log-handler2"
set faz-event-severity "medium"
set faz-event-tags "User log in successful"
next
end
2. Create an automation action:
config system automation-action
edit "auto-faz-1_email"
set action-type email
set email-to "admin@fortinet.com"
set email-subject "CSF stitch alert"
set message "User login FortiGate successfully."
next
end
3. Create the automation stitch:
config system automation-stitch
edit "auto-faz-1"
set trigger "auto-faz-1"
config actions
edit 1
set action "auto-faz-1_email"
set required enable
next
end
FortiOS 7.6.2 Administration Guide 3626
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,626
|
Fortinet Security Fabric
next
end
View the trigger event log
To view the trigger event log in the GUI:
1. Log in to the FortiGate.
The FortiAnalyzer sends a notification to the FortiGate automation framework, generates an event log on the
FortiGate, and triggers the automation stitch.
2. Go to Log & Report > System Events and select General System Events. From the log location dropdown, select
FortiAnalyzer.
To view the trigger event log in the CLI:
# execute log display
...
date=2019-02-05 time=14:16:17 logid="0100046600" type="event" subtype="system"
level="notice" vd="root" eventtime=1549404977 logdesc="Automation stitch triggered"
stitch="auto-faz-1" trigger="auto-faz-1" from="log" msg="stitch:auto-faz-1 is triggered."
...
Sample email
The email sent by the action will look similar to the following:
Fabric connector event trigger
With the Fabric Connector Event trigger, any supported Fabric connector is able to trigger an automation stitch on the
FortiGate based on a specific event defined on the Fabric connector. Currently, only FortiDeceptor 4.1 and later supports
this trigger for the Insider Threat, Notify Ban, and Notify Unban events.
In the following example, an authorized FortiDeceptor in the Security Fabric deploys a decoy called ubuntu16 configured
with SSH, SAMBA, HTTP, and HTTPS services.
This example assumes the Security Fabric is already configured. Refer to Configuring the root FortiGate and
downstream FortiGates and FortiDeceptor for detailed configuration steps. On the root FortiGate, the Allow downstream
device REST API access option must be enabled (set downstream-access enable). The minimum permission
required for the selected Administrator profile is Read/Write for User & Device (set authgrp read-write).
Three stitches are configured, one for each FortiDeceptor trigger type:
Stitch name Fabric connector event trigger Actions
fortideceptor_threat Insider threat Email and IP ban
fortideceptor_ban Notify ban Email and IP ban
FortiOS 7.6.2 Administration Guide 3627
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,627
|
Fortinet Security Fabric
Stitch name Fabric connector event trigger Actions
fortideceptor_unban Notify unban Email and CLI script
To configure stitches with the Fabric connector event trigger in the GUI:
1. Configure the triggers:
a. Go to Security Fabric > Automation, select the Trigger tab, and click Create New.
b. In the Security Fabric section, click Fabric Connector Event and enter the following:
Name fdc_Insider_Threat
Description Insider_Threat
Connector Select the FortiDeceptor connector
Event Name Insider Threat
c. Click OK.
d. Repeat these steps to create two more triggers with the following settings:
Name fdc_Notify_Ban
Description Notify_Ban
Connector Select the FortiDeceptor connector
Event Name Notify Ban
Name fdc_Notify_Unban
Description Notify_Unban
Connector Select the FortiDeceptor connector
Event Name Notify Unban
2. Configure the actions (the default IP Ban action will be added later to the stitch):
a. Go to Security Fabric > Automation, select the Action tab, and click Create New.
b. In the Notifications section, click Email and enter the following:
Name email_log
To Enter an email address
Subject CSF stitch alert
c. Click OK.
d. Repeat these steps to create a CLI Script (in the General section) action with the following settings:
Name fdc_unban
Script diagnose user banned-ip delete src4 %%log.srcip%%
Administrator profile super_admin
3. Configure the fortideceptor_threat stitch:
FortiOS 7.6.2 Administration Guide 3628
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,628
|
Fortinet Security Fabric
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, fortideceptor_threat.
c. Click Add Trigger. Select fdc_Insider_Threat and click Apply.
d. Click Add Action. Select email_log and click Apply.
e. Click Add Action. Select IP Ban and click Apply.
f. Click the Add delay located between both actions. Enter 5 and click OK.
g. Click OK.
4. Configure the fortideceptor_ban stitch:
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, fortideceptor_ban.
c. Click Add Trigger. Select fdc_Notify_Ban and click Apply.
d. Click Add Action. Select email_log and click Apply.
e. Click Add Action. Select IP Ban and click Apply.
f. Click the Add delay located between both actions. Enter 5 and click OK.
g. Click OK.
5. Configure the fortideceptor_unban stitch:
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, fortideceptor_unban.
c. Click Add Trigger. Select fdc_Notify_Unban and click Apply.
d. Click Add Action. Select email_log and click Apply.
e. Click Add Action. Select fdc_unban and click Apply.
f. Click the Add delay located between both actions. Enter 5 and click OK.
g. Click OK.
To configure stitches with the Fabric connector event trigger in the CLI:
1. Configure the triggers:
config system automation-trigger
edit "fdc_Insider_Threat"
set description "Insider_Threat"
set event-type fabric-event
set serial "FDC-VMTM210000**"
set fabric-event-name "insider_threat"
next
edit "fdc_Notify_Ban"
set description "Notify_Ban"
set event-type fabric-event
set serial "FDC-VMTM210000**"
set fabric-event-name "notify_ban"
next
edit "fdc_Notify_Unban"
set description "Notify_Unban"
set event-type fabric-event
set serial "FDC-VMTM210000**"
set fabric-event-name "notify_unban"
next
end
FortiOS 7.6.2 Administration Guide 3629
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,629
|
Fortinet Security Fabric
2. Configure the actions:
config system automation-action
edit "IP Ban"
set action-type ban-ip
next
edit "fdc_unban"
set action-type cli-script
set script "diagnose user banned-ip delete src4 %%log.srcip%%"
set output-size 10
set timeout 0
set accprofile "super_admin"
next
edit "email_log"
set action-type email
set email-to "*******@fortinet.com"
set email-subject "CSF stitch alert"
next
end
3. Configure the stitches:
config system automation-stitch
edit "fortideceptor_threat"
set trigger "fdc_Insider_Threat"
config actions
edit 1
set action "email_log"
set required enable
next
edit 2
set action "IP Ban"
set delay 5
set required enable
next
end
next
edit "fortideceptor_ban"
set trigger "fdc_Notify_Ban"
config actions
edit 1
set action "email_log"
set required enable
next
edit 2
set action "IP Ban"
set delay 5
set required enable
next
end
next
edit "fortideceptor_unban"
set trigger "fdc_Notify_Unban"
config actions
edit 1
set action "email_log"
set required enable
FortiOS 7.6.2 Administration Guide 3630
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,630
|
Fortinet Security Fabric
next
edit 2
set action "fdc_unban"
set delay 5
set required enable
next
end
next
end
Verification
A device with IP 172.16.200.33 uses SSH to access the decoy (ubuntu16) deployed in the FortiDeceptor. The
FortiDeceptor will detect the attacker IP 172.16.200.33, automatically quarantine it, and send the insider threat
notification to the FortiGate. This notification will trigger the fortideceptor_threat stitch due to the insider threat event
trigger, so an email alert is sent and the attacker IP (172.16.200.33) is banned.
In FortiDeceptor, if the attacker IP (172.16.200.33) is manually blocked or unblocked, the FortiDeceptor will send out the
internal block or unblock notification to FortiGate (see Quarantine Status for more details). This notification will trigger
the fortideceptor_ban or fortideceptor_unban stitch due the notify ban or unban event trigger. An email alert is sent, and
based on the event, the IP is banned or the CLI script runs to unban the IP.
To view the quarantine details in FortiDeceptor:
1. Go to Fabric > Quarantine Status.
a. Automatic quarantine:
b. Manual block or unblock:
To confirm that the stitch was triggered in the FortiOS GUI:
1. Go to Security Fabric > Automation and select the Stitch tab.
a. Triggered insider threat:
FortiOS 7.6.2 Administration Guide 3631
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,631
|
Fortinet Security Fabric
b. Triggered notify ban or unban:
To view the quarantined IP details in the FortiOS CLI:
# diagnose user banned-ip list
src-ip-addr created expires cause
172.16.200.33 Wed Jan 5 15:57:41 2022 indefinite Administrative
If the IP is unbanned by the stitch, the list will be empty:
# diagnose user banned-ip list
src-ip-addr created expires cause
FortiOS event log trigger
You can configure a FortiOS event log trigger for when a specific event log ID occurs. You can select multiple event log
IDs, and apply log field filters. FortiOS event log triggers can be configured from the Security Fabric > Automation
> Trigger page, or by using the shortcut on the Log & Report > System Events > Logs page.
A maximum of 16 log IDs can be set as triggers for the event log.
To configure a FortiOS event log trigger in the GUI:
1. Go to Security Fabric > Automation, select the Trigger tab, and click Create New.
2. In the Miscellaneous section, click FortiOS Event Log.
3. Enter a name and description.
4. In the Event field, click the + to select multiple event log IDs.
The Event options correspond to the Message Meaning listed in the FortiOS Log Message Reference. Hover over
an entry to view the tooltip that includes the event ID and log name. In this example, the Admin login successful
event in the GUI corresponds to log ID 32001, which is LOG_ID_ADMIN_LOGIN_SUCC.
FortiOS 7.6.2 Administration Guide 3632
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,632
|
Fortinet Security Fabric
5. In the Field filter(s) field, click the + to add multiple field filters. The configured filters must match in order for the
stitch to be triggered.
a. To view the list of available fields for a log, refer to the FortiOS Log Message Reference by appending the log
ID to the document URL (https://docs.fortinet.com/document/fortigate/7.6.2/fortios-log-messagereference/<log_ID>).
6. Click OK.
To configure a FortiOS event log trigger in the CLI:
config system automation-trigger
edit "event_login_logout"
set description "trigger for login logout event"
set event-type event-log
set logid 32001 32003
config fields
edit 1
set name "user"
set value "csf"
next
edit 2
set name "srcip"
set value "10.6.30.254"
next
FortiOS 7.6.2 Administration Guide 3633
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,633
|
Fortinet Security Fabric
end
next
end
System Events page shortcut
A FortiOS Event Log trigger can be created using the shortcut on the System Events > Logs page. In this example, a
trigger is created for a FortiGate update succeeded event log.
To configure a FortiOS Event Log trigger from the System Events page:
1. Go to Log & Report > System Events and select the Logs tab.
2. Select a log for a successful FortiGate update, then right-click and select Create Automation Trigger.
The Create New Automation Trigger pane opens to configure the FortiOS Event Log settings.
3. Enter a name (such as trigger-update). The Event field is already populated with FortiGate update succeeded.
FortiOS 7.6.2 Administration Guide 3634
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,634
|
Fortinet Security Fabric
4. Optionally in the Field filter(s) field, click the + to add multiple field filters. The configured filters must match in order
for the stitch to be triggered.
5. Click OK. The trigger is now listed on the Security Fabric > Automation > Trigger page.
Event log category triggers
There are six default automation triggers based on event log categories:
l Anomaly logs
l IPS logs
l SSH logs
l Traffic violations
l Virus logs
l Web filter violations
When multi-VDOM mode is enabled, individual VDOMs can be specified so that the trigger is only applied to those
VDOMs.
config system automation-trigger
edit "Anomaly Logs"
set trigger-type event-based
set event-type anomaly-logs
FortiOS 7.6.2 Administration Guide 3635
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,635
|
Fortinet Security Fabric
set vdom <name>
next
edit "IPS Logs"
set trigger-type event-based
set event-type ips-logs
set vdom <name>
next
edit "SSH Logs"
set trigger-type event-based
set event-type ssh-logs
set vdom <name>
next
edit "Traffic Violation"
set trigger-type event-based
set event-type traffic-violation
set vdom <name>
next
edit "Virus Logs"
set trigger-type event-based
set event-type virus-logs
set vdom <name>
next
edit "Webfilter Violation"
set trigger-type event-based
set event-type webfilter-violation
set vdom <name>
next
end
A maximum of 16 log IDs can be set as triggers for the event log.
Example
In this example, an automation stitch is created that uses the anomaly logs trigger and an email notification action. The
trigger specifies which VDOMs should be used. There is a three-second delay between the trigger and action.
To configure an automation stitch with the anomaly logs trigger in the GUI:
1. Configure the trigger:
a. Go to Security Fabric > Automation, select the Trigger tab.
b. Edit the Anomaly Logs trigger.
c. Add the required VDOMs (root, vdom-nat, vdom-tp).
FortiOS 7.6.2 Administration Guide 3636
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,636
|
Fortinet Security Fabric
d. Click OK.
2. Configure the action:
a. Go to Security Fabric > Automation, select the Action tab, and click Create New.
b. In the Notifications section, click Email and enter the following:
Name email_default_rep_message
To Enter an email address
Subject CSF stitch alert
Replacement message Enable
c. Click OK.
3. Configure the stitch:
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, anomaly-logs-stitch.
c. Click Add Trigger. Select Anomaly Logs and click Apply.
d. Click Add Action. Select email_default_rep_message and click Apply.
e. Click Add delay (between the trigger and action). Enter 3 and click OK.
f. Click OK.
To configure an automation stitch with the anomaly logs trigger in the CLI:
1. Configure the trigger:
config system automation-trigger
edit "Anomaly Logs"
set event-type anomaly-logs
set vdom "root" "vdom-nat" "vdom-tp"
next
end
2. Configure the action:
config system automation-action
edit "email_default_rep_message"
set action-type email
set email-to "admin@fortinet.com"
FortiOS 7.6.2 Administration Guide 3637
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,637
|
Fortinet Security Fabric
set email-subject "CSF stitch alert"
set replacement-message enable
next
end
3. Configure the stitch:
config system automation-stitch
edit "anomaly-logs-stitch"
set description "anomaly-logs"
set trigger "Anomaly Logs"
config actions
edit 1
set action "email_default_rep_message"
set delay 3
set required enable
next
end
next
end
Verification
Once the anomaly log is generated, the automation stitch is triggered end the email notification is sent.
To confirm that the stitch was triggered in the GUI:
1. Go to Security Fabric > Automation and select the Stitch tab.
2. Verify the Last Triggered column.
To confirm that the stitch was triggered in the CLI:
# diagnose test application autod 2
...
stitch: anomaly-logs-stitch
destinations: all
trigger: Anomaly Logs
FortiOS 7.6.2 Administration Guide 3638
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,638
|
Fortinet Security Fabric
type:anomaly logs
field ids:
(id:6)vd=root,vdom-nat,vdom-tp
local hit: 1 relayed to: 0 relayed from: 0
actions:
email_default_rep_message type:email interval:0
delay:3 required:yes
subject: CSF stitch alert
body: %%log%%
sender:
mailto:admin@fortinet.com;
Certificate expiration trigger
The local certificate expiry trigger (local-certificate-near-expiry) can be used in an automation stitch if a usersupplied local certificate used for SSL VPN, deep inspection, or other purpose is about to expire. This trigger relies on a
VPN certificate setting in the CLI configuration setting for the certificate log expiring warning threshold:
config vpn certificate setting
set cert-expire-warning <integer>
end
cert-expire-warning
<integer>
Set the certificate log expiring warning threshold, in days (0 - 100, default = 14).
Example
In this example, the default local certificate expiry trigger is used with an email notification action to remind an
administrator to re-sign or load a new local certificate to avoid any service interruptions. The local certificate, fw-cert-30-
days, will expire in 30 days. The certificate log expiring warning threshold is set to 31 days.
To configure the certificate log expiring warning threshold:
config vpn certificate setting
set cert-expire-warning 31
end
To configure an automation stitch with the local certificate expiry trigger in the GUI:
1. Configure the action:
a. Go to Security Fabric > Automation, select the Action tab, and click Create New.
b. In the Notifications section, click Email, and enter the following:
Name email_no_rep_message
To Enter an email address.
Subject CSF stitch alert
c. Click OK.
2. Configure the stitch:
FortiOS 7.6.2 Administration Guide 3639
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,639
|
Fortinet Security Fabric
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, cert-expiry.
c. Click Add Trigger. Select Local Certificate Expiry and click Apply.
d. Click Add Action. Select email_no_rep_message and click Apply.
e. Click OK.
To configure an automation stitch with the local certificate expiry trigger in the CLI:
1. Configure the trigger:
config system automation-trigger
edit "Local Certificate Expiry"
set description "A local certificate is near expiration."
set event-type local-cert-near-expiry
next
end
2. Configure the action:
config system automation-action
edit "email_no_rep_message"
set action-type email
set email-to "*******@fortinet.com"
set email-subject "CSF stitch alert"
next
end
3. Configure the stitch:
config system automation-stitch
edit "cert-expiry"
set trigger "Local Certificate Expiry"
config actions
edit 1
set action "email_no_rep_message"
set required enable
next
end
next
end
Verification
Once the event log is generated for the local certificate expiry, the automation stitch is triggered end the email notification
is sent.
FortiOS 7.6.2 Administration Guide 3640
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,640
|
Fortinet Security Fabric
To confirm that the stitch was triggered in the GUI:
1. Go to Security Fabric > Automation and select the Stitch tab.
2. Verify the Last Triggered column.
To confirm that the stitch was triggered in the CLI:
# diagnose test application autod 3
alert mail log count: 0
stitch: cert-expiry
local hit: 1 relayed to: 0 relayed from: 0
last trigger:Thu Jun 23 09:32:21 2022
last relay:
actions:
email_no_rep_message:
done: 1 relayed to: 0 relayed from: 0
last trigger:Thu Jun 23 09:32:21 2022
last relay:
logid to stitch mapping:
id:22207 local hit: 1 relayed hits: 0
cert-expiry
Schedule trigger
The schedule automation trigger can be used for monthly, weekly, daily, hourly, or one-time triggers, including a onetime configuration backup to a disk, a reboot, or a shutdown.
config system automation-trigger
edit <name>
set trigger-type scheduled
set trigger-frequency {hourly | daily | weekly | monthly | once}
set trigger-hour <inetger>
set trigger-minute <integer>
set trigger-weekday {sunday | monday | tuesday | wednesday | thursday | friday |
saturday}
set trigger-day <integer>
set trigger-datetime <YYYY-MM-DD HH:MM:SS>
next
end
trigger-frequency {hourly
| daily | weekly |
monthly | once}
Set the scheduled trigger frequency (default = daily).
trigger-hour <inetger> Set the hour of the day on which to trigger (0 - 23, default = 1), available for daily,
weekly, and monthly schedule.
FortiOS 7.6.2 Administration Guide 3641
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,641
|
Fortinet Security Fabric
trigger-minute <integer> Set the minute of the hour on which to trigger (0 - 59, default = 0), available for
hourly, daily, weekly, and monthly schedule.
trigger-weekday {sunday |
monday | tuesday |
wednesday | thursday
| friday | saturday}
Set the day of the week to trigger, available for weekly schedule.
trigger-day <integer> Set the day within a month to trigger, available for monthly schedule.
trigger-datetime <YYYYMM-DD HH:MM:SS>
Set the trigger time in YYYY-MM-DD HH:MM:SS format for one-time triggers.
Example
In this example, an automation stitch is created to trigger a one-time configuration backup to a disk. The backup will
occur August 5, 2022 at 4:00 AM.
To schedule a one-time automation stitch in the GUI:
1. Configure the trigger:
a. Go to Security Fabric > Automation, select the Trigger tab, and click Create New.
b. In the Miscellaneous section, click Schedule.
c. Enter a name (schedule-once) in the Name field.
d. In the Frequency dropdown list, select Once.
e. Select when the trigger will occur in the Date/Time fields.
f. Click OK.
2. Configure the stitch:
a. Go to Security Fabric > Automation, select the Stitch tab, and click Create New.
b. Enter the name, backup-once.
c. Click Add Trigger. Select schedule-once and click Apply.
d. Click Add Action. Select Backup Config Disk and click Apply.
FortiOS 7.6.2 Administration Guide 3642
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,642
|
Fortinet Security Fabric
e. Click OK. The backup configuration will occur once at the date and time you set.
To schedule a one-time automation stitch in the CLI:
1. Configure the trigger:
config system automation-trigger
edit "schedule-once"
set trigger-type scheduled
set trigger-frequency once
set trigger-datetime 2022-08-05 04:00:00
next
end
2. Configure the action:
config system automation-action
edit "Backup Config Disk"
set description "Backup the configuration on disk."
set action-type system-actions
set system-action backup-config
next
end
3. Configure the stitch:
config system automation-stitch
edit "backup-once"
set trigger "schedule-once"
config actions
edit 1
set action "Backup Config Disk"
set required enable
next
end
next
end
4. To view automation stitch information:
FortiOS 7.6.2 Administration Guide 3643
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,643
|
Fortinet Security Fabric
# diagnose test application autod 3
stitch: backup-once (scheduled)
local hit: 0 relayed to: 0 relayed from: 0
last trigger: last relay:
next scheduled trigger:Fri Aug 5 05:00:00 2022
actions:
Backup Config Dis:
done: 0 relayed to: 0 relayed from: 0
last trigger: last relay:
logid to stitch mapping:
id:0 (scheduled stitches) local hit: 0 relayed hits: 0
backup-once
Actions
There are two types of automation actions that can be configured in automation stitches: static and dynamic.
Static automation actions are included in FortiOS by default. They require only a name, description, and one setting.
Static automation actions can be edited, but they cannot be deleted.
Dynamic automation actions require multiple settings to be configured. Dynamic automation actions can be created by
clicking the Create New button on the Action tab, or clicking Create within the Create Automation Stitch page.
Multiple actions can be added to an automation stitch. Actions can be reorganized in the Edit Automation Stitch page by
dragging and dropping the actions in the diagram.
The following table outlines the available static actions.
Action Description
Access Layer Quarantine This option is only available for Compromised Host triggers.
Quarantine the MAC address on access layer devices (FortiSwitch and FortiAP).
FortiClient Quarantine This option is only available for Compromised Host triggers.
Use FortiClient EMS to block all traffic from the source addresses that are flagged
as compromised hosts.
Quarantined devices are flagged on the Security Fabric topology views. Go to the
Dashboard > Assets & Identities > Quarantine widget to view and manage
quarantined IP addresses.
FortiNAC Quarantine This option is only available for Compromised Host and Incoming Webhook
triggers.
Use FortiNAC to quarantine a client PC and disable its MAC address. See
FortiNAC Quarantine action on page 3646 for details.
IP Ban This option is only available for Compromised Host triggers.
Block all traffic from the source addresses flagged by the IoC.
Go to the Dashboard > Assets & Identities > Quarantine widget to view and
manage quarantined IP addresses.
FortiOS 7.6.2 Administration Guide 3644
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,644
|
Fortinet Security Fabric
Action Description
System Action > Backup
Config Disk
Back up the FortiGate's configuration. The default minimum interval is 0 seconds.
See System actions on page 3704 for an example.
System Action > Reboot
FortiGate
Reboot the FortiGate. The default minimum interval is 5 minutes (300 seconds in
the CLI). See System actions on page 3704 for an example.
System Action > Shutdown
FortiGate
Shut down the FortiGate. The default minimum interval is 0 seconds.
The following table outlines the available dynamic actions.
Category Action Description
Security Response
VMware NSX Security
Tag
This option is only available for Compromised Host triggers.
If an endpoint instance in a VMware NSX environment is
compromised, the configured security tag is assigned to the
compromised endpoint. See VMware NSX security tag action on
page 3649 and VMware NSX-T security tag action on page 3654 for
details.
Notifications
Email Send a custom email message to the selected recipients. At least one
recipient and an email subject must be specified.
Enable Send to FortiCare email to send the message to the email
address associated with the FortiCare Support entitlement. This is the
FortiCloud email address visible on the System > FortiGuard page
under the FortiCare Support license information.
The email body can use parameters from logs or previous action
results. Wrapping the parameter with %% will replace the expression
with the JSON value for the parameter, for example:
%%results.source%% is the source property from the previous
action.
Replacement messages can be enabled in the email body to create
branded email alerts. See Replacement messages for email alerts on
page 3658 for details.
FortiExplorer
Notification
Send push notifications to FortiExplorer.
The FortiGate must be registered to FortiCare on the mobile app that
will receive the notification.
Slack Notification Send a notification to a Slack channel. See Slack Notification action
on page 3662 for details.
Microsoft Teams
Notification
Send a notification to channels in Microsoft Teams. See Microsoft
Teams Notification action on page 3666 for details.
Cloud Compute
FortiOS 7.6.2 Administration Guide 3645
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,645
|
Fortinet Security Fabric
Category Action Description
AWS Lambda Send log data to an integrated AWS service. See AWS Lambda
action on page 3671 for details.
Azure Function Send log data to an Azure function. See Azure Function action on
page 3673 for details.
Google Cloud Function Send log data to a Google Cloud function. See Google Cloud
Function action on page 3674 for details.
AliCloud Function Send log data to an AliCloud function. See AliCloud Function action
on page 3676 for details.
General
CLI Script Run one or more CLI scripts. See CLI script action on page 3678 for
details. See Execute a CLI script based on memory and CPU
thresholds on page 3682 for an example.
Webhook Send an HTTP request using a REST callback. See Webhook action
on page 3686 for details, and Slack integration webhook on page
3700 and Microsoft Teams integration webhook on page 3702 for
examples.
Alert Generate a FortiOS dashboard alert.
This option is only available in the CLI.
Disable SSID Disable the SSID interface.
This option is only available in the CLI.
FortiNAC Quarantine action
Users can configure an automation stitch with the FortiNAC Quarantine action with a Compromised Host or Incoming
Webhook trigger. When the automation is triggered, the client PC will be quarantined and its MAC address is disabled in
the configured FortiNAC.
In this example, the FortiNAC has been configured to join an enabled Security Fabric. See Configuring FortiNAC on
page 3510 for more information.
The FortiNAC must also be configured to isolate disabled hosts:
l Endpoints connecting to FortiWiFi or wired ports on FortiGate:
l See the requisite Configure FortiNAC section in the FortiGate Endpoint Management Integration Guide.
l Endpoints connecting to FortiAP:
l Set the Dead End VLAN. See Model configuration.
l Endpoints connecting to FortiSwitch:
l Set the Dead End VLAN. See Model configuration.
l Add the switch to the physical address filtering group. See Systems groups and Modify a group.
FortiOS 7.6.2 Administration Guide 3646
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,646
|
Fortinet Security Fabric
To configure an automation stitch with a FortiNAC quarantine action in the GUI:
1. Create a new API user and generate the API key:
a. Go to System > Administrators and click Create New > REST API Admin.
b. Configure the settings as needed.
c. Click OK. The New API key window opens.
d. Copy the key to the clipboard and click Close.
e. Click OK.
2. Configure the automation stitch trigger:
a. Go to Security Fabric > Automation and click Create New.
b. Enter the stitch name (auto_webhook).
c. Click Add Trigger.
d. Click Create and select Incoming Webhook.
e. Enter a name (auto_webhook).
f. Click OK.
g. Paste the key in the API admin key field.
h. Click OK.
i. Select the trigger in the list and click Apply.
3. Configure the automation stitch action:
a. Click Add Action.
b. Select FortiNAC Quarantine.
c. Click Apply.
d. Click OK.
FortiOS 7.6.2 Administration Guide 3647
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,647
|
Fortinet Security Fabric
4. On a Linux PC accessible by the FortiGate, create a cURL request to trigger the automation stitch:
root@pc56:~# curl -k -X POST -H 'Authorization: Bearer ckx7d9xdzzx14Nztd1Ncr701dpwwy9' -
-data '{ "srcip": "1.1.1.1", "mac":"00:0C:29:0B:A6:16", "fctuid":
"A8BA0B12DA694E47BA4ADF24F8358E2F"}'
https://172.17.48.225:4431/api/v2/monitor/system/automation-stitch/webhook/auto_webhook
5. In FortiOS, verify the automation stitch is triggered and the action is executed:
a. Go to Log & Report > System Events to confirm that the stitch was activated.
b. Go to Security Fabric > Automation to see the last time that the stitch was triggered.
In FortiNAC, the Host View shows the status of the client PC. It is quarantined and its MAC address is disabled.
To configure an automation stitch with a FortiNAC quarantine action in the CLI:
1. Create a new API user and generate the API key:
config system api-user
edit "g-api-rw-user"
set api-key ************
set accprofile "super_admin"
set vdom "root"
config trusthost
edit 1
set ipv4-trusthost 10.6.30.0 255.255.255.0
next
end
next
end
2. Configure the automation trigger:
config system automation-trigger
edit "auto_webhook"
set event-type incoming-webhook
next
end
3. Configure the automation action:
config system automation-action
edit "FortiNAC Quarantine"
set action-type quarantine-fortinac
FortiOS 7.6.2 Administration Guide 3648
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,648
|
Fortinet Security Fabric
next
end
4. Configure the automation stitch:
config system automation-stitch
edit "auto_webhook"
set trigger "auto_webhook"
config actions
edit 1
set action "FortiNAC Quarantine"
set required enable
next
end
next
end
5. On a Linux PC accessible by the FortiGate, create a cURL request to trigger the automation stitch:
root@pc56:~# curl -k -X POST -H 'Authorization: Bearer ckx7d9xdzzx14Nztd1Ncr701dpwwy9' -
-data '{ "srcip": "1.1.1.1", "mac":"00:0C:29:0B:A6:16", "fctuid":
"A8BA0B12DA694E47BA4ADF24F8358E2F"}'
https://172.17.48.225:4431/api/v2/monitor/system/automation-stitch/webhook/auto_webhook
6. In FortiOS, verify that the automation stitch is triggered and the action is executed:
# diagnose test application autod 2
csf: enabled root:yes
version:1592949233 sync time:Tue Jun 23 15:03:15 2020
total stitches activated: 1
stitch: auto_webhook
destinations: all
trigger: auto_webhook
(id:15)service=auto_webhook
local hit: 1 relayed to: 0 relayed from: 0
actions:
FortiNAC Quarantine type:quarantine-fortinac interval:0
date=2020-06-23 time=15:25:44 logdesc="Internal Message" path="system" name="automationstitch" action="webhook" mkey="auto_webhook" srcip="1.1.1.1" mac="00:0C:29:0B:A6:16"
fctuid="A8BA0B12DA694E47BA4ADF24F8358E2F" vdom="root" service="auto_webhook"
date=2020-06-23 time=15:25:44 logid="0100046600" type="event" subtype="system"
level="notice" vd="root" eventtime=1592951144401490054 tz="-0700" logdesc="Automation
stitch triggered" stitch="auto_webhook" trigger="auto_webhook" stitchaction="FortiNAC
Quarantine" from="log" msg="stitch:auto_webhook is triggered."
VMware NSX security tag action
If an endpoint instance in a VMware NSX environment is compromised, this action will assign the configured security tag
to the compromised endpoint.
This action is only available when the automation trigger is set to compromised host.
FortiOS 7.6.2 Administration Guide 3649
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,649
|
Fortinet Security Fabric
To set up the NSX quarantine action, you need to:
1. Configure a VMware NSX SDN connector
2. Configure an NSX security tag automation stitch
3. Configure FortiAnalyzer logging on the FortiGate
Configure a VMware NSX SDN connector
The FortiGate retrieves security tags from the VMware NSX server through the connector.
To configure a VMware NSX SDN connector in the GUI:
1. Go to Security Fabric > External Connectors.
2. Click Create New.
3. Select VMware NSX.
4. Configure the settings as needed.
5. Click OK.
To configure a VMware NSX SDN connector in the CLI:
config system sdn-connector
edit "nsx"
set type nsx
set server "172.18.64.32"
set username "admin"
set password xxxxxxxxxxxx
next
end
FortiOS 7.6.2 Administration Guide 3650
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,650
|
Fortinet Security Fabric
Configure an NSX security tag automation stitch
Security tags are retrieved from the VMware NSX server through the NSX SDN connector.
To configure an automation stitch with an NSX security tag in the GUI:
1. Go to Security Fabric > Automation and click Create New.
2. Enter the stitch name (pcui-test).
3. Configure the trigger:
a. Click Add Trigger.
b. Select Compromised Host.
c. Click Apply.
4. Configure the VMware NSX Security Tag action:
a. Click Add Action.
b. Click Create and select VMware NSX Security Tag.
c. Enter the following:
Name pcui-test_quarantine-nsx
Specify NSX server(s) Enable and select the SDN connector
Security tag Select an existing tag, or create a new one
d. Click OK.
e. Select the action in the list and click Apply.
5. Click OK.
To configure an automation stitch with an NSX security tag in the CLI:
1. Create the automation trigger:
config system automation-trigger
edit "Compromised Host"
next
end
FortiOS 7.6.2 Administration Guide 3651
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,651
|
Fortinet Security Fabric
2. Create the automation action:
config system automation-action
edit "pcui-test_quarantine-nsx"
set action-type quarantine-nsx
set security-tag "pcui-tag2"
set sdn-connector "nsx"
next
end
3. Create the automation stitch:
config system automation-stitch
edit "pcui-test"
set trigger "Compromised Host"
config actions
edit 1
set action "pcui-test_quarantine-nsx"
set required enable
next
end
next
end
Configure FortiAnalyzer logging on the FortiGate
The FortiAnalyzer is used to send endpoint compromise notification to the FortiGate.
See Configuring FortiAnalyzer on page 3451 for more information.
To configure FortiAnalyzer logging in the GUI:
1. Go to Security Fabric > Fabric Connectors and double-click the Logging & Analytics card.
2. In the FortiAnalyzer tab, ensure the Status is Enabled, and configure the settings as needed.
FortiOS 7.6.2 Administration Guide 3652
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,652
|
Fortinet Security Fabric
3. Click OK.
To configure FortiAnalyzer logging in the CLI:
config log fortianalyzer setting
set status enable
set server "172.18.64.234"
set serial "FL-8HFT000000000"
set upload-option realtime
set reliable enable
end
When an endpoint instance is compromised
When an endpoint instance, such as pcui-ubuntu2, in the VMware NSX environment is compromised, the automation
stitch is triggered. The FortiGate then assigns the configured security tag, pcui-tag2 in this example, to the compromised
NSX endpoint instance.
FortiOS 7.6.2 Administration Guide 3653
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,653
|
Fortinet Security Fabric
VMware NSX-T security tag action
VMware NSX SDN connectors' vCenter server and credentials can be configured so the FortiGate resolves NSX-T VMs.
The FortiGate uses the VMWare NSX Security Tag automation action to assign a tag to the VM through an automation
stitch.
The FortiGate is notified of a compromised host on the NSX-T network by an incoming webhook or other means, such as
FortiGuard IOC. An automation stitch can be configured to process this trigger and action it by assigning a VMware NSX
security tag on the VM instance.
To configure an automation stitch to assign a security tag to NSX-T VMs in the GUI:
1. Configure the NSX SDN connector:
a. Go to Security Fabric > External Connectors and click Create New.
b. Select VMware NSX.
c. Configure the connector settings.
d. Enable vCenter Settings and configure as needed.
FortiOS 7.6.2 Administration Guide 3654
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,654
|
Fortinet Security Fabric
e. Click OK.
2. Configure the automation stitch trigger:
a. Go to Security Fabric > Automation and click Create New.
b. Enter the stitch name (auto_webhook).
c. Click Add Trigger.
d. Click Create and select Incoming Webhook.
e. Enter a name (auto_webhook).
f. Click OK to close the Incoming Webhook URL prompt.
g. Select the trigger in the list and click Apply.
3. Configure the automation stitch action:
a. Click Add Action.
b. Click Create and select VMware NSX Security Tag.
c. Enter the following:
Name auto_webhook_quarantine-nsx
Specify NSX server(s) Enable and select the SDN connector
Security tag Select an existing tag, or create a new one
FortiOS 7.6.2 Administration Guide 3655
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.