Secrets Manager secret should use a customer-managed KMS key
Medium
AWS
General
aws-secretsmanager-secret-secrets-manager-secret-c
Applies to
AWS::SecretsManager::Secret
What CGPulse checks
A resource passes this rule when kmsKeyId must be set true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure a customer-managed KMS key for enhanced audit and encryption control. In AWS Console: Secrets Manager > select secret > edit encryption key. See: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security-encryption.html
Terraform
resource "aws_secretsmanager_secret" "{name}" {
kms_key_id = aws_kms_key.{name}.arn
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled