Primary references
Use the original standards below to check terminology and requirements. These references explain the standards; they do not endorse CISGuard or independently verify its product coverage.
The CIS Amazon Elastic Kubernetes Service Benchmark v1.8.0 defines 48 controls specific to EKS clusters: IAM integration for cluster authentication, control-plane logging to CloudWatch, network policy via VPC CNI, EKS managed node groups, and EKS-specific control-plane hardening. Combined with the CIS Kubernetes Benchmark, this provides full EKS evidence.
CISGuard uses an IAM role mapped to a Kubernetes RBAC binding in the cluster. The IAM role is granted minimal read permissions via the EKS aws-auth ConfigMap. Multi-cluster scanning uses a centralized scanning identity with cross-cluster RBAC.
Yes. EKS Fargate (serverless containers) is supported. Fargate-specific controls focus on pod configuration since there are no customer-managed nodes. CISGuard validates Fargate profile configuration, pod security context, and applicable subset of Kubernetes benchmark controls.
Yes. EKS on AWS GovCloud (US-East and US-West) is supported. CISGuard configuration accommodates the GovCloud endpoints. GovCloud customers get the same Framework Coverage Reports as commercial AWS customers.
Our compliance engineers will scope your environment and quote within one business day of an initial briefing.
Use the original standards below to check terminology and requirements. These references explain the standards; they do not endorse CISGuard or independently verify its product coverage.