CloudTrail trail does not log all management events (Read + Write)
- Severity
- High
- Service
- CloudTrail
- Check ID
- CLOUDTRAIL_NOT_LOGGING_MANAGEMENT_EVENTS
What this check finds
This CloudTrail trail has custom event selectors configured but does not log both Read and Write management events. CIS requires all management events to be captured for complete audit coverage.
Passing looks like: CloudTrail logs all management events.
How to fix it
Update the trail event selectors to include all management events.
AWS CLI
aws cloudtrail put-event-selectors --trail-name TRAIL_NAME --event-selectors "[{\"ReadWriteType\":\"All\",\"IncludeManagementEvents\":true,\"DataResources\":[]}]"
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
CloudTrail → Trails → Edit → Management events → Read + Write.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| CIS AWS Foundations Benchmark v5.0.0 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More CloudTrail checks
- CriticalS3 bucket used for CloudTrail logs is publicly accessible
- MediumCloudTrail is not logging S3 data events
- MediumCloudTrail logs are not encrypted with KMS
- MediumCloudTrail logs are not integrated with CloudWatch Logs
- LowCloudTrail Insights is not enabled on the trail
- LowCloudTrail is not enabled
- LowCloudTrail log file validation is not enabled
- LowCloudTrail S3 bucket does not have server-access logging enabled