43 of 50 in All Controls
aws

Enable GuardDuty EKS Protection

IDAWS-SEC-004
Severity
high
Automation
Auto
Category
security
Enforcementrecommended
Complexity / Impact
low(none impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:root
Environments
all
Target Resources
AWS::GuardDuty::DetectorAWS::EKS::Cluster
Services
guarddutyeksorganizations
Tags
threat-detectionguarddutykubernetescontainersekslanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2AWS FSBP
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-20

Specification & Description

Enable Amazon GuardDuty EKS Protection (EKS_AUDIT_LOGS) across all AWS Organizations member accounts from the Security delegated administrator account to detect threats against Amazon EKS control planes.

Technical Specifications

GuardDuty EKS Audit Log Monitoring (EKS_AUDIT_LOGS) ingests Kubernetes audit logs directly from the Amazon EKS control plane without requiring customers to enable CloudWatch Logs export or manage log-forwarding agents.

Enabling EKS_AUDIT_LOGS with AutoEnable = ALL in the GuardDuty delegated administrator account detects anomalous Kubernetes API activity, anonymous access attempts, privileged pod creation, and cluster-role binding abuse across all member accounts.

Security Rationale

Kubernetes control-plane attacks occur inside the Kubernetes API layer rather than through standard AWS IAM API calls alone. Specialized EKS audit log analysis surfaces container orchestration threats that CloudTrail management events cannot observe.

Business & Security Impact

Without GuardDuty EKS Protection, attackers exploiting misconfigured RBAC policies, exposed Kubernetes API endpoints, or compromised service account tokens can escalate privileges inside EKS clusters undetected.

Operational & Implementation Notes

GuardDuty EKS Audit Log Monitoring pulls Kubernetes audit logs directly from the EKS control plane without requiring CloudWatch Logs export. For container runtime telemetry on worker nodes (FSBP GuardDuty.7), evaluate enabling the companion GuardDuty Runtime Monitoring feature (RUNTIME_MONITORING).

Compliance Framework Mappings (5)

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
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.5
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

Query the GuardDuty delegated administrator detector and organization configuration to confirm EKS_AUDIT_LOGS is ENABLED on the administrator detector and AutoEnable is ALL across the organization.

AWS CLI: Verify GuardDuty EKS_AUDIT_LOGS Status and Org Auto-Enablebash
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

aws guardduty describe-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "Features[?Name=='EKS_AUDIT_LOGS'].{Name:Name,AutoEnable:AutoEnable}" \
  --output json

aws guardduty get-detector \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "Features[?Name=='EKS_AUDIT_LOGS'].{Name:Name,Status:Status}" \
  --output json

Remediation Guide & Automation

In the GuardDuty delegated administrator (Security) account, enable the `EKS_AUDIT_LOGS` feature on the administrator detector and configure organization auto-enablement to `ALL` across active regions.

Step-by-Step Instructions

  1. In the GuardDuty delegated administrator (Security) account, enable the EKS_AUDIT_LOGS feature on the administrator detector.
  2. Update the GuardDuty organization configuration with EKS_AUDIT_LOGS AutoEnable set to ALL so existing and new accounts are covered automatically.
  3. Repeat configuration in every AWS region where EKS clusters are deployed.
  4. Monitor EKS findings in GuardDuty and Security Hub and route alerts to the incident response queue.
AWS CLI: Enable GuardDuty EKS Audit Log Monitoring for Organizationbash
# Run in the GuardDuty Delegated Administrator (Security) account
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

aws guardduty update-detector \
  --detector-id "$DETECTOR_ID" \
  --features Name=EKS_AUDIT_LOGS,Status=ENABLED \
  --region "$HOME_REGION"

aws guardduty update-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --auto-enable-organization-members ALL \
  --features Name=EKS_AUDIT_LOGS,AutoEnable=ALL \
  --region "$HOME_REGION"
Terraform: Enable GuardDuty EKS Audit Log Monitoring Featurehcl
variable "guardduty_detector_id" {
  type        = string
  description = "GuardDuty detector ID in the Security delegated administrator account."
}

resource "aws_guardduty_detector_feature" "eks_audit_logs" {
  detector_id = var.guardduty_detector_id
  name        = "EKS_AUDIT_LOGS"
  status      = "ENABLED"
}

resource "aws_guardduty_organization_configuration_feature" "eks_audit_logs" {
  detector_id = var.guardduty_detector_id
  name        = "EKS_AUDIT_LOGS"
  auto_enable = "ALL"

  depends_on = [aws_guardduty_detector_feature.eks_audit_logs]
}

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.