Container with elevated privileges assigned to a privileged Kubernetes node

Documentos > Datadog Security > OOTB Rules > Container with elevated privileges assigned to a privileged Kubernetes node

Set up the kubernetes integration.

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Description

Granting excessive security capabilities to a pod or container can lead to unintended lateral movement to other containers, access to the underlying Kubernetes node, or access to cloud provider resources. Assignment of the pod or container to a node with privileged roles or permissions can increase the blast radius of potential unauthorized access to cloud resources.

Remediation

Review your Kubernetes pod or container security context configurations to ensure they provide proper isolation boundaries between containers and host resources.
Apply possible mitigations, including the use of Kubernetes Pod Security Policies, SELinux, AppArmor, or Seccomp filters.
Review the assigned cloud provider roles and permissions on the assigned node to ensure they are scoped to the principle of least privilege.