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.