Attack in progressA leaked CI key of ‹ci-deploy-bot› is being used to break in: 6 accounts and machines created.Open the case
Privileged workload setup V-031
Finds privileged pods, pods sharing the host's namespaces, sensitive host mounts and root pods outside the allowed system namespaces.
Checks
| Checks | Needs |
|---|---|
| Checks that no workload outside the system namespaces runs a privileged container. | k8s workload, k8s pod |
| Checks that no workload outside the system namespaces shares the node's process, IPC or network namespace. | k8s workload, k8s pod |
| Checks that no workload outside the system namespaces mounts a sensitive directory of the node. | k8s workload, k8s pod |
| Checks that no workload outside the system namespaces runs a container as root. | k8s workload, k8s pod |
Coverage
Could not read anything this run
Run history
No run has recorded this rule yet.
Findings
No open findings.
What it fed
No case has used a finding of this rule in the last 30 days.
Techniques
None mapped.
How to fix
kubectl get clusterrolebinding -o yaml / DescribeAccessEntry → remove the binding or access policy through GitOps; reversible