container-run-as-group
A container running with GID 0 places its processes in the root group, which owns or can write many files in images and mounted host volumes, widening what a compromised process reaches.
object.spec.containers.all(c,
!has(c.securityContext) ||
!has(c.securityContext.runAsGroup) ||
c.securityContext.runAsGroup > 0
)
spec.containers[*].securityContext.runAsGroup must be undefined or a non-zero value (> 0).
Set runAsGroup to a non-zero GID such as 1000, or leave it unset. Field: spec.containers[*].securityContext.runAsGroup.
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicy
metadata:
name: container-run-as-group
annotations:
kubeapt.io/uuid: "37bb1c69-4a89-4758-86cc-1d500f27a7a1"
security.kubeapt.io/displayName: "Runs With the Root Group (GID 0)"
security.kubeapt.io/description: "A container running with GID 0 places its processes in the root group, which owns or can write many files in images and mounted host volumes, widening what a compromised process reaches."
security.kubeapt.io/resource: "Containers"
security.kubeapt.io/severity: "Moderate"
security.kubeapt.io/remediation: "Set runAsGroup to a non-zero GID such as 1000, or leave it unset. Field: spec.containers[*].securityContext.runAsGroup."
security.kubeapt.io/product: "Kubernetes"
spec:
failurePolicy: Fail
matchConstraints:
resourceRules:
- apiGroups:
- ''
apiVersions:
- v1
operations:
- CREATE
- UPDATE
resources:
- pods
validations:
- expression: |
object.spec.containers.all(c,
!has(c.securityContext) ||
!has(c.securityContext.runAsGroup) ||
c.securityContext.runAsGroup > 0
)
message: |
spec.containers[*].securityContext.runAsGroup must be undefined or a non-zero value (> 0).Save it as container-run-as-group.yaml — the commands below assume that name.
Check a workload against this one policy, before anything is installed on a cluster.
$ kubeapt validate -p ./container-run-as-group.yaml -r ./workload.yamlOr without the file, from the published policy set — -r takes a directory too:
$ kubeapt policies download && kubeapt validate --policy-name container-run-as-group -r ./manifestsOr against every namespace in the cluster your kubeconfig points at:
$ kubeapt validate --policy-name container-run-as-group -A