Configuring Sophos XG Firewall Connectors

Stellar Cyber Academy icon Learn more at Stellar Cyber Academy.

The following link takes you to a course on the Stellar Cyber Academy technical training portal where you can learn more about this topic by watching the suggested lessons.

(2024) ADMIN - Connector Example - Sophos Firewall (02h:22m)

Get introduced to configuring, testing, and validating a firewall connector using a Sophos firewall within the Stellar Cyber Platform. Understand the essentials of setting up IP host groups and firewall rules, as well as configuring API communication for firewall management.

Learn where connectors fit into the Stellar Cyber Platform network architecture. Explore the capabilities of various connectors, including data collection and response actions, and understand how connectors enable communication with firewalls, Active Directory, and other technologies.

Configure the Sophos firewall connector by setting up host groups, firewall rules, and enabling API access. Learn to create the connector in the Stellar Cyber UI and configure it to interact securely with the Sophos firewall for threat response actions.

Watch a demonstration on configuring the Sophos firewall connector, covering each step from setting firewall rules to configuring API settings in the Stellar Cyber Platform.

Test the connector to ensure it communicates successfully with the Sophos firewall. Validate the API settings and confirm connectivity between the firewall and Stellar Cyber Platform.

Follow a demonstration on testing the Sophos firewall connector. Confirm API connectivity and view logs to ensure the connector is ready for operational use.

Verify the functionality of the connector by manually using the respond action to block IP addresses. Understand how administrators and SOC analysts can utilize this action to manage firewall rules dynamically from the Stellar Cyber Platform.

Watch a demonstration on verifying the respond action in the firewall connector. Learn to block and unblock IP addresses manually, observing real-time changes to firewall rules and connectivity.

Use Interflow detail actions to automate firewall rules based on Interflow records. See how this method simplifies blocking IP addresses from the Stellar Cyber Platform for SOC analysts.

Follow a practical demo of using the Interflow detail action to automatically trigger firewall blocks. Understand how to link Interflow data to firewall actions for efficient threat response.

Discover how to set up automated threat hunting (ATH) actions in the firewall connector, automating IP blocking based on predefined criteria without manual intervention.

Watch a demonstration on configuring ATH actions within the connector. See how ATH playbooks enable automated IP blocking on the firewall, showcasing advanced response capabilities in the Stellar Cyber Platform.

The first time you access a link on the portal during a session, you must log in to access content.

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: Sophos XG 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

Block IP

srcip or dstip

Third Party Native Alert Integration Details

N/A

Required Credentials and Configurations

  • User Name, Password, Device IP Address, Source IP Group, Destination IP Group, and Device Port

Connecting a Sophos XG Firewall Connector

To connect a Sophos XG firewall:

  1. Create IP host groups and add them to firewall deny rules in Sophos XG
    1. Enable API configuration

      • Check Enable

      • In Allowed IP address, enter the source IP address of the device making the API calls, for example, the local Stellar Cyber sensor IP address

  2. Add the connector in Stellar Cyber
  3. Test the connector

Adding the Connector in Stellar Cyber

Stellar Cyber Academy icon See the top of this page for recommended lessons about this section at Stellar Cyber Academy.

To add a new Sophos XG 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 Sophos XG 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.

  10. Click Next. The Configuration tab appears.

    The asterisk (*) indicates a required field.

  11. Enter the User Name to log in to the firewall.

  12. Enter the Password for that user.

    The password should not include non-ASCII special characters.

  13. Enter the Device IP Address.

  14. Enter the Source IP Group to which to add the IP address.

  15. Enter the Destination IP Group to which to add the IP address.

  16. Enter the Device Port. The default Admin console HTTPS port configured in the Sophos XG firewall is 4444.

  17. Click Next. The final confirmation tab appears.

  18. Click Submit.

The new firewall connector is immediately active.

Testing the Connector

Stellar Cyber Academy icon See the top of this page for recommended lessons about this section at Stellar Cyber Academy.

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).

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 | 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.

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.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

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.