Risky container allows escaping to a node with privileged cloud permissions

kubernetes

Set up the kubernetes integration.

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

Description

A risky container has been identified on a privileged node. This could lead to a container escape, potentially escalating to privileged access to the associated cloud node. This situation poses a risk as it could lead to granting unauthorized control over your cloud environment.

Remediation

  1. Apply patches or security fixes to the affected application.
  2. Revisit your Kubernetes pod/container configurations. Avoid using containers that run as root and enforce security practices using Kubernetes Pod Security Policies, SELinux, AppArmor, or Seccomp.