ValidatingAdmissionPolicy for C-0013

[suhasgumma]

Control C-0013

Related Resources: CronJob, DaemonSet, Deployment, Job, Pod, ReplicaSet, StatefulSet

Control Docs: https://hub.armosec.io/docs/c-0013

Control Rego: https://github.com/kubescape/regolibrary/blob/master/rules/non-root-containers/raw.rego

[suhasgumma]

Hi @slashben, there is a mismatch between the documentation and the rego functionality.

This is what the rego actually does:

• Check whether runAsUser is set to a non-zero value or runAsNonRoot is set to true in PodSecurityContext. If both of them result in false, rego checks the same in every ContainerSecurityContext. Even if one container returns false for both checks, the control fails.
• Checks if allowPrivilegeEscalation is set to false in PodSecurityContext. If it is not set or set to true, rego checks the same in every ContainerSecurityContext. Even if one container did not set "allowPrivilegeEscalation" or set it to true, the control fails.

[suhasgumma]

• There is one more issue. PodSecurityContext does not support allowPrivilegeEscalation.
  For more details, see this issue: "allowPrivilegeEscalation" is not supported at Pod Scope regolibrary#186

• Keeping that in mind, I've written CEL such that it directly checks if each container set the securityContext.allowPrivilegeEscalation to false. Even if one container did not set it, the control fails.

[slashben]

This is a very complex control, I will review a bit later

[Daniel-GrunbergerCA]

Hi @suhasgumma
Please note that the if and else statements are evaluated in order (https://www.openpolicyagent.org/docs/latest/policy-language/#else-keyword).
That means that first we check the container security context for the given fields, and only if they are not present there, we check the Pod security context. The reason for that being that the container security context takes precedence over the Pod security context (https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#securitycontext-v1-core).
This behavior needs to be reflected on your check as well. For example, it is possible that runAsNonRoot will be set to true in the Pod security context, and runAsUser will be set to non-zero in the container security context, and so on.

[suhasgumma]

Thank you @Daniel-GrunbergerCA . ContainerSecurityContext takes precedence. Only if the values are not set, we should check in PodSecurityContext. I will implement the control according to this logic and get back to you.

[suhasgumma]

Hi @Daniel-GrunbergerCA, this is what I have done:

• Check if allowPreviligeEscalation is set to false in ContainerSecurityContext. Only if it is not set, check for it in PodSecurityContext. The control fails if it is not set to false.

• Check either runAsNonRoot is set to true or runAsUser is non-zero. Only if they are not set in ContainerSecurityContext, fetch their values from PodSecurityContext if they are set there.

[Daniel-GrunbergerCA]

Good job! Sorry for the delay :)

[matthyx]

@slashben can you have a look, Daniel did approve in the past, but a second review before merging would be good