Collect AWS VPN logs

Supported in:

Google SecOps SIEM

Note: This feature is covered by Pre-GA Offerings Terms of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the Google Security Operations Technical Support Service guidelines and the Google Security Operations Service Specific Terms.

This document explains how to ingest AWS VPN logs to Google Security Operations. AWS VPN provides a secure connection between your on-premises network and your Amazon Virtual Private Cloud (VPC). By forwarding VPN logs to Google SecOps, you can analyze VPN connection activities, detect potential security risks, and monitor traffic patterns.

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.

Configure CloudTrail for AWS VPN Logging

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, VPN-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 is 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 to All and Data events to Networking and VPN services 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 during the CloudTrail configuration, continue with the following process:

    1. Go to S3.
    2. Identify and select the newly created log bucket.
    3. Select the AWSLogs folder.
    4. Click Copy S3 URI and save it.

Configure AWS Client VPN logging

1. Go to the AWS Client VPN console.
2. Under Client VPN Endpoints, select the required endpoint.
3. In the Logging section, click enable logging and specify an Amazon CloudWatch Log group to which VPN connection logs will be sent.

Configure a feed in Google SecOps to ingest AWS VPN 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 VPN Logs.
4. Select Amazon S3 as the Source type.
5. Select AWS VPN 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.

     Note: If you select the Delete transferred files or Delete transferred files and empty directories option, make sure that you granted appropriate permissions to the service account.

   • 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

2024-09-19

Enhancement:

• Mapped connection-attempt-status to security_result.action.

2024-07-19

• Newly created parser.

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