Enforce Customer Managed KMS Keys and Key Rotation for Audit Logs
Specification & Description
Enforce the use of Customer Managed Keys (CMKs) with automated key rotation enabled and strict cross-account key policies for encrypting centralized CloudTrail and audit log archives.
Technical Specifications
Default AWS-managed keys (aws/s3 or aws/cloudtrail) are insufficient for enterprise Landing Zone
audit logging because their key policies cannot be modified to restrict access, cannot be shared across
accounts with granular IAM conditions, and do not provide detailed KMS access logs for forensic investigation.
1. Customer Managed Key (CMK) Governance
- All audit trails and centralized log archive buckets must use dedicated AWS KMS Customer Managed Keys.
- CMKs provide granular control over key administration versus key usage permissions.
- Decryption capabilities can be isolated to dedicated security and forensic roles, preventing unauthorized member account admins from decrypting sensitive organizational audit trails.
2. Automated Key Rotation
- Regular automated key rotation must be enabled on the KMS key.
- When rotation occurs, KMS automatically creates a new backing key while retaining previous versions to seamlessly decrypt historical logs without manual key migration.
3. Multi-Account KMS Key Policy Guardrails
- Key policies must explicitly allow the
cloudtrail.amazonaws.comservice principal to generate data keys across the organization usingaws:SourceOrgIDconditions. - Key policies must prevent
kms:DisableKey,kms:ScheduleKeyDeletion, or policy modifications by unauthorized principals.
Security Rationale
Using KMS Customer Managed Keys with automated rotation ensures cryptographic separation of duties and maintains log confidentiality. Even if an attacker compromises an S3 bucket policy or acquires raw S3 object permissions, they cannot decrypt the forensic logs without explicit KMS key permissions. Automated key rotation limits the cryptanalytic blast radius of any individual key version.
Business & Security Impact
Using default AWS-managed keys prevents multi-account log aggregation and leaves decryption uncontrolled. Failure to rotate keys increases cryptographic exposure risks over long retention periods.
Related Controls & Guardrails (3)
Compliance Framework Mappings (6)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
CIS AWS Foundations Benchmark v3.0CIS AWS | 3.73.8 | 2 |
NIST 800-53 Rev 5NIST 800-53 | SC-28SC-12AU-9 | 3 |
ISO 27001:2022ISO 27001 | A.8.24 | 1 |
SOC 2SOC 2 | CC6.1 | 1 |
PCI DSS v4.0PCI DSS | 10.5.13.5.1 | 2 |
HIPAA Security RuleHIPAA | 164.312(a)(2)(iv) | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Verifies that the KMS key configured for CloudTrail and log archive storage is a Customer Managed Key (not an AWS managed key) and that key rotation is currently enabled.
Preventative Enforcement Policies
Remediation Guide & Automation
Create a Customer Managed Key (CMK) in the Log Archive account with automated rotation enabled and a multi-account key policy, then update CloudTrail and S3 bucket configurations to utilize the CMK.
Step-by-Step Instructions
- Provision a KMS Customer Managed Key in the Log Archive account with `enable_key_rotation = true`.
- Configure the KMS key policy to allow `cloudtrail.amazonaws.com` service encryption constrained by `aws:SourceOrgID`.
- Restrict `kms:Decrypt` actions to authorized security and audit roles only.
- Update CloudTrail trail configuration (`--kms-key-id`) to use the new CMK ARN.
- Verify key rotation status using AWS CLI or Boto3.