Enforce Encryption at Rest Is Enabled for AWS Log Groups

Ensuring that CloudWatch log groups are encrypted at rest is crucial for enhancing security. This measure helps protect log data by encrypting it, thereby reducing the risk of unauthorized access and ensuring compliance with security best practices and regulatory requirements.

This policy pack can help you configure the following settings for CloudWatch log groups:

• Set Customer Managed Key to be used for encryption
• Enable Encryption at Rest for log groups

Documentation

• Review policy settings →

Getting Started

Requirements

• Terraform
• Guardrails mods:
  • @turbot/aws-logs

Credentials

To create a policy pack through Terraform:

• Ensure you have Turbot/Admin permissions (or higher) in Guardrails
• Create access keys in Guardrails

And then set your credentials:

export TURBOT_WORKSPACE=myworkspace.acme.com
export TURBOT_ACCESS_KEY=acce6ac5-access-key-here
export TURBOT_SECRET_KEY=a8af61ec-secret-key-here

Please see Turbot Guardrails Provider authentication for additional authentication methods.

Usage

Install Policy Pack

Note

By default, installed policy packs are not attached to any resources.

Policy packs must be attached to resources in order for their policy settings to take effect.

Clone:

git clone https://github.com/turbot/guardrails-samples.git
cd guardrails-samples/policy_packs/aws/logs/enforce_encryption_at_rest_is_enabled_for_log_groups

Run the Terraform to create the policy pack in your workspace:

terraform init
terraform plan

Then apply the changes:

terraform apply

Apply Policy Pack

Log into your Guardrails workspace and attach the policy pack to a resource.

If this policy pack is attached to a Guardrails folder, its policies will be applied to all accounts and resources in that folder. The policy pack can also be attached to multiple resources.

For more information, please see Policy Packs.

Enable Enforcement

Tip

You can also update the policy settings in this policy pack directly in the Guardrails console.

Please note your Terraform state file will then become out of sync and the policy settings should then only be managed in the console.

By default, the policies are set to Check in the pack's policy settings. To enable automated enforcements, you can switch these policies settings by adding a comment to the Check setting and removing the comment from one of the listed enforcement options:

resource "turbot_policy_setting" "aws_logs_log_group_encryption_at_rest" {
  resource = turbot_policy_pack.main.id
  type     = "tmod:@turbot/aws-logs#/policy/types/logGroupEncryptionAtRest"
  # value    = "Check: AWS SSE or higher"
  # value    = "Check: Customer managed key"
  # value    = "Check: Encryption at Rest > Customer Managed Key"
  # value    = "Enforce: AWS SSE or higher"
  # value    = "Enforce: Customer managed key"
  value    = "Enforce: Encryption at Rest > Customer Managed Key"
}

Then re-apply the changes:

terraform plan
terraform apply