services / Google Cloud / Kubernetes Engine Pods

A Kubernetes Pod is a logical host that encapsulates one or more Containers. It is the smallest and most basic unit of deployment. Containers can communicate with each other via localhost. Pod lifecycle is typically managed by a higher level controller, such as a Deployment, StatefulSet, or DaemonSet.

The risks associated with Pods is similar to Deployments, StatefulSets, and DaemonSets. Pods consume CPU, memory, and network resources of the cluster, thus they are susceptible to exhaustion attacks. Containers inside Pods run a specific image, and may lead to arbitrary code execution in the cluster if an attacker is able to run their image. Pods also need access to other resources within the cluster, and outside the cluster, often using other services of the cloud provider. In order to do so, Pods have service account credentials, which, if leaked, allow one to move laterally by authenticating as the service account.


Deleting a pod deletes its pods and ephemeral volumes. PersistentVolumes attached to the pod are left intact. Logs of the deleted pod disappear permanently when the pods shut down, unless they are exported to an external system for persistence.



This privilege may grant access to confidential data, or its exploit can incur operational cost.

Contributed by P0 Security

© 2023–present P0 Security and contributors to the IAM Privilege Catalog