Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
rds_cluster_integration_cloudwatch_logsProvider: AWS
Service:
rdsSeverity: MEDIUM
Categories:
loggingResource type:
AwsRdsDbClusterWhat this check verifies
RDS clusters running Aurora MySQL, Aurora PostgreSQL, MySQL, or PostgreSQL are assessed for CloudWatch Logs publishing, confirming that database logs are exported to a CloudWatch Logs group.Risk
Without publishing to CloudWatch, database events lack centralized visibility and retention. Brute-force, SQL injection, or privilege misuse may go undetected, hindering forensics and response, risking data confidentiality and integrity and delaying recovery.Recommendation
Publish RDS/Aurora logs to CloudWatch Logs and centralize analysis. Select appropriate types (e.g.,error, general, slowquery, audit), define retention, and create alarms. Limit log access with least privilege and integrate with SIEM for defense-in-depth monitoring.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/publishing_cloudwatchlogs.html
- https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_LogAccess.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-34
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = rds_cluster_integration_cloudwatch_logs. 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