Collect AWS Key Management Service logs

This document explains how to ingest AWS Key Management Service (KMS) logs to Google Security Operations. AWS KMS is a fully managed service that lets you to create and control encryption keys used to encrypt your data. This integration helps in monitoring and auditing the usage of encryption keys.

Before you begin

Ensure you have the following prerequisites:

• Google SecOps instance
• Privileged access to AWS

Configure Amazon S3 and IAM

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.

How to configure CloudTrail for AWS KMS

1. Sign in to the AWS Management Console.
2. In the search bar, type and select CloudTrail from the services list.
3. Click Create trail.
4. Provide a Trail name (for example, KMS-Activity-Trail).
5. Select the Enable for all accounts in my organization checkbox.
6. Type the S3 bucket URI created earlier (the format should be: s3://your-log-bucket-name/), or create a new S3 bucket.
7. If SSE-KMS enabled, provide a name for AWS KMS alias, or choose an existing AWS KMS Key.
8. You can leave the other settings as default.
9. Click Next.
10. Select Management events and Data events under Event Types.
11. Click Next.
12. Review the settings in Review and create.
13. Click Create trail.
14. Optional: if you created a new bucket, continue with the following process:
    1. Go to S3.
    2. Identify and select the newly created log bucket.
    3. Select the folder AWSLogs.
    4. Click Copy S3 URI and save it.

Set up feeds

There are two different entry points to set up feeds in the Google SecOps platform:

• SIEM Settings > Feeds
• Content Hub > Content Packs

Set up feeds from SIEM Settings > Feeds

To configure multiple feeds for different log types within this product family, see Configure feeds by product.

To configure a single feed, follow these steps:

1. Go to SIEM Settings > Feeds.
2. Click Add New Feed.
3. On the next page, click Configure a single feed.
4. In the Feed name field, enter a name for the feed (for example, AWS KMS Logs).
5. Select Amazon S3 as the Source type.
6. Select AWS KMS as the Log type.
7. Click Next.

8. 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 your S3 bucket.
   • URI is a: Select either Directory or Directory which includes subdirectories, depending on your bucket structure.

   • Source deletion options: Select the deletion option according to your ingestion preferences.

   • Access Key ID: The user's access key with permissions to read from the S3 bucket.

   • Secret Access Key: The user's secret key with permissions to read from the S3 bucket.

   • Asset namespace: The asset namespace.

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

9. Click Next.

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

Set up feeds from the Content Hub

Specify values for the following fields:

• 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 your S3 bucket.
• URI is a: Select either Directory or Directory which includes subdirectories, depending on your bucket structure.
• Source deletion options: Select the deletion option according to your ingestion preferences.

• Access Key ID: The user's access key with permissions to read from the S3 bucket.

• Secret Access Key: The user's secret key with permissions to read from the S3 bucket.

Advanced Options

• Feed Name: A prepopulated value that identifies the feed.
• Source Type: Method used to collect logs into Google SecOps.
• Asset Namespace: Namespace associated with the feed.
• Ingestion Labels: Labels applied to all events from this feed.

UDM Mapping Table

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