Forward Logs to Amazon Security Lake

1. Enable communication between Strata Logging Service and your Amazon Security Lake.
2. Create an Identity and Access Management (IAM) role to permit write access to the Amazon Security Lake bucket location.
3. Sign In to the hub.
4. Select the Strata Logging Service instance that you want to configure for log forwarding.
   If you have multiple Strata Logging Service instances, click the Strata Logging Service tile and select an instance from the list of those available.
   If you are using Strata Cloud Manager to manage Strata Logging Service, click SettingsStrata Logging ServiceLog Forwarding forward logs to external server.
5. Select Log ForwardingAmazon Security Lake + to add a new Amazon Security Lake profile.
6. Configure a log forwarding profile to forward logs to Amazon Security Lake.
   1. Enter a descriptive Name for the profile.
   2. Enter the name of the Amazon Security Lake S3 configured bucket that is used as the storage container for your forwarded log data. You can get the name from the Amazon Console.
   3. Enter the geographic region (regional code) where the Amazon Security Lake is hosted.
   4. Select the external identification method to authenticate Amazon Security Lake.
      • IAM Role
        • IAM Role ARN - The Amazon Resource Names (ARN) of the role that has access to the Amazon S3 bucket. The IAM Role ARN need to be in the following format: arn:partition:service:region:account-id:resource-type:resource-id. For example, arn:aws:iam::account:role/role-name-with-path
        • External ID - The external identifier that you defined while linking the IAM role to your AWS account.
      • Access Key- If you have created a long-term access key to authenticate your AWS account, enter the key and secret password here.

        • To create an access key for the Amazon S3 bucket:
          1. Log in to AWS Management Console with your AWS account ID.
          2. On the Console Home page, select the IAM service.
          3. Select Users and then select Create user from the navigation pane.
          4. On the Specify user details page, enter the name for the new user.
          5. Do not select Provide user access to the – AWS Management Console and click Next.
          6. Set Permissions for the user. Here is a sample of the JSON code to set the permission boundaries in the policy:

             {
                 "Version": "2012-10-17",
                 "Statement": [ 
                     {
                        "Effect": "Allow",
                        "Action": "s3:PutObject",
                        "Resource": [
                            "arn:aws:s3:::DOC-EXAMPLE-BUCKET1",
                            "arn:aws:s3:::DOC-EXAMPLE-BUCKET1/*"
                           ]
                       }
                    ]
             }
             

          7. Review the selection and create the user.
          8. In the Summary page, select Security credentials > Create Access Key.
          9. Select the Third-party service option as the reason for enabling the access key and confirm the recommendation to create the access key.
          10. Retrieve the access key and use it while configuring the log forwarding.
7. Test Connection to ensure that the Strata Logging Service can communicate with the receiver.
   This sends an empty log to the sls_test_events folder in the configured destination to verify that transmission is possible.

   If the test fails, you won't be able to proceed.
8. Click Next.
9. Specify the Payload Format as PARQUET - the log format in which the Strata Logging Service forwards logs.
10. (Optional) To receive a STATUS NOTIFICATION when Strata Logging Service is unable to connect to the Amazon Security Lake, enter the email address at which you’d like to receive the notification.
    You will continue to receive these notifications at least once every 60 minutes until connectivity is restored. If the connectivity issue is addressed within 72 hours, no logs will be lost. However, any log older than 72 hours following the service disconnection could be lost.
11. Add the log type as Endpoint > Events and optionally write a query to create filter to forward only the logs that are most critical to you. Save your changes
    If you want to forward all logs of the type you selected, do not enter a query.

    You can forward only the following events endpoint log fields to Amazon Security Lake. Refer to Log Reference guide for information on the log fields

    • Event Log Fields
      • policy.action
      • user.id
      • user.name
      • user.email
      • user.tenant_id
      • device.device_uuid
      • device.hostname
      • device.ip_address
      • device.os.type
      • network.http.method
      • network.http.url
      • network.http.classifications
      • network.http.url
      • network.http.status
      • id
      • batch_id
      • device.browser_type
      • device.browser_version
12. Save your changes.
13. Verify that the Status of your forwarding profile is Running (
    ).
14. Verify if the logs are forwarded to the destination location. This is a sample path: /Amazon S3 bucket location > folder name > logsource.logtype > year > month > date
15. (Optional) You can use the running Amazon Security Lake forwarding profile to forward past logs spanning up to 3 days.