AWS Configuration Guide for Cloud SIEM
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Overview
Cloud SIEM applies detection rules to all processed logs in Datadog to detect threats, like a targeted attack, a threat intel listed IP communicating with your systems, or an insecure configuration. The threats are surfaced as Security Signals in the Security Signals Explorer for triaging.
This guide walks you through the following steps so that you can start detecting threats with your AWS CloudTrail logs:
- Set up Datadog’s AWS integration
- Enable AWS CloudTrail logs
- Send AWS CloudTrail logs to Datadog
- Use Cloud SIEM to triage Security Signals
Go to Datadog’s AWS integration tile to install the integration.
Click Automatically Using CloudFormation. If there is already an AWS account set up, click Add Another Account first.
Select the AWS Region where the CloudFormation stack will be launched.
Select or create the Datadog API Key used to send data from your AWS account to Datadog.
Select Yes for Send Logs to Datadog. This sets up the Datadog Lambda Forwarder to be used later for sending AWS CloudTrail logs to Datadog.
Click Launch CloudFormation Template. This opens the AWS Console and loads the CloudFormation stack with the parameters filled in based on your selections in the prior Datadog form.
Note: The DatadogAppKey parameter enables the CloudFormation stack to make API calls to Datadog to add and edit the Datadog configuration for this AWS account. The key is automatically generated and tied to your Datadog account.
Check the required boxes from AWS and click Create stack.
After the CloudFormation stack is created, go back to the AWS integration tile in Datadog and click Ready!
See Getting Started with AWS for more information about Datadog’s AWS integration and CloudFormation template. See AWS manual setup instructions if you need to set up the AWS integration manually.
Enable AWS CloudTrail logging
Enable AWS CloudTrail logging so that logs are sent to a S3 bucket. If you already have this setup, skip to Send AWS CloudTrail logs to Datadog.
- Click Create trail on the CloudTrail dashboard.
- Enter in the name for your trail.
- Create a new S3 bucket or use an existing S3 bucket to store the CloudTrail logs.
- Create a new AWS KMS key or use an existing AWS KMS key. Click Next.
- Leave the event type with the default management read and write events, or choose additional event types you want to send to Datadog. Click Next.
- Review and click Create trail.
Send AWS CloudTrail logs to Datadog
Set up a trigger on your Datadog Forwarder Lambda function to send CloudTrail logs stored in the S3 bucket to Datadog for monitoring.
- Go to the Datadog Forwarder Lambda that was created during the AWS integration set up.
- Click Add trigger.
- Select S3 for the trigger.
- Select the S3 bucket you are using to collect AWS CloudTrail logs.
- For Event type, select All object create events.
- Click Add.
- See CloudTrail logs in Datadog’s Log Explorer.
See Log Explorer for more information on how to search and filter, group, and visualize your logs.
Use Cloud SIEM to triage Security Signals
Cloud SIEM applies out of the box detection rules to all processed logs, including the CloudTrail logs you have just set up. When a threat is detected with a Detection Rule, a Security Signal is generated and can be viewed in the Security Signals Explorer.
Since Cloud SIEM applies detection rules to all processed logs, see the in-app instructions on how to collect Kubernetes audit logs and logs from other sources for threat detection. You can also enable different AWS services to log to a S3 bucket and send them to Datadog for threat monitoring.
Further reading
Documentation, liens et articles supplémentaires utiles:
