Amazon GuardDuty not enabled
GuardDuty analyses CloudTrail, VPC flow and DNS logs for signs of compromise — stolen credentials, unusual API calls, communication with known-bad hosts. It needs no agents and is off until enabled.
Why it matters
Many cloud compromises are quiet: a leaked key used from a new country, an instance reaching a mining pool. GuardDuty is designed to catch exactly these.
Without it, the first sign of trouble is often the bill or an abuse report — far too late.
How to check for it
- aws guardduty list-detectors per region — an empty result means it's off there.
- Check that it's enabled in every region, not just the one you use most.
How to fix it
- Enable GuardDuty in all regions, ideally via the organisation (delegated administrator) so new accounts are covered automatically.
- Route findings to Security Hub or an alerting pipeline so someone sees them.
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
- Is GuardDuty expensive?
- Pricing scales with log volume and starts small; most teams find the cost minor next to the detection it provides. A 30-day trial shows your actual cost.