securityContext is not applied to pods and containers misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID	APPSEC_K8S_29
Category - Subcategory	Kubernetes - Access Control
Provider	OTHER
Severity	LOW
Framework	Helm, Kubernetes, Kustomize, Terraform, Terraform Plan

Impact

securityContext defines privilege and access control settings for your pod or container, and holds security configurations that will be applied to a container. Some fields are present in both securityContext and PodSecurityContext, when both are set, securityContext takes precedence. Well-defined privilege and access control settings will enhance assurance that your pod is running with the properties it requires to function.

How to Fix

Resource: Container / Pod / Deployment / DaemonSet / StatefulSet / ReplicaSet / ReplicationController / Job / CronJob

• Arguments: securityContext (Optional) A field that defines privilege and access control settings for your Pod or Container. [source,go]

---

apiVersion: v1 kind: Pod metadata: name: spec: containers:

• name: image:
• securityContext:

---

apiVersion: v1 kind: Pod metadata: name: spec:

• securityContext:

---

apiVersion: batch/v1beta1 kind: CronJob metadata: name: spec: schedule: <> jobTemplate: spec: template: spec:

• securityContext:

---

apiVersion: <> kind: metadata: name: spec: template: spec:

• securityContext:

---