Configuring AWS CloudWatch Connectors

The AWS CloudWatch connector allows Stellar Cyber to collect AWS ECS/EKS, WAF, VPC Flow, and Amazon GuardDuty logs. Use these instructions to obtain credentials and set up the connector.

Although the AWS CloudWatch connector may successfully import other logs, only AWS Elastic Container Service (ECS)/Elastic Kubernetes Service (EKS), Web Application Firewall (WAF), VPC Flow, and Amazon GuardDuty logs are supported in this release due to performance issues that can occur with other log types. Stellar Cyber is working on enhancements for other log types in future releases.

You can use an AWS CloudWatch connector to ingest logs from Amazon GuardDuty findings by exporting those logs to your AWS CloudWatch service. Refer to Amazon's documentation for configuration of this export: https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_exportfindings.html .

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: AWS CloudWatch

Capabilities

Collect: Yes
Respond: No
Native Alerts Mapped: No
Runs on: DP
Interval: Configurable

Collected Data

Content Type	Index	Locating Records
N/A	Syslog Traffic (VPC flow)	msg_class: aws_cloudwatch_log `aws_cloudwatch_waf` (for WAF logs) `aws_guardduty` (for GuardDuty logs) `aws_cloudwatch_vpcflow` (for VPC Flow logs. Select the VPC Flow Logs checkmark also.) msg_origin.source: aws_cloudwatch aws_guardduty msg_origin.vendor: aws msg_origin.category: paas `waf` (for WAF logs)

Content Type

Index

Locating Records

N/A

Syslog

Traffic (VPC flow)

msg_class:

aws_cloudwatch_log

aws_cloudwatch_waf (for WAF logs)

aws_guardduty (for GuardDuty logs)

aws_cloudwatch_vpcflow (for VPC Flow logs. Select the VPC Flow Logs checkmark also.)

msg_origin.source:

aws_cloudwatch

aws_guardduty

msg_origin.vendor:

aws

msg_origin.category:

paas

waf (for WAF logs)

Domain

https://logs.<Region>.amazonaws.com/

where <Region> is a variable from the configuration of this connector

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

For Access Key / Secret Key authentication: Access Key and Secret Key, plus Region, and Log Group(s)
For IAM Role authentication: Source Account Access Key, Source Account Secret Key, and IAM Role ARN, plus Region, and Log Group(s)

Adding an AWS CloudWatch Connector

To add an AWS CloudWatch connector:

Add an AWS user
Create an access key
Identify CloudWatch log groups
(Optional) Create an IAM role in same AWS account
(Optional) Create an IAM role across AWS accounts
Add the connector in Stellar Cyber
Test the connector
Verify ingestion

Adding an AWS User for Stellar Cyber

Use our example as a guideline, as you might be using a different software version.

To add a user with the appropriate permissions:

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
Choose Policies and then choose Create Policy.
In the Create policy pane, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

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

Copy

CloudWatch policy

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "logs:DescribeLogGroups",
                "logs:DescribeLogStreams",
                "logs:GetLogEvents",
                "logs:FilterLogEvents"
            ],
            "Resource": "*",
            "Condition": {
                "ForAnyValue:StringEquals": {
                    "aws:RequestedRegion": "us-west-2"
                }
            }
        }
    ]
}

Choose Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.

The policy can now be attached to a user.
From the IAM navigation pane, choose Users and then choose Create user.
On the Specify user details page for User details, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
On the Set permissions page, choose Attach policies directly. Then search for the policy you created above.
Select the checkbox to the left of the policy name, then choose Next.
On the Review and create page, verify the information and then choose Create user.

Creating an Access Key

The procedures in this section are for Access Key / Secret Key authentication in Stellar Cyber.

