Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
documentdb_cluster_cloudwatch_log_exportProvider: AWS
Service:
documentdbSeverity: MEDIUM
Categories:
loggingResource type:
AwsRdsDbClusterWhat this check verifies
Amazon DocumentDB clusters are evaluated for exportingaudit and profiler logs to CloudWatch Logs.
Clusters missing one or both log types are identified as lacking complete log export configuration.
Risk
Missing audit and/or profiler exports reduces observability of authentication, authorization, and data definition activity. Attacks like brute-force logins, privilege abuse, or destructive schema changes can go unnoticed, degrading confidentiality and integrity and delaying incident response.Recommendation
Enable export of bothaudit and profiler logs to CloudWatch Logs for all clusters and centralize analysis.
Apply least privilege to log access, define retention and immutability, integrate with alerting, and use separation of duties to protect and regularly review logs for defense in depth.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/documentdb-controls.html#documentdb-4
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/DocumentDB/enable-profiler.html
- https://docs.aws.amazon.com/cli/latest/reference/docdb/create-db-cluster.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 = documentdb_cluster_cloudwatch_log_export. 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