Ensure EKS cluster uses GuardDuty for threat detection
GuardDuty EKS Protection should be enabled for runtime threat detection.
Security Impact
Without GuardDuty, malicious activity in EKS clusters may not be detected.
How to Remediate
Enable GuardDuty EKS Protection for EKS audit log monitoring and runtime monitoring.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Kubernetes Service (EKS) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-eks-19
- Service
- Elastic Kubernetes Service (EKS)
- Category
- Threat Detection
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Elastic Kubernetes Service (EKS) Checks
View all checksEnsure EKS cluster endpoint is not publicly accessible
Ensure EKS cluster has secrets encryption enabled
Ensure EKS cluster logging is enabled
Ensure EKS node groups use managed node groups
Ensure EKS clusters use the latest Kubernetes version