Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
eks_control_plane_logging_all_types_enabledProvider: AWS
Service:
eksSeverity: MEDIUM
Categories:
logging, forensics-readyResource type:
AwsEksClusterWhat this check verifies
Amazon EKS clusters are evaluated for control plane logging coverage of required types:api, audit, authenticator, controllerManager, scheduler.
The finding identifies clusters where any of these log types are not configured.
Risk
Gaps in control plane logging reduce visibility across the cluster.- Confidentiality: undetected API access, RBAC abuse, token misuse
- Integrity: untraceable config changes and policy edits
- Availability: scheduler/controller issues lack evidence, delaying recovery and masking attacker persistence
Recommendation
Enable and standardize EKS control plane logging for all required types["api","audit","authenticator","controllerManager","scheduler"].
Apply least privilege to log access, set retention and alerts, and centralize analysis to support defense in depth, rapid detection, and reliable forensics.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/eks/latest/userguide/logging-monitoring.html
- https://support.icompaas.com/support/solutions/articles/62000233623-ensure-eks-control-plane-logging-is-enabled-for-all-required-log-types
- https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html
- https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/kubernetes-eks-logging.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = eks_control_plane_logging_all_types_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks