Cache services must enforce TLS encryption in transit
High
Cross-cloud
General
redis-encryption-in-transit
Applies to
Microsoft.Cache/redisAWS::ElastiCache::CacheClusterAWS::ElastiCache::ReplicationGroup
What CGPulse checks
A resource passes this rule when minimumTlsVersion must be one of ["1.2","1.3"] OR transitEncryptionEnabled must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable encryption in transit to protect data from interception during replication. In AWS Console: ElastiCache > Replication groups > enable Transit encryption. See: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/in-transit-encryption.html
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 Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening
- Kubernetes clusters must restrict public API access