Amazon Security Lake

Logging in and navigating

1. Log into your AWS console and navigate to Security Lake.

2. Navigate to Subscribers, and click Create subscriber.

Creating a subscriber

1. Enter a descriptive name for your subscriber. For example, Wazuh.

2. Enter the AWS account ID for the account you are currently logged into.

3. Enter a unique value in External ID. For example, WAZUH-EXTERNAL-ID-VALUE.

4. Choose to either collect all log and event sources, or only specific log and event sources.

5. Select S3 as your data access method.

6. Under S3 notification type select SQS queue.

7. Click the Create button to get to the Subscribers pages.

Reviewing the subscriber

1. Navigate to My subscribers section, and click on your newly created subscriber to get to the Subscriber details page.

2. Check that AWS created the subscriber with the correct parameters.

3. Save the SQS queue name. You need the name of the Subscription endpoint for later on when verifying the information in the SQS queue.

Verifying information in SQS Queue

Follow these steps in your Amazon deployment to verify the information for the SQS Queue that Security Lake creates.

1. In your AWS console, navigate to the Amazon Simple Queue Service.

2. In the Queues section, navigate to the queue that Security Lake created. Click on its name.

3. In the information page for the queue, click on the Monitoring tab. Verify that events are flowing in by looking at the Approximate Number Of Messages Visible graph and confirming the number is increasing.

Verifying events are flowing into S3 bucket

Follow these steps in your Amazon deployment to verify that parquet files are flowing into your configured S3 buckets.

1. In your AWS console, navigate to the Amazon S3 service.

2. Navigate to the Buckets section, and click on the S3 bucket name that Security Lake created for each applicable region. These bucket names start with the prefix aws-security-data-lake.

3. In each applicable bucket, navigate to the Objects tab. Click through the directories to verify that Security Lake has available events flowing into the S3 bucket. Check that new files with the .gz.parquet extension appear.

   • If you enabled Security Lake on more than one AWS account, check if you see each applicable account number listed. Check that parquet files exist inside each account.

4. In each applicable S3 bucket, navigate to the Properties tab and verify in the Event notifications section that the data destination is the Security Lake SQS queue.

Configuring the role

Follow these steps to modify the Security Lake subscriber role. You have to associate an existing user with the role.

1. In your AWS console, navigate to the Amazon IAM service.

2. In your Amazon IAM service, navigate to the Roles page.

3. In the Roles page, select the Role name of the subscription role notification that was created as part of the Security Lake subscriber provisioning process.

4. In the Summary page, navigate to the Trust relationships tab to modify the Trusted entity policy.

5. Modify the Trusted entity policy with the following updates:

   • In the stanza containing the ARN, attach the username from your target user account to the end of the ARN. This step connects a user to the role. It lets you configure the Security Lake service with the secret access key. See the following Trusted entity example:

   {
       "Version": "2012-10-17",
       "Statement": [
           {
               "Sid": "1",
               "Effect": "Allow",
               "Principal": {
                   "AWS": "arn:aws:iam::<ACCOUNT_ID>:user/<USERNAME>"
               },
               "Action": "sts:AssumeRole",
               "Condition": {
                       "StringEquals": {
                           "sts:ExternalId": [
                               "<WAZUH-EXTERNAL-ID-VALUE>"
                           ]
                       }
               }
           }
       ]
   }
   

   Note

   <ACCOUNT_ID>, <USERNAME> and <WAZUH-EXTERNAL-ID-VALUE> are placeholders. Replace them with the appropriate values.

Granting user permission to switch roles

Follow these steps to configure the user permissions:

1. In your Amazon IAM service, navigate to the Users page.

2. In the Users page, select the Username of the user you have connected to the role (<USERNAME>).

3. Replace <ACCOUNT_ID> and <RESOURCE_ROLE> with the appropriate values and add the following permission to switch to the new role:

   Note that <RESOURCE_ROLE> is the name of the subscription role that was created as part of the Security Lake subscriber provisioning process.

   {
       "Version": "2012-10-17",
       "Statement": [
           {
           "Sid": "VisualEditor1",
           "Effect": "Allow",
           "Action": "sts:AssumeRole",
           "Resource": "arn:aws:iam::<ACCOUNT_ID>:role/<RESOURCE_ROLE>"
           }
       ]
   }