Enhanced Cloud Security Policies for Kubernetes

The following available security policies include:

EKS CIS - Avoid use of system:masters group EKS CIS - Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster [Role] EKS CIS - Ensure Image Vulnerability Scanning using Amazon ECR image scanning or a third-party provider AKS CIS - Restrict Access to the Control Plane Endpoint AKS CIS - Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled AKS CIS - Use Azure RBAC for Kubernetes Authorization GKE CIS - Manage Kubernetes RBAC users with Google Groups for GKE GKE CIS - Ensure Kubernetes Web UI is Disabled K8s CIS - Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster [ClusterRole] K8s CIS - Ensure that all Namespaces have Network Policies defined K8s CIS - Minimize access to create pods through Cluster Role K8s CIS - Minimize access to secrets through Cluster Role K8s CIS - Minimize access to secrets through Role K8s CIS - Ensure that Service Account Tokens are only mounted where necessary for Service Account K8s CIS - Ensure that default service accounts are not actively used K8s CIS - Minimize access to create pods through Role K8s CIS - Minimize wildcard use in ClusterRoles K8s CIS - Minimize wildcard use in Roles K8s CIS - Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture

These security policies provide granular control and help ensure a secure Kubernetes environment.