OpenParable
Skip to content
← Back to skills

Cis AWS Foundations 4.5

DevOps & Security
cis-aws-foundations-4.5

Cis AWS Foundations 4.5 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure CloudTrail logs are encrypted at rest using KMS CMKs

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_Amazon_Web_Services_Foundations_Benchmark_v7.0.0/cis-aws-foundations-4.5/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-foundations-4-5, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Ensure CloudTrail logs are encrypted at rest using KMS CMKs

Description

AWS CloudTrail is a web service that records AWS API calls for an account and makes those logs available to users and resources in accordance with IAM policies. AWS Key Management Service (KMS) is a managed service that helps create and control the encryption keys used to encrypt account data, and uses Hardware Security Modules (HSMs) to protect the security of encryption keys. CloudTrail logs can be configured to leverage server side encryption (SSE) and KMS customer-created master keys (CMK) to further protect CloudTrail logs. It is recommended that CloudTrail be configured to use SSE-KMS.

Rationale

Configuring CloudTrail to use SSE-KMS provides additional confidentiality controls on log data, as a given user must have S3 read permission on the corresponding log bucket and must be granted decrypt permission by the CMK policy.

Impact

Customer-created keys incur an additional cost. See https://aws.amazon.com/kms/pricing/ for more information.

Audit Procedure

Using AWS Console

  1. Sign in to the AWS Management Console and open the CloudTrail console at https://console.aws.amazon.com/cloudtrail.
  2. In the left navigation pane, choose Trails.
  3. Select a trail.
  4. In the General details section, select Edit to edit the trail configuration.
  5. Ensure the box at Log file SSE-KMS encryption is checked and that a valid AWS KMS alias of a KMS key is entered in the respective text box.

Using AWS CLI

  1. Run the following command:
aws cloudtrail describe-trails
  1. For each trail listed, SSE-KMS is enabled if the trail has a KmsKeyId property defined.

Expected Result

All CloudTrail trails have a KmsKeyId property defined, indicating SSE-KMS encryption is enabled.

Remediation

Using AWS Console

  1. Sign in to the AWS Management Console and open the CloudTrail console at https://console.aws.amazon.com/cloudtrail.
  2. In the left navigation pane, choose Trails.
  3. Click on a trail.
  4. Under the S3 section, click the edit button (pencil icon).
  5. Click Advanced.
  6. Select an existing CMK from the KMS key Id drop-down menu.
    • Note: Ensure the CMK is located in the same region as the S3 bucket.
    • Note: You will need to apply a KMS key policy on the selected CMK in order for CloudTrail, as a service, to encrypt and decrypt log files using the CMK provided. View the AWS documentation for editing the selected CMK Key policy.
  7. Click Save.
  8. You will see a notification message stating that you need to have decryption permissions on the specified KMS key to decrypt log files.
  9. Click Yes.

Using AWS CLI

Run the following command to specify a KMS key ID to use with a trail:

aws cloudtrail update-trail --name <trail-name> --kms-key-id <cloudtrail-kms-key>

Run the following command to attach a key policy to a specified KMS key:

aws kms put-key-policy --key-id <cloudtrail-kms-key> --policy <cloudtrail-kms-key-policy>

Additional Information

Three statements that need to be added to the CMK policy:

  1. Enable CloudTrail to describe CMK properties:
{
  "Sid": "Allow CloudTrail access",
  "Effect": "Allow",
  "Principal": {
    "Service": "cloudtrail.amazonaws.com"
  },
  "Action": "kms:DescribeKey",
  "Resource": "*"
}
  1. Granting encrypt permissions:
{
  "Sid": "Allow CloudTrail to encrypt logs",
  "Effect": "Allow",
  "Principal": {
    "Service": "cloudtrail.amazonaws.com"
  },
  "Action": "kms:GenerateDataKey*",
  "Resource": "*",
  "Condition": {
    "StringLike": {
      "kms:EncryptionContext:aws:cloudtrail:arn": ["arn:aws:cloudtrail:*:aws-account-id:trail/*"]
    }
  }
}
  1. Granting decrypt permissions:
{
  "Sid": "Enable CloudTrail log decrypt permissions",
  "Effect": "Allow",
  "Principal": {
    "AWS": "arn:aws:iam::aws-account-id:user/username"
  },
  "Action": "kms:Decrypt",
  "Resource": "*",
  "Condition": {
    "Null": {
      "kms:EncryptionContext:aws:cloudtrail:arn": "false"
    }
  }
}

Default Value

By default, CloudTrail logs are not encrypted with a KMS CMK. Logs may be encrypted with SSE-S3, but this does not provide the same level of control or auditing as KMS CMKs.

References

  1. https://docs.aws.amazon.com/awscloudtrail/latest/userguide/encrypting-cloudtrail-log-files-with-aws-kms.html
  2. https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html
  3. CCE-78919-8
  4. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudtrail/update-trail.html
  5. https://awscli.amazonaws.com/v2/documentation/api/latest/reference/kms/put-key-policy.html

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v83.11 Encrypt Sensitive Data at Rest - Encrypt sensitive data at rest on servers, applications, and databases containing sensitive data.xx
v88.1 Establish and Maintain an Audit Log Management Process - Establish and maintain an audit log management process that defines the enterprise's logging requirements.xxx
v714.8 Encrypt Sensitive Information at Rest - Encrypt all sensitive information at rest using a tool that requires a secondary authentication mechanism not integrated into the operating system.x

MITRE ATT&CK Mappings

Techniques / Sub-techniquesTacticsMitigations
T1530TA0009M1041

Profile

Level 2 | Automated