CloudTrail logs are not encrypted with customer managed key Affecting CloudTrail service in AWS
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CC-00004
- creditSnyk Research Team
Description
By default, the log files delivered by CloudTrail to your bucket are encrypted with Amazon S3-managed encryption keys (SSE-S3). To get control over key rotation and obtain auditing visibility into key usage, use SSE-KMS to encrypt log files with customer managed KMS keys.
How to fix?
Set the aws_cloudtrail kms_key_id field to the KMS key ARN to use to encrypt the logs delivered by CloudTrail.
Example Configuration
resource "aws_cloudtrail" "example" {
kms_key_id = "arn:aws:kms:example-key-id"
# other required fields here
}
Set the AWS::CloudTrail::Trail KMSKeyId field to the KMS key ARN to use to encrypt the logs delivered by CloudTrail.
Example Configuration
JSON example configuration:
{
"Type" : "AWS::CloudTrail::Trail",
"Properties" : {
"IsLogging" : true,
"KMSKeyId" : "alias/MyAliasName",
"S3BucketName" : "yourbucketname"
}
# other required fields here
}
YAML example configuration:
Type: AWS::CloudTrail::Trail
Properties:
IsLogging: true
KMSKeyId: alias/MyAliasName
S3BucketName: yourbucketname
# other required fields here