Container with elevated privileges assigned to a privileged Kubernetes node

Set up the kubernetes integration.

이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

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

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