Ensure ElastiCache Redis parameter groups disable dangerous commands
Dangerous Redis commands like FLUSHALL, FLUSHDB, CONFIG should be renamed or disabled to prevent accidental or malicious data loss.
Security Impact
Dangerous commands can be exploited to flush all cached data or reconfigure the cluster, causing service disruption.
How to Remediate
Create custom parameter groups that rename dangerous commands. Use rename-commands parameter to disable FLUSHALL, FLUSHDB, CONFIG, EVAL.
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 Security Best Practices, Defense in Depth compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elasticache-12
- Service
- Amazon ElastiCache
- Category
- Configuration Security
- Severity
- MEDIUM
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 encryption in transit enabled
Ensure ElastiCache Redis clusters have AUTH enabled
Ensure ElastiCache clusters are not publicly accessible
Ensure ElastiCache Redis has automatic backups enabled