GuardDuty Not Enabled

Amazon GuardDuty is not enabled, or not in every Region and account, so activity such as credential misuse, reconnaissance and crypto-mining is not detected.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator
CVSS 4.02.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-778: Insufficient Logging
OWASP Top 10A09:2025 Security Logging and Alerting Failures
CategoryInsufficient Logging

Description

Amazon GuardDuty is AWS's managed threat detection service. Once enabled in a Region, it analyses CloudTrail management events, VPC Flow Logs and DNS query logs, which it reads from its own independent streams without the account having to enable those logs, and raises findings for activity such as the use of EC2 instance credentials from outside AWS, API calls from known malicious addresses, unusual console sign-ins, port scanning and communication with crypto-mining or command-and-control infrastructure. Optional protection plans extend it to S3 data events, EKS audit logs, runtime monitoring of EC2, ECS and EKS workloads, malware scanning, RDS login activity and Lambda network activity.

Common attacks on AWS accounts, such as the use of leaked access keys, theft of instance role credentials and deployment of crypto-mining resources, raise GuardDuty findings soon after they begin when it is enabled. Without GuardDuty or an equivalent detection capability, an intruder using stolen credentials, a compromised instance or an exposed resource can operate for longer before anyone notices. The weakness gives no access on its own; it reduces the organisation's ability to detect and contain a compromise, which raises the impact of other weaknesses, and the risk is lower where an equivalent third-party detection service covers the account.

GuardDuty is enabled per Region, through one detector per account in each Region, and in an AWS organisation is normally managed from a delegated administrator account that enables it for every member. The finding is raised when there is no detector in one or more Regions, when a detector is suspended, or when member accounts are not enrolled. It is confirmed with aws guardduty list-detectors and aws guardduty get-detector in each Region, or in the GuardDuty console of the delegated administrator, and is reported by Prowler and Security Hub.

Remediation

Enable GuardDuty in every Region, including Regions the organisation does not use, since attackers favour unwatched Regions:

  • In an AWS organisation, designate a security account as the GuardDuty delegated administrator and turn on automatic enablement for all existing and new member accounts, in each Region.
  • Enable the protection plans relevant to the estate, such as S3 Protection for accounts holding sensitive data and Runtime Monitoring for EC2, ECS and EKS workloads.
  • Send findings to the people who will act on them, for example through Amazon EventBridge to a ticketing or paging system, or through Security Hub to a SIEM, and define how high-severity findings are handled.
  • Where Regions are not used at all, also consider denying them with a service control policy.

Confirm the fix with aws guardduty list-detectors returning an enabled detector in every Region, and by checking in the delegated administrator that all member accounts are enabled. GuardDuty's sample findings can be used to check that alerts reach their destination.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More AWS Findings

Every AWS finding