Ensure CloudWatch Anomaly Detection is configured for critical metrics
Anomaly detection should be enabled for critical metrics to detect unusual patterns.
Security Impact
Static thresholds may miss anomalies that fall within normal ranges but are unusual for the time.
How to Remediate
Configure anomaly detection models for critical metrics and create alarms based on anomalies.
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 CloudWatch 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 SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudwatch-13
- Service
- Amazon CloudWatch
- Category
- Monitoring
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon CloudWatch Checks
View all checksEnsure CloudWatch log groups have retention configured
Ensure CloudWatch log groups are encrypted with KMS
Ensure CloudWatch Alarms exist for root account usage
Ensure CloudWatch Alarms exist for unauthorized API calls
Ensure CloudWatch Alarms have SNS notifications configured