Enable GuardDuty EKS Protection
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).
Related Controls & Guardrails (1)
Official References
Compliance Framework Mappings (5)
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 |
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.
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
- In the GuardDuty delegated administrator (Security) account, enable the EKS_AUDIT_LOGS feature on the administrator detector.
- Update the GuardDuty organization configuration with EKS_AUDIT_LOGS AutoEnable set to ALL so existing and new accounts are covered automatically.
- Repeat configuration in every AWS region where EKS clusters are deployed.
- Monitor EKS findings in GuardDuty and Security Hub and route alerts to the incident response queue.