Ensure CloudTrail trails are not stopped
CloudTrail trails should be actively logging. Stopped trails create gaps in audit logs.
Security Impact
Stopped trails allow malicious activity to go unlogged, preventing detection and forensic analysis.
How to Remediate
Start any stopped trails: aws cloudtrail start-logging --name TRAIL_NAME. Set up CloudWatch alarms for trail status.
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 AWS CloudTrail 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, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudtrail-11
- Service
- AWS CloudTrail
- Category
- Logging
- Severity
- CRITICAL
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS CloudTrail Checks
View all checksEnsure CloudTrail is enabled in all regions
Ensure CloudTrail log file validation is enabled
Ensure CloudTrail logs are encrypted with KMS
Ensure CloudTrail S3 bucket is not publicly accessible
Ensure CloudTrail logs are delivered to CloudWatch Logs