← Policy catalog
</> ValidatingAdmissionPolicy · Apache-2.0

Runs With the Root Group (GID 0)

initcontainer-run-as-group

severityModerate resourceInitContainers productKubernetes bundles1

An init 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.

Rejects unless

!has(object.spec.initContainers) || object.spec.initContainers.all(ic,
  !has(ic.securityContext) ||
  !has(ic.securityContext.runAsGroup) ||
  ic.securityContext.runAsGroup > 0
)

spec.initContainers[*].securityContext.runAsGroup must be undefined or a non-zero value (> 0).

Remediation

Set runAsGroup to a non-zero GID such as 1000, or leave it unset. Field: spec.initContainers[*].securityContext.runAsGroup.

Applies to

  • pods · v1 · CREATE, UPDATE

Manifest

apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicy
metadata:
  name: initcontainer-run-as-group
  annotations:
    kubeapt.io/uuid: "14da0518-3885-4dcc-b859-a23056ea44d6"
    security.kubeapt.io/displayName: "Runs With the Root Group (GID 0)"
    security.kubeapt.io/description: "An init 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: "InitContainers"
    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.initContainers[*].securityContext.runAsGroup."
    security.kubeapt.io/product: "Kubernetes"
spec:
  failurePolicy: Fail
  matchConstraints:
    resourceRules:
    - apiGroups:
      - ''
      apiVersions:
      - v1
      operations:
      - CREATE
      - UPDATE
      resources:
      - pods
  validations:
  - expression: |
      !has(object.spec.initContainers) || object.spec.initContainers.all(ic,
        !has(ic.securityContext) ||
        !has(ic.securityContext.runAsGroup) ||
        ic.securityContext.runAsGroup > 0
      )
    message: |
      spec.initContainers[*].securityContext.runAsGroup must be undefined or a non-zero value (> 0).

Save it as initcontainer-run-as-group.yaml — the commands below assume that name.

Validate with kubeapt

Check a workload against this one policy, before anything is installed on a cluster.

$ kubeapt validate -p ./initcontainer-run-as-group.yaml -r ./workload.yaml

Or without the file, from the published policy set — -r takes a directory too:

$ kubeapt policies download && kubeapt validate --policy-name initcontainer-run-as-group -r ./manifests

Or against every namespace in the cluster your kubeconfig points at:

$ kubeapt validate --policy-name initcontainer-run-as-group -A