Collect AWS Security Hub logs

This document explains how to ingest AWS Security Hub logs to Google Security Operations. AWS Security Hub provides a comprehensive view of security alerts and findings across AWS accounts. By sending these findings to Google SecOps, you can use Google SecOps capabilities to enhance monitoring and threat detection.

Before you begin

• Ensure that you have a Google SecOps instance.
• Ensure that you have privileged access to AWS.

Configure AWS IAM and S3

1. Create an Amazon S3 bucket following this user guide: Creating a bucket.
2. Save the bucket Name and Region for later use.
3. Create a user following this user guide: Creating an IAM user.
4. Select the created User.
5. Select the Security credentials tab.
6. Click Create Access Key in the Access Keys section.
7. Select Third-party service as the Use case.
8. Click Next.
9. Optional: add a description tag.
10. Click Create access key.
11. Click Download CSV file to save the Access Key and Secret Access Key for later use.
12. Click Done.
13. Select the Permissions tab.
14. Click Add permissions in the Permissions policies section.
15. Select Add permissions.
16. Select Attach policies directly.
17. Search for and select the AmazonS3FullAccess policy.
18. Click Next.
19. Click Add permissions.

Create a Lambda function

1. Sign in to the AWS Management Console.
2. Go to Lambda.
3. Click Create Function and select Author from Scratch.
4. Provide a name for your function; for example, SecurityHubToS3.
5. Choose Python 3.x for the runtime.

6. Enter the Lambda code that takes the findings from EventBridge and writes them to your S3 bucket:

   import json
   import boto3
   from datetime import datetime
   
   # Initialize the S3 client
   s3_client = boto3.client('s3')
   
   # S3 bucket where findings will be stored
   bucket_name = 'aws-security-hub-findings-stream'
   
   def lambda_handler(event, context):
      # Extract Security Hub findings from the event
      findings = event['detail']['findings']
   
      # Generate a timestamp for the file name to avoid overwriting
      timestamp = datetime.now().strftime('%Y-%m-%dT%H-%M-%S')
   
      # Generate the S3 object key (file name) based on the timestamp
      object_key = f"security_hub_findings_{timestamp}.json"
   
      # Convert findings to JSON format
      findings_json = json.dumps(findings, indent=4)
   
      # Upload the findings to S3
      try:
         response = s3_client.put_object(
               Bucket=bucket_name,
               Key=object_key,
               Body=findings_json,
               ContentType='application/json'
         )
         print(f"Successfully uploaded findings to S3: {response}")
      except Exception as e:
         print(f"Error uploading findings to S3: {e}")
         raise e
   
      return {
         'statusCode': 200,
         'body': json.dumps('Successfully processed findings')
      }
   

7. Set permissions for Lambda by adding an IAM role to the Lambda function with the following policy:

   {
      "Version": "2012-10-17",
      "Statement": [
         {
               "Effect": "Allow",
               "Action": [
                  "s3:PutObject"
               ],
               "Resource": "arn:aws:s3:::aws-security-hub-findings-stream/*"
         }
      ]
   }
   

Configure AWS Security Hub to forward findings with EventBridge

1. Sign in to the AWS Management Console.
2. In the search bar, type and select Security Hub from the services list.
3. Click Settings.
4. Under the Integrations section, find EventBridge and click Enable.
5. In the search bar, type and select EventBridge from the services list.
6. In the EventBridge console, click Rules > Create rule.
7. Provide the following Rule configuration:
   1. Rule Name: provide a descriptive name for the rule; for example, SendSecurityHubFindingsToS3.
   2. Event Source: select AWS services.
   3. Service Name: choose Security Hub.
   4. Event Type: select Security Hub Findings.
   5. Set the Target: choose Lambda function.
   6. Select the Lambda function you just created (SecurityHubToS3).
8. Click Create.

Configure a feed in Google SecOps to ingest AWS Security Hub logs

1. Go to SIEM Settings > Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed; for example, AWS Security Hub Logs.
4. Select Amazon S3 as the Source type.
5. Select AWS Security Hub as the Log type.
6. Click Next.

7. Specify values for the following input parameters:

   • Region: the region where the Amazon S3 bucket is located.
   • S3 URI: the bucket URI.
     • s3://your-log-bucket-name/
       • Replace your-log-bucket-name with the actual name of the bucket.
   • URI is a: select Directory or Directory which includes subdirectories.

   • Source deletion options: select the deletion option according to your preference.

   • Access Key ID: the User access key with access to the S3 bucket.

   • Secret Access Key: the User secret key with access to the S3 bucket.

   • Asset namespace: the asset namespace.

   • Ingestion labels: the label to be applied to the events from this feed.

8. Click Next.

9. Review your new feed configuration in the Finalize screen, and then click Submit.

UDM Mapping Table

Changes

2025-02-18

Enhancement:

• Added support for a new array of JSON log format.

2025-01-20

Enhancement:

• Added support for new log format.

2025-01-16

Enhancement:

• Added support for a new JSON log format.

2023-06-20

Enhancement:

• Modified metadata.event_type from GENERIC_EVENT to USER_RESOURCE_ACCESS.

2023-03-24

Enhancement:

• When detail.findings.0.Resources.0.Type == AwsEcsTaskDefinition -
• Mapped target.resource.resource_type to TASK.
• Mapped event_type to USER_RESOURCE_ACCESS.
• Mapped detail.findings.0.ProductFields.Resources:0/Id to principal.asset_id.
• Parsed all other failing logs as GENERIC_EVENT as STATUS_UPDATE was not a good parsing option for them.

2022-08-22

Enhancement:

• Updated vendor_name from AWS SECURITY HUB to AMAZON.
• Updated product_name from AWS SECURITY HUB to AWS Security Hub.
• Parsed The new JSON format logs containing configurationItem or configurationItems.
• Handled the logs which were ingested as an import file by separating them out using for loop and parse each as individual events.

2022-07-01

• Newly Created Parser.

Need more help? Get answers from Community members and Google SecOps professionals.