initcontainer-capabilities-add
Linux capabilities beyond the baseline set, such as SYS_ADMIN, SYS_MODULE, SYS_PTRACE or NET_RAW, hand an init container kernel level privileges it can use to mount filesystems, load modules and break out onto the node.
(has(object.spec.os) &&
has(object.spec.os.name) &&
object.spec.os.name.lowerAscii() == "windows") ||
!has(object.spec.initContainers) || object.spec.initContainers.all(ic,
!has(ic.securityContext) ||
!has(ic.securityContext.capabilities) ||
!has(ic.securityContext.capabilities.add) ||
ic.securityContext.capabilities.add.all(cap,
variables.allowedCaps.exists(a, a == cap)
)
)
Only the baseline capabilities may be added by initContainers: AUDIT_WRITE, CHOWN, DAC_OVERRIDE, FOWNER, FSETID, KILL, MKNOD, NET_BIND_SERVICE, SETFCAP, SETGID, SETPCAP, SETUID, SYS_CHROOT.
allowedCaps
["AUDIT_WRITE","CHOWN","DAC_OVERRIDE","FOWNER","FSETID","KILL",
"MKNOD","NET_BIND_SERVICE","SETFCAP","SETGID","SETPCAP","SETUID","SYS_CHROOT"]
Drop the non-baseline entries from the added capability list and keep only baseline names such as CHOWN, KILL, SETGID, SETUID and NET_BIND_SERVICE. Field: spec.initContainers[*].securityContext.capabilities.add.
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionPolicy
metadata:
name: initcontainer-capabilities-add
annotations:
kubeapt.io/uuid: "9de7568a-b2d1-4e55-9bef-dba6c1a2f38f"
security.kubeapt.io/displayName: "Adds a Capability Outside the Baseline Set"
security.kubeapt.io/description: "Linux capabilities beyond the baseline set, such as SYS_ADMIN, SYS_MODULE, SYS_PTRACE or NET_RAW, hand an init container kernel level privileges it can use to mount filesystems, load modules and break out onto the node."
security.kubeapt.io/resource: "InitContainers"
security.kubeapt.io/severity: "Moderate"
security.kubeapt.io/remediation: "Drop the non-baseline entries from the added capability list and keep only baseline names such as CHOWN, KILL, SETGID, SETUID and NET_BIND_SERVICE. Field: spec.initContainers[*].securityContext.capabilities.add."
security.kubeapt.io/product: "Kubernetes"
spec:
failurePolicy: Fail
matchConstraints:
resourceRules:
- apiGroups:
- ''
apiVersions:
- v1
operations:
- CREATE
- UPDATE
resources:
- pods
variables:
- name: allowedCaps
expression: |
["AUDIT_WRITE","CHOWN","DAC_OVERRIDE","FOWNER","FSETID","KILL",
"MKNOD","NET_BIND_SERVICE","SETFCAP","SETGID","SETPCAP","SETUID","SYS_CHROOT"]
validations:
- expression: |
(has(object.spec.os) &&
has(object.spec.os.name) &&
object.spec.os.name.lowerAscii() == "windows") ||
!has(object.spec.initContainers) || object.spec.initContainers.all(ic,
!has(ic.securityContext) ||
!has(ic.securityContext.capabilities) ||
!has(ic.securityContext.capabilities.add) ||
ic.securityContext.capabilities.add.all(cap,
variables.allowedCaps.exists(a, a == cap)
)
)
message: |
Only the baseline capabilities may be added by initContainers: AUDIT_WRITE, CHOWN, DAC_OVERRIDE, FOWNER, FSETID, KILL, MKNOD, NET_BIND_SERVICE, SETFCAP, SETGID, SETPCAP, SETUID, SYS_CHROOT.Save it as initcontainer-capabilities-add.yaml — the commands below assume that name.
Check a workload against this one policy, before anything is installed on a cluster.
$ kubeapt validate -p ./initcontainer-capabilities-add.yaml -r ./workload.yamlOr without the file, from the published policy set — -r takes a directory too:
$ kubeapt policies download && kubeapt validate --policy-name initcontainer-capabilities-add -r ./manifestsOr against every namespace in the cluster your kubeconfig points at:
$ kubeapt validate --policy-name initcontainer-capabilities-add -A