CloudTrail Insights is not enabled on the trail
- Severity
- Low
- Service
- CloudTrail
- Check ID
- CLOUDTRAIL_INSIGHTS_DISABLED
What this check finds
CloudTrail Insights detects unusual API call-rate and error-rate activity — the signal that surfaces credential misuse and enumeration that individually-valid API calls will not. A trail can be correctly configured for logging and still perform no anomaly detection at all.
Passing looks like: CloudTrail Insights enabled.
How to fix it
Enable Insights on the trail.
AWS CLI
aws cloudtrail put-insight-selectors --trail-name TRAIL --insight-selectors '[{"InsightType":"ApiCallRateInsight"},{"InsightType":"ApiErrorRateInsight"}]'
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
CloudTrail → Trails → select trail → Insights events → Edit.
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 |
|---|---|
| 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
- HighCloudTrail trail does not log all management events (Read + Write)
- MediumCloudTrail is not logging S3 data events
- MediumCloudTrail logs are not encrypted with KMS
- MediumCloudTrail logs are not integrated with CloudWatch Logs
- LowCloudTrail is not enabled
- LowCloudTrail log file validation is not enabled
- LowCloudTrail S3 bucket does not have server-access logging enabled