CloudTrail trail logs should be encrypted with KMS CMK¶

To help protect sensitive data at rest, ensure encryption is enabled for your AWS CloudWatch Log Groups.

How to fix¶

Attribute kms_key_id of aws_cloudtrail must be non-empty.

Implementation options¶

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources¶

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_cloudtrail.

resource "aws_cloudtrail" "this" {
  advanced_event_selector {
    field_selector {
      equals = ["Data"]
      field  = "eventCategory"
    }
    field_selector {
      equals = ["AWS::S3::Object"]
      field  = "resources.type"
    }

    name = "Log all S3 data events"
  }

  name           = "pofix-example-trail"
  s3_bucket_name = "example-bucket-abc123"

  kms_key_id = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
}

Which option should I choose?

Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings¶

Use these identifiers to cross-reference this control across tools, reports, and evidence.

Compliance.tf (CTF) Control: cloudtrail_trail_logs_encrypted_with_kms_cmk
AWS Config Managed Rule: CLOUD_TRAIL_ENCRYPTION_ENABLED
Checkov Check: CKV_AWS_35
Powerpipe Controls: aws_compliance.control.cis_v500_3_5, aws_compliance.control.cis_v600_4_5, aws_compliance.control.cloudtrail_trail_logs_encrypted_with_kms_cmk