Log in to the IAM Console with your AWS account ID, your IAM user name, and password. You must have the permissions required to create access keys for a user.
Choose Users, then click the user name, and click Security credentials.
In the Access keys section, choose Create access key. Access keys have two parts: an access key ID and a secret access key. Click Create access key.
On the Access key best practices & alternatives page, choose Other and then choose Next.
(Optional) On the Set description tag page, enter a description.
Click Create access key.
On the Retrieve access keys page, choose Show to reveal the value of the user's secret access key. Save the access key ID and secret access key in a secure location. You will need them when configuring the connector in Stellar Cyber.
Click Done.

Identifying AWS CloudWatch Log Groups

For this connector, you will specify one or more log groups to ingest. Use this procedure to locate the group names (this procedure assumes that you have already configured your CloudWatch instances and log groups).

Log in to your AWS CloudWatch Console at https://console.aws.amazon.com/cloudwatch/ .
Navigate to the Logs section of the left hand navigation pane.
Select Log Groups.
Make note of the groups you want to ingest to Stellar Cyber.

(Optional) Creating an IAM Role in Same AWS Account

The procedures in this section are for an IAM role that is created in the same AWS account. The procedures are for IAM Role authentication in Stellar Cyber.

Create an IAM User Without Permissions and Create IAM Policy

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page for User details, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
On the Set permissions page, choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

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

Copy

CloudWatch policy - IAM Role - same AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "logs:DescribeLogGroups",
                "logs:DescribeLogStreams",
                "logs:GetLogEvents",
                "logs:FilterLogEvents"
            ],
            "Resource": "arn:aws:logs:us-west-2:001xxxxxx433:log-group:vpc-flow:*"
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.
Note that in the example policy above, vpc-flow is the AWS CloudWatch log group name. To find your log group name, see Identifying AWS CloudWatch Log Groups.

Create an IAM Role with Trusted Entities

From the IAM navigation pane, choose Roles and then click Create Role.
Choose Custom trust policy.

Using the example below as a guide, edit the custom trust policy document.

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

Copy

Trusted entities - same AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::001xxxxxx433:user/jzhang-connector"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

Click Next.
On the Add permissions page, select the permissions policy created earlier.
Click Next.
On the Name, review, and create page, enter a Role name.
Review the trusted entities and permissions, then click Create Role.
On the Roles page, use the Search box to find your role name.
Click your role name.
Copy your ARN, which you will need when configuring the connector in Stellar Cyber.

(Optional) Creating an IAM Role Across AWS Accounts

The procedures in this section are for an IAM role that is created across AWS accounts. The procedures are for IAM Role authentication in Stellar Cyber.

Create an IAM User for Source AWS Account and Create IAM Policy

Create this IAM user if you have a source AWS account like an MSSP AWS account.

When configuring the connector in Stellar Cyber, you will need the source AWS account (MSSP account) and the access key and secret key.

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
Choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

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

Copy

CloudWatch policy - IAM Role - across AWS accounts

1
2
3
4
5
6
7
8
9
10
11
12
13
14
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sts:AssumeRole"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

(Optional) To only allow the particular destination AWS account IAM role, using the example below as a guide, edit the JSON policy document.

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

Copy

CloudWatch policy - IAM Role - allow destination AWS account

1
2
3
4
5
6
7
8
9
10
11
12
13
14
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sts:AssumeRole"
            ],
            "Resource": [
                "arn:aws:iam::578xxxxxx273:role/Stellar-cloudwatch-role"
            ]
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.
To find your log group name, see Identifying AWS CloudWatch Log Groups.

(Optional) Create an IAM User for Destination AWS Account and Create IAM Policy

Create this IAM user if you have a destination AWS account like an MSSP's tenant AWS account.

When configuring the connector in Stellar Cyber, you will need the destination AWS account (MSSP's tenant account), the IAM role ARN, as well as the CloudWatch log group name.

Log in to your AWS Management Console at https://aws.amazon.com/console. View the services in the Console Home or choose View all services.
Choose IAM. The IAM Dashboard appears.
From the IAM navigation pane, choose Users and then click Create user.
On the Specify user details page, enter a User name for the new user.
Choose Provide user access to the – AWS Management Console optional to produce login credentials for the new user, such as a password.
Choose how you want to create the Console password and then choose Next.
Choose Attach policies directly and click Create policy.
On the Specify permissions page, choose the JSON tab.

Using the example below as a guide, edit the JSON policy document.

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

Copy

CloudWatch policy - Stellar-cloudwatch-policy

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "logs:DescribeLogGroups",
                "logs:DescribeLogStreams",
                "logs:GetLogEvents",
                "logs:FilterLogEvents"
            ],
            "Resource": "arn:aws:logs:us-west-2:578xxxxxx273:log-group:System:*:*"
        }
    ]
}

Click Next.
Give your policy a name to associate it with Stellar Cyber, then choose Create policy.
To find your log group name, see Identifying AWS CloudWatch Log Groups.

Create an IAM Role with Trusted Entities

From the IAM navigation pane, choose Roles and then click Create Role.
Choose Custom trust policy.

Using the example below as a guide, edit the custom trust policy document.

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

Copy

Trusted entities - across AWS accounts

1
2
3
4
5
6
7
8
9
10
11
12
13
14

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Statement1",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::001xxxxxx433:user/jzhang-connector"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

Click Next.
On the Add permissions page, select the permissions policy created earlier.
Click Next.
On the Name, review, and create page, enter a Role name.
Review the trusted entities and permissions, then click Create Role.
On the Roles page, use the Search box to find your role name.
Click your role name.
Copy your ARN, which you will need when configuring the connector in Stellar Cyber.

Adding the Connector in Stellar Cyber

With the credential and log information available, you can now add the AWS CloudWatch connector in Stellar Cyber:

Log in to Stellar Cyber.
Click System | Connectors (under Integrations). 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 PaaS from the Category drop-down.
Choose AWS CloudWatch from the Type drop-down.
For this connector, the supported Function is Collect, which is enabled already.
Enter a Name.

This field does not accept multibyte characters.
Choose a Tenant Name. The Interflow records created by this connector include this tenant name.
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.
(Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.
Click Next. The Configuration tab appears.

The asterisk (*) indicates a required field.
Choose the Auth Method to use Access Key / Secret Key or IAM Role.

For Access Key / Secret Key authentication:
1. Enter the Access Key you noted above in Creating an Access Key.
2. Enter the Secret Key you noted above.
For IAM Role authentication:

The asterisk (*) indicates a required field.
1. Enter the Source Account Access Key.
2. Enter the Source Account Secret Key.
  The IAM role can be across multiple AWS accounts:
  - For the source account, provide the trusted IAM user's access key and secret key. Refer to Creating an Access Key.
  - For the destination account, provide the AWS IAM role, in which this role is trusting the source account IAM user. Refer to (Optional) Creating an IAM Role Across AWS Accounts.
3. Enter the IAM Role ARN you noted above.
Choose a Region from the available regions in the drop-down.
Enter the Log Group(s) as named in your AWS CloudWatch console. To enter multiple log group names, press Enter after each name.

If you want to enter Log Stream(s) in the optional step below, you can only enter one Log Group in this step.
(Optional) Enter the Log Stream(s). Provide a list of log stream(s) that correspond to the provided log group. To enter multiple log stream names, press Enter after each name. If log streams are not specifically listed, every log stream within the provided log group is automatically searched.
(Optional) Click the checkmark for VPC Flow Logs if you are collecting VPC flow logs.
Choose the Interval (min). This is how often the logs are collected.
Click Next. The final confirmation tab appears.
Click Submit.

To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.
If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.
- This prompt only occurs during the initial create connector process when Collect is enabled.
- Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.
- The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.
The Connector Overview appears.

The new connector is immediately active and starts collecting logs.

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

Click System | Connectors (under Integrations). The Connector Overview appears.
Locate the connector by name 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.

Display sample messages...

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.

Verifying Ingestion

To verify ingestion:

Click Investigate | Threat Hunting. The Interflow Search tab appears.
Change the Indices for the type of content you collected:
- Change the Indices to Syslog.
- For VPC flow logs only, change the Indices to Traffic.
The table immediately updates to show ingested Interflow records.