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
Capabilities
-
Collect: No
-
Respond: Yes
-
Native Alerts Mapped: No
-
Runs on: DP or Sensor
-
Interval: N/A
Collected Data
N/A
Domain
https://<Device IP Address>:<Device Port> where <Device IP Address> and <Device Port> are variables from the configuration of this connector |
Response Actions
Action |
Required Fields |
---|---|
|
Third Party Native Alert Integration Details
N/A
Required Credentials
-
API Token, Device IP Address, Device Port, Source Network Object, and Destination Network Object
Let us know if you find the above overview useful.
Adding a Barracuda Firewall Connector
To add a new Barracuda firewall 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:
-
Create a rule for blocking inbound IP addresses.
-
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.
-
Create a rule for blocking outbound IP addresses.
-
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:
-
Log in to Stellar Cyber.
-
Click System | Integration | Connectors. The Connector Overview appears.
-
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.
-
Choose Firewall from the Category drop-down.
-
Choose Barracuda Firewall from the Type drop-down.
-
For this connector, the supported Function is Respond, which is enabled already.
-
Enter a Name.
Notes:- This field does not accept multibyte characters.
- It is recommended that you follow a naming convention such as tenantname-connectortype.
-
Choose a Tenant Name. The Interflow records created by this connector include this tenant name.
-
Choose the device on which to run the connector.
-
Click Next. The Configuration tab appears.
The asterisk (*) indicates a required field.
-
Enter the API Token to access the firewall.
-
Enter the Device IP Address or FQDN.
-
Enter the Device Port you noted earlier.
-
Enter the name of the Source Network Object that you created earlier.
-
Enter the name of the Destination Network Object that you created earlier.
-
Click Next. The final confirmation tab appears.
-
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.
-
Click System | Integrations | Connectors. The Connector Overview appears.
-
Locate the connector that you added, or modified, or that you want to test.
-
Click Test at the right side of that row. The test runs immediately.
Note that you may run only one test at a time.
Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.
To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the button from the same row to review and correct issues.
The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.
Repeat the test as needed.
If the test fails, the common HTTP status error codes are as follows:
HTTP Error Code | HTTP Standard Error Name | Explanation | Recommendation |
---|---|---|---|
400 | Bad Request | This error occurs when there is an error in the connector configuration. |
Did you configure the connector correctly? |
401 | Unauthorized |
This error occurs when an authentication credential is invalid or when a user does not have sufficient privileges to access a specific API. |
Did you enter your credentials correctly? Are your credentials expired? Are your credentials entitled or licensed for that specific resource? |
403 | Forbidden | This error occurs when the permission or scope is not correct in a valid credential. |
Did you enter your credentials correctly? Do you have the required role or permissions for that credential? |
404 | Not Found | This error occurs when a URL path does not resolve to an entity. | Did you enter your API URL correctly? |
429 | Too Many Requests |
This error occurs when the API server receives too much traffic or if a user’s license or entitlement quota is exceeded. |
The server or user license/quota will eventually recover. The connector will periodically retry the query. If this occurs unexpectedly or too often, work with your API provider to investigate the server limits, user licensing, or quotas. |
For a full list of codes, refer to HTTP response status codes.