Amazon Detective is not enabled
- Severity
- Low
- Service
- Threat detection
- Check ID
- DETECTIVE_NOT_ENABLED
What this check finds
Amazon Detective is not active. Detective automatically ingests CloudTrail, VPC flow logs, and GuardDuty findings into a behaviour graph for faster security investigation. Without it, incident response relies on manual log correlation.
Passing looks like: Amazon Detective enabled.
How to fix it
Enable Detective.
AWS CLI
aws detective create-graph
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Detective → Get started → Set up Detective. It automatically pulls data from enabled GuardDuty and CloudTrail.
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