Ensure ElastiCache Redis clusters have encryption in transit enabled
Encryption in transit protects data moving between cache nodes and between cache and clients using TLS, preventing man-in-the-middle attacks.
Security Impact
Unencrypted in-transit data can be intercepted on the network, exposing sensitive cached data and session information.
How to Remediate
Enable in-transit encryption when creating Redis clusters. Requires Redis version 3.2.6 or later. Update client applications to use TLS connections.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon ElastiCache resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS AWS v2.0, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elasticache-2
- Service
- Amazon ElastiCache
- Category
- Encryption
- Severity
- HIGH
- CIS Benchmark
- 6.2
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon ElastiCache Checks
View all checksEnsure ElastiCache Redis clusters have encryption at rest enabled
Ensure ElastiCache Redis clusters have AUTH enabled
Ensure ElastiCache clusters are not publicly accessible
Ensure ElastiCache Redis has automatic backups enabled
Ensure ElastiCache Redis uses Multi-AZ with automatic failover