Configuring Barracuda 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: Barracuda Firewall

Adding a Barracuda Firewall Connector

To add a new Barracuda firewall connector:

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

Creating Firewall Rules

To trigger firewall actions you must have rules on your Barracuda firewall that you can trigger. Those rules must have network objects. You must:

1. Create a rule for blocking inbound IP addresses.

2. Configure a source network object . The Name of this object is the Source Network Object you will use when configuring the connector in Stellar Cyber.

3. Create a rule for blocking outbound IP addresses.

4. Configure a destination network object . The Name of this object is the Destination Network Object yo will use when configuring the connector in Stellar Cyber.

Enabling the Firewall API

You must enable the Barracuda firewall API for HTTPS. When you do, note:

• the HTTPS Port

• the API Token

You'll need both of these when configuring the connector in Stellar Cyber.

Adding the Connector in Stellar Cyber

To add a Barracuda firewall connector in Stellar Cyber:

1. Log in to Stellar Cyber.

2. Click System | Connectors (under Integrations). 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 Barracuda Firewall from the Type drop-down.

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

7. Enter a Name.

   Notes:

   • This field does not accept multibyte characters.
   • It is recommended that you follow a naming convention such as tenantname-connectortype.

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.

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

10. Click Next. The Configuration tab appears.

    

    The asterisk (*) indicates a required field.

11. Enter the API Token to access the firewall.

12. Enter the Device IP Address or FQDN.

13. Enter the Device Port you noted earlier.

14. Enter the name of the Source Network Object that you created earlier.

15. Enter the name of the Destination Network Object that you created earlier.

16. Click Next. The final confirmation tab appears.

    

17. 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 authentication and connectivity).

1. Click System | Connectors (under Integrations). The Connector Overview appears.

   

2. Locate the connector by name 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.