Configuring Fortigate Firewall Connectors

You can connect Stellar Cyber to firewalls so that you can quickly and easily implement firewall rules on those firewalls from within Stellar Cyber, while you are threat hunting. You can configure firewall actions or manually trigger a firewall action from the event display. For either action you must already have your firewall connected.

Connector Overview: Fortigate Firewall

               Let us know if you find the above overview useful.

Adding a Fortigate Firewall Connector

To add a Fortigate firewall connector:

1. Create firewall rules
2. Add the connector in Stellar Cyber
3. Test the connector

Creating Firewall Rules

To trigger firewall actions, you must have rules on your Fortigate firewall that you can trigger. Create the rules with a user that has access rights to modify rules.

Login to Fortigate with a user that you have previously logged in with. Or, if you have created a new user, log in to Fortigate as that user and accept the license agreement before starting this procedure.

To create the rules:

1. Create two address groups. You will use these when adding the connector in Stellar Cyber. When a firewall action is triggered, Stellar Cyber adds the IP address to one of these groups. For our examples, we used dst_group and src_group.

   

2. Create two deny policies. For the first one:

   • Source = src_group
   • Destination = all
   • Action = DENY

   

3. For the second one:

   • Source = all
   • Destination = dst_group
   • Action = DENY
4. Save the rules.

Adding the Connector in Stellar Cyber

To add a new Fortigate firewall connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | Integration | Connectors. The Connector Overview appears.

   

3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

   

   The asterisk (*) indicates a required field.

4. Choose Firewall from the Category drop-down.

5. Choose Fortigate from the Type drop-down.

6. For this connector, the supported Function is Respond, which is enabled already.

7. Enter a Name.

   This field does not accept multibyte characters.

8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

9. Choose the device on which to run the connector.

10. Click Next. The Configuration tab appears.

    

    The asterisk (*) indicates a required field.

11. Enter the User Name to log in to the firewall. This user must have access rights to modify a rule.

12. Enter the Password to log in to the firewall.

13. Enter the Device IP Address. This is the management IP address for the firewall.

14. Enter the Device Port. The default is 443.

15. Enter the Source IP Group to which to add the IP address. This is the source address group you created.

16. Enter the Destination IP Group to which to add the IP address. This is the destination address group you created.

17. Enter the Virtual Domain Name. This is the where the rules were created.

    Virtual Domains (VDOMs) are used to divide a Fortigate into two or more virtual units that function independently. By default, the management VDOM is root.

18. Click Next. The final confirmation tab appears.

    

19. Click Submit.

The new firewall connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

1. Click System | Integrations | Connectors. The Connector Overview appears.

   

2. Locate the connector that you added, or modified, or that you want to test.

3. Click Test at the right side of that row. The test runs immediately.

   Note that you may run only one test at a time.

Display sample messages...

Success !

Failure with summary of issue: Show More example detail: