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

               Let us know if you find the above overview useful.

Adding an AWS Firewall Connector

To add an AWS firewall connector:

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

Prerequisites

The following permissions are required:

• DescribeNetworkAcls

• ReplaceNetworkAclEntry

• CreateNetworkAclEntry

• DeleteNetworkAclEntry

An example of the JSON policy document is as follows:

The following is just an EXAMPLE. You must modify this JSON to match the resources in your own environment.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeNetworkAcls",
                "ec2:ReplaceNetworkAclEntry",
                "ec2:CreateNetworkAclEntry",
                "ec2:DeleteNetworkAclEntry"
            ],
            "Resource": "arn:aws:ec2:<region>:<AWS account id>:network-acl/<network ACL id>",
            "Condition": {
                "StringEquals": {
                    "ec2:Region": "<region>"
                }
            }
        }
    ]
}

For example:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeNetworkAcls",
                "ec2:ReplaceNetworkAclEntry",
                "ec2:CreateNetworkAclEntry",
                "ec2:DeleteNetworkAclEntry"
            ],
            "Resource": "arn:aws:ec2:us-west-2:0018xxxxxx33:network-acl/acl-0469dfdd77xxxxxx2",
            "Condition": {
                "StringEquals": {
                    "ec2:Region": "us-west-2"
                }
            }
        }
    ]
}

Adding the Connector in Stellar Cyber

To add a new AWS 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 AWS 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 Access Key ID to log in to the firewall.

12. Enter the Secret Key to log in to the firewall.

13. Enter the ACL ID.

14. Enter the Region Name.

15. Click Next. The final confirmation tab appears.

    

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