Check ID:
Provider: Kubernetes
Service:
Severity: HIGH
Categories:
Resource type:
core_minimize_net_raw_capability_admissionProvider: Kubernetes
Service:
coreSeverity: HIGH
Categories:
container-securityResource type:
PodWhat this check verifies
Kubernetes pods where any container’s security context adds theNET_RAW Linux capability are identified.
The inspection evaluates container securityContext.capabilities.add entries to detect explicit requests for NET_RAW.
Risk
Granting NET_RAW enables raw sockets for packet crafting and sniffing, undermining confidentiality and integrity. Attackers can run ARP/DNS spoofing, pivot or scan inside the cluster, bypass service isolation, exfiltrate data, and impact availability through network abuse.Recommendation
Apply least privilege: avoid addingNET_RAW and drop unnecessary Linux capabilities by default. Use cluster-wide admission policies to block requests for NET_RAW. When strictly required, isolate the workload, restrict egress with network controls, and audit capability use as part of defense in depth.
Remediation
- Terraform
- Dashboard steps
References
- https://support.icompaas.com/support/solutions/articles/62000234711-minimize-the-admission-of-containers-with-the-net-raw-capability
- https://dev.to/castai/kubernetes-security-10-best-practices-from-the-industry-and-community-1bp6?comments_sort=latest
- https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container
- https://istio.io/latest/docs/setup/additional-setup/pod-security-admission/
- https://github.com/aws-samples/k8s-psa-pss-testing
- https://kubernetes.io/docs/tasks/configure-pod-container/security-context
- https://kubernetes.io/docs/concepts/security/pod-security-admission/
Where this check fires
This check runs on every scheduled scan against your Kubernetes account. Findings appear at Cloud Security → Findings filterable byCheck ID = core_minimize_net_raw_capability_admission. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Kubernetes checks