cis-aks-t1.2.0, cis-eks-t1.2.0, security, cis-v1.23-t1.0.1
A security context defines the operating system security settings (uid, gid, capabilities, SELinux role, etc..) applied to a container. When designing your containers and pods, make sure that you configure the security context for your pods, containers, and volumes. A security context is a property defined in the deployment yaml. It controls the security parameters that will be assigned to the pod/container/volume. There are two levels of security context: pod level security context, and container level security context.
ControlPlaneInfo, CronJob, DaemonSet, Deployment, Job, Pod, ReplicaSet, StatefulSet
Check that pod and container security context fields according to recommendations in CIS Security Benchmark for Docker Containers
Review the pod definitions in your cluster and verify that you have security contexts defined as appropriate.
Follow the Kubernetes documentation and apply security contexts to your pods. For a suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker Containers.
If you incorrectly apply security contexts, you may have trouble running the pods.
By default, no security contexts are automatically applied to pods.
Updated 6 days ago