AWS Security Hub

About the Device

AWS Security Hub provides you with a comprehensive view of your security state in AWS and helps you check your environment against security industry standards and best practices.

Security Hub collects security data from across AWS accounts, services, and supported third-party partner products and helps you analyze your security trends and identify the highest priority security issues.

AWS Security Hub reduces the effort of collecting and prioritizing security findings across accounts, from AWS services, and AWS partner tools. The service ingests data using a standard findings format called ASFF.

Device Information

Collection Method

Device Configuration

Prerequisite:

• AWS Config is enabled. Please refer below page to enable AWS Config: https://docs.aws.amazon.com/config/latest/developerguide/gs-console.html

• AWS Security Hub is enabled. Please refer below page to enable Security Hub: https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-enable.html

• Cloudwatch log group should be created. Please refer the following page to create a Cloudwatch loggroup. https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/Working-with-log-groups-and-streams.html

• Integrations with AWS services

We support two methods to ingest logs into Chronicle from AWS Security Hub. The Lambda+S3+SQS method is preferred, while the Data Firehose method is secondary.

Device Configuration

Method 1: Lambda+S3+SQS

Please follow below steps to forward security hub findings to Cloudwatch log group:

1. Navigate to Amazon EventBridge, Click Rules and click create rule.

2. Provide details like Name, Description, Rule type and click next.

3. In Build Event Pattern, select other.

4. For Event source, choose Event Pattern, select Security hub.

   1. Choose Custom pattern (JSON editor)

   2. Copy the following example pattern and paste it into the Event pattern text area. Be sure to replace the existing brackets.

{
  "source": ["aws.securityhub"],
  "detail-type": ["Security Hub Findings - Custom Action", "Security Hub Findings – Imported"]
}

5. On the target screen, select AWS Service as target type. Select target as CloudWatch log group.

   1. Select the Log Group.

6. On the review and create screen, review your configured event pattern, target and click Create rule.

If you have enabled security hub, findings will be forwarded to the provided CloudWatch log group.

 Once logs are available in the S3 bucket, please configure SQS, please follow below step:

1. Follow the guide provided above for log export from Cloudwatch log group to S3 bucket.

2. Create SQS and attach it with S3. Please refer: Configuring AWS Simple Queue Service (SQS) with S3 Storage

Method 2: Amazon Data Firehose

Please find more details on Firehose Configuration on the below page:

Amazon Data Firehose to Chronicle: C2C-Push

Important Links:

• For more details on how to get required credentials for integration parameters please refer: Get Credentials for AWS Storage

• Please refer below page to check required IAM user and KMS Key policies for S3, SQS and KMS:IAM User and KMS Key Policies Required for AWS

• Below are the URL details which we need to allow for connectivity (Please identify URLs by referring AWS document according to your services and regions):

  • IAM: For any logging source IAM URL should be allowed :https://docs.aws.amazon.com/general/latest/gr/iam-service.html

  • S3: For S3 or SQS logging source, S3 URL should be allowed: https://docs.aws.amazon.com/general/latest/gr/s3.html

  • SQS: For SQS logging source, SQS URL should be allowed:https://docs.aws.amazon.com/general/latest/gr/sqs-service.html

Integration parameters

SQS:

Integration via Amazon Data Firehose:

Configure Amazon Data Firehose on Google Chronicle instance and copy a Endpoint URL & Secret key.