Skip to main content

⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 AWS → 📁 GuardDuty

🛡️ AWS GuardDuty Detector EKS Audit Log Monitoring is not enabled🟢

Logic​

Similar Policies​

Description​

Open File

Description​

This policy identifies AWS GuardDuty Detectors that have EKS Audit Log Monitoring disabled. This feature is a part of GuardDuty EKS Protection, which provides specialized threat detection for Amazon Elastic Kubernetes Service (EKS) clusters.

GuardDuty analyzes Kubernetes audit logs from your EKS clusters to detect suspicious activity and potential security threats, such as privilege escalation, use of exposed credentials, or connections from known malicious IP addresses.

Rationale​

Kubernetes audit logs provide a chronological, security-relevant record of actions and events within a cluster. Monitoring these logs is crucial for detecting unauthorized access, suspicious API calls, and other malicious activities that could compromise your containerized applications. Disabling this feature creates a significant blind spot in your container security posture.

Impact​

Enabling this feature will incur costs based on the volume of EKS audit logs analyzed by GuardDuty.

Audit​

This policy flags an AWS GuardDuty Detector as INCOMPLIANT if its Data Sources contain Kubernetes Audit Logs Status set to DISABLED.

Remediation​

Open File

Remediation​

Enable EKS Audit Log Monitoring​

From Command Line​

Enable EKS Audit Log Monitoring for a specific GuardDuty detector using the following command:

aws guardduty update-detector \
    --detector-id {{detector-id}} \
    --region {{region}} \
    --data-sources "Kubernetes={AuditLogs={Enable=true}}"

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [GuardDuty.5] GuardDuty EKS Audit Log Monitoring should be enabled1no data
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration60no data