41 of 50 in All Controls
aws

Centralized GuardDuty Threat Detection

IDAWS-SEC-002
Severity
critical
Automation
Auto
Category
security
Enforcementmandatory
Complexity / Impact
medium(low impact)
Risk Profile
high likelihood(low residual)
Cloud Scopeaws:root
Environments
all
Target Resources
AWS::GuardDuty::DetectorAWS::Organizations::Policy
Services
guarddutyorganizations
Tags
threat-detectionguarddutymonitoringsecuritylanding-zone
Frameworks
NIST 800-53CIS AWSISO 27001PCI DSSSOC 2AWS FSBP
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-20

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 = ALL in 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.

Compliance Framework Mappings (6)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
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.

AWS CLI: Verify GuardDuty Admin, Detector Status, Auto-Enable, and Membersbash
# 1. Verify GuardDuty delegated administrator
aws guardduty list-organization-admin-accounts \
  --region "$HOME_REGION" \
  --query "AdminAccounts[*].{AdminAccountId:AdminAccountId,AdminStatus:AdminStatus}" \
  --output json

# 2. Capture detector ID and inspect detector, org auto-enable, and member status
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

aws guardduty get-detector \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "{Status:Status,FindingPublishingFrequency:FindingPublishingFrequency}" \
  --output json

aws guardduty describe-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "{AutoEnableOrganizationMembers:AutoEnableOrganizationMembers,MemberAccountLimitReached:MemberAccountLimitReached}" \
  --output json

aws guardduty list-members \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "Members[*].{AccountId:AccountId,RelationshipStatus:RelationshipStatus}" \
  --output json

Preventative Enforcement Policies

SCP: Prevent GuardDuty Disablement and Tampering in Member Accountsjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ProtectGuardDutyCentralization",
      "Effect": "Deny",
      "Action": [
        "guardduty:DeleteDetector",
        "guardduty:UpdateDetector",
        "guardduty:DisassociateFromAdministratorAccount",
        "guardduty:StopMonitoringMembers",
        "guardduty:DeleteMembers",
        "guardduty:DisassociateMembers",
        "guardduty:UpdateOrganizationConfiguration",
        "guardduty:UpdateMemberDetectors",
        "guardduty:DeletePublishingDestination",
        "guardduty:UpdatePublishingDestination"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/LandingZoneAdminRole"
          ]
        }
      }
    }
  ]
}
Terraform: Deploy and Attach GuardDuty Protection SCPhcl
variable "organization_root_id" {
  type        = string
  description = "AWS Organizations Root or OU ID where the SCP is attached."
}

resource "aws_organizations_policy" "guardduty_scp" {
  name        = "protect-guardduty"
  description = "Prevents member accounts from disabling or detaching GuardDuty"
  type        = "SERVICE_CONTROL_POLICY"

  content = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Sid    = "ProtectGuardDutyCentralization"
        Effect = "Deny"
        Action = [
          "guardduty:DeleteDetector",
          "guardduty:UpdateDetector",
          "guardduty:DisassociateFromAdministratorAccount",
          "guardduty:StopMonitoringMembers",
          "guardduty:DeleteMembers",
          "guardduty:DisassociateMembers",
          "guardduty:UpdateOrganizationConfiguration",
          "guardduty:UpdateMemberDetectors",
          "guardduty:DeletePublishingDestination",
          "guardduty:UpdatePublishingDestination"
        ]
        Resource = "*"
        Condition = {
          ArnNotLike = {
            "aws:PrincipalArn" = [
              "arn:aws:iam::*:role/LandingZoneAdminRole"
            ]
          }
        }
      }
    ]
  })
}

resource "aws_organizations_policy_attachment" "guardduty_scp_root" {
  policy_id = aws_organizations_policy.guardduty_scp.id
  target_id = var.organization_root_id
}

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

  1. From the Organizations Management account, enable trusted access for guardduty.amazonaws.com and designate the Security account as delegated administrator in every enabled region.
  2. In the Security delegated administrator account, verify or create an enabled GuardDuty detector in each operational region.
  3. Configure GuardDuty organization settings with AutoEnableOrganizationMembers set to ALL so all existing and future accounts are enrolled automatically.
  4. Integrate GuardDuty findings with Security Hub and EventBridge for automated high-severity alerting.
  5. Attach the protective SCP to the Organization Root to prevent member accounts from disabling or detaching GuardDuty.
AWS CLI: Enable GuardDuty Delegated Admin and Organization Auto-Enablebash
# 1. Management account: enable trusted access and designate Security account as delegated admin
aws organizations enable-aws-service-access \
  --service-principal guardduty.amazonaws.com

aws guardduty enable-organization-admin-account \
  --admin-account-id "$SECURITY_ACCOUNT_ID" \
  --region "$HOME_REGION"

# 2. Security (Delegated Admin) account: ensure detector exists and enable org-wide enrollment
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

if [ "$DETECTOR_ID" = "None" ] || [ -z "$DETECTOR_ID" ]; then
  DETECTOR_ID=$(aws guardduty create-detector \
    --enable \
    --region "$HOME_REGION" \
    --query "DetectorId" \
    --output text)
fi

aws guardduty update-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --auto-enable-organization-members ALL \
  --region "$HOME_REGION"
Terraform: Configure GuardDuty Delegated Admin and Organization Auto-Enablehcl
variable "security_account_id" {
  type        = string
  description = "12-digit AWS account ID of the central Security Tooling account."
}

variable "home_region" {
  type        = string
  description = "Target AWS region for GuardDuty administration."
}

provider "aws" {
  alias  = "security"
  region = var.home_region

  assume_role {
    role_arn = "arn:aws:iam::${var.security_account_id}:role/LandingZoneAdminRole"
  }
}

# Run in Management account
resource "aws_guardduty_organization_admin_account" "main" {
  admin_account_id = var.security_account_id
}

# Run in Security (Delegated Admin) account
resource "aws_guardduty_detector" "security_admin" {
  provider = aws.security
  enable   = true
}

resource "aws_guardduty_organization_configuration" "main" {
  provider                         = aws.security
  detector_id                      = aws_guardduty_detector.security_admin.id
  auto_enable_organization_members = "ALL"

  depends_on = [aws_guardduty_organization_admin_account.main]
}

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.