# GuardDuty can be enabled by AWS Organizations declarative policies

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

AWS announced on 1 October 2026 that Amazon GuardDuty supports AWS Organizations declarative policies. A delegated administrator can set an enablement baseline at the organization root, an OU or an account, with per-Region overrides, and enablement set by a policy cannot be changed from the GuardDuty console or API.

AWS announced that Amazon GuardDuty now supports AWS Organizations declarative policies, so GuardDuty threat detection can be enabled centrally across every account and Region in an organization. The announcement, posted 1 October 2026, says the configuration applies to existing accounts and is maintained as new accounts join, with a default configuration for every Region where GuardDuty is available and optional per-Region overrides for exceptions.

AWS also states that enablement set by a policy cannot be overridden through the GuardDuty console or API. For guardrail owners this extends the declarative policy model, already used for settings such as image sharing, to a security service, so account owners cannot quietly turn detection off. The delegated administrator needs permission to manage GuardDuty policies before creating one.

## Related pages

- [VPC Service Controls folder membership and folder rules reach GA](/news/vpc-sc-folders-organizations-in-rules-ga/)
- [ECS extends CPU and memory IAM condition keys to RunTask](/news/ecs-cpu-memory-condition-keys-runtask/)
- [VPC Service Controls perimeters can be edited with deleted principals](/news/vpc-sc-deleted-principals-in-perimeters-preview/)
- [All of them](/news/)

## Sources

- https://aws.amazon.com/about-aws/whats-new/2026/10/guardduty-org-enablement-policies/ (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/news/guardduty-declarative-policies-organization-enablement/
