CloudTrail isn't logging
CloudTrail records API activity across your account. Without an active trail, there's no audit record of who created, changed or deleted anything.
Why it matters
After an incident, the first question is 'what happened and who did it'. Without CloudTrail there's no answer, and no way to scope the damage.
An active, multi-region trail delivering to a locked-down bucket is a baseline requirement in every cloud security standard.
How to check for it
- CloudTrail console → Trails. Confirm there's at least one multi-region trail with Logging = On.
- aws cloudtrail describe-trails and aws cloudtrail get-trail-status --name <trail> (IsLogging should be true).
How to fix it
- Create a multi-region CloudTrail trail delivering to an S3 bucket (CloudTrail → Create trail).
- Lock the destination bucket down (Block Public Access on, restrictive policy) and turn on log file validation.
- Forward the trail to CloudWatch Logs or a SIEM so changes are alerted on, not just stored.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Does CloudTrail cost a lot?
- One trail of management events is free; you pay for data events and storage. The cost of not having it — a blind incident — is far higher.