Centralized GuardDuty Threat Detection
Specification & Description
Enable Amazon GuardDuty across all AWS Organizations accounts and enabled regions, centralizing detector administration and threat findings in the designated Security delegated administrator account.
Technical Specifications
Amazon GuardDuty analyzes AWS CloudTrail management events, VPC Flow Logs, and DNS query logs to detect unauthorized activity and compromised identities or workloads without deploying host agents.
1. Delegated Administration and Auto-Enablement
- Register the Security account as the GuardDuty delegated administrator from the Organizations Management account.
- Enable
AutoEnableOrganizationMembers = ALLin every enabled AWS region so both existing and newly provisioned accounts are enrolled automatically.
2. Cross-Account Alerting and Tamper Prevention
- Forward high-severity findings from the Security account via Amazon EventBridge or SNS into incident response workflows.
- Attach a Service Control Policy (SCP) at the Organization Root preventing member accounts from deleting detectors, stopping member monitoring, or disassociating from the administrator account.
Security Rationale
Proactive threat detection is essential for identifying account compromises, credential misuse, and command-and-control activity early across the organization. GuardDuty delivers managed detection across foundational data sources without custom log pipelines or sensor infrastructure.
Business & Security Impact
Without centralized GuardDuty coverage, cross-account attack patterns and malicious activity in individual workload accounts go unnoticed, delaying containment and increasing incident blast radius.
Operational & Implementation Notes
GuardDuty is regional. Repeat delegated administrator configuration, detector checks, and organization auto-enablement across every enabled AWS region in the landing zone (typically via Terraform region modules or StackSets), and forward findings to Security Hub for centralized cross-region visibility.
Related Controls & Guardrails (2)
Official References
Compliance Framework Mappings (6)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | SI-4 | 1 |
CIS AWS Foundations Benchmark v3.0CIS AWS | 4.15 | 1 |
ISO 27001:2022ISO 27001 | A.8.16 | 1 |
PCI DSS v4.0PCI DSS | 11.5.2 | 1 |
SOC 2SOC 2 | CC7.2 | 1 |
AWS Foundational Security Best PracticesAWS FSBP | GuardDuty.1 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Verify that the GuardDuty delegated administrator is registered, confirm the Security account detector is ENABLED in each operational region, verify AutoEnableOrganizationMembers is set to ALL, and confirm all member accounts report an Enabled relationship status.
Preventative Enforcement Policies
Remediation Guide & Automation
From the AWS Organizations Management account, enable trusted access for GuardDuty and designate the Security account as delegated administrator. From the Security account in each enabled region, ensure a detector is active and set auto-enablement to ALL for existing and new member accounts.
Step-by-Step Instructions
- From the Organizations Management account, enable trusted access for guardduty.amazonaws.com and designate the Security account as delegated administrator in every enabled region.
- In the Security delegated administrator account, verify or create an enabled GuardDuty detector in each operational region.
- Configure GuardDuty organization settings with AutoEnableOrganizationMembers set to ALL so all existing and future accounts are enrolled automatically.
- Integrate GuardDuty findings with Security Hub and EventBridge for automated high-severity alerting.
- Attach the protective SCP to the Organization Root to prevent member accounts from disabling or detaching GuardDuty.