Ensure ElastiCache Memcached clusters are not using default port
Using non-default ports adds obscurity and reduces automated scanning effectiveness, though should not be sole security measure.
Security Impact
Default ports are commonly targeted by automated scanners and attacks, increasing exposure to reconnaissance.
How to Remediate
Configure custom ports instead of default (Redis: 6379, Memcached: 11211) when creating clusters. Update application configurations.
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 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-8
- Service
- Amazon ElastiCache
- Category
- Network Security
- Severity
- LOW
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