GuardDuty Not Enabled
Nothing is watching this account for threats, so credential misuse, crypto-mining and reconnaissance go unnoticed.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable GuardDuty.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- GuardDuty Detectors on AWS
- The fix, by hand
- GuardDuty → Settings → check current status. If detector is suspended, choose Resume.
- If no detector exists: GuardDuty → Get started → Enable GuardDuty.
- Enable optional protection plans relevant to your stack: S3, EKS, RDS, Lambda, Malware Protection.
- Configure findings export: Settings → Findings export → S3 bucket + KMS key (long-term retention).
- EventBridge rule → forward high/critical findings to SNS / Slack / PagerDuty.
- Enable across all active regions; use AWS Organizations to delegate the GuardDuty admin account if you have multiple accounts.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1100- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.