Minimize the admission of containers wishing to share the host process ID namespace

チェック方法

監査方法: シェルコマンド

out=$(kubectl get pods -A -o go-template='{{range .items}}{{.metadata.namespace}} {{.metadata.name}} {{.spec.hostPID}}{{"\n"}}{{end}}') || exit 1
bad=$(printf '%s\n' "$out" | awk -v ex='^(kube-system|kube-public|kube-node-lease)$' 'NF && $1 !~ ex && ($3=="true")')
if [ -z "$bad" ]; then echo compliant; else printf '%s\n' "$bad" | head -n 25; fi

期待される出力

compliant

修正方法

修正方法: ガイダンスまたは IaC パッチ

Configure Pod Security Admission on workload namespaces so pods that request spec.hostPID: true are denied at admission time. In current EKS guidance, AWS recommends applying Pod Security Standards with at least the baseline profile cluster-wide and the restricted profile for workload namespaces. AWS also states that the baseline profile prohibits hostPID, while restricted inherits that restriction. For remediation, use enforce because AWS documents that only enforce rejects violating pods. warn and audit can help during rollout, but they do not block admission. • Label each workload namespace to enforce restricted. kubectl label ns NAMESPACE pod-security.kubernetes.io/enforce=restricted --overwrite • Add warn and audit during transition if you want visibility into violations before or alongside enforcement.

このホストをチェック

監査が許可されているマシンで実行してください。スキャンは読み取り専用です。

tmaegis scan --target eks