Publicly accessible application in a 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 increases the blast radius of 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: dgreen15/github-error-fix