Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
elasticache_redis_replication_group_auth_enabledProvider: AWS
Service:
elasticacheSeverity: MEDIUM
Categories:
identity-accessResource type:
OtherWhat this check verifies
Amazon ElastiCache Redis replication groups running versions prior to6.0 are evaluated for the use of AUTH tokens. For 6.0+, the finding indicates ACL/RBAC configuration should be reviewed instead of token-based AUTH.
Risk
Without AUTH on pre-6.0 clusters, clients can run unauthenticated commands, enabling data reads/writes, key deletion, and cache poisoning. This threatens confidentiality and integrity, and can facilitate lateral movement via stolen or injected session data.
Recommendation
Apply defense in depth:- For versions <
6.0, enable AUTH with strong, rotated tokens and require in-transit encryption. - For
6.0+, prefer RBAC/ACLs with least-privilege, deny-by-default roles. - Restrict network access to trusted sources and audit access regularly.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws elasticache modify-replication-group —replication-group-id <example_resource_id> —auth-token <AUTH_TOKEN> —auth-token-update-strategy SET —apply-immediately
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/elasticache-controls.html#elasticache-6
- https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/auth.html#auth-modifyng-token
- https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/auth.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = elasticache_redis_replication_group_auth_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks