Keyspaces table should use customer-managed KMS encryption
Medium
AWS
General
aws-keyspaces-table-encryption
Applies to
AWS::Keyspaces::Table
What CGPulse checks
A resource passes this rule when encryptionType must equal CUSTOMER_MANAGED_KMS. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure customer-managed KMS encryption for granular key control and audit trail. In AWS Console: Keyspaces > Tables > configure KMS encryption key. See: https://docs.aws.amazon.com/keyspaces/latest/devguide/EncryptionAtRest.html
Terraform
resource "aws_keyspaces_table" "{name}" {
encryption_specification {
type = "CUSTOMER_MANAGED_KMS"
kms_key = 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