Policy does not restrict default capabilities Affecting Pod Security Policy service in Kubernetes
Severity Framework
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Snyk CCSS
Rule category
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Containers/ Capabilities
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
CIS-ControlsCIS-KubernetesCSA-CCM
- Snyk IDSNYK-CC-00637
- creditSnyk Research Team
Description
Default insecure capabilities are not restricted. Pods will be allowed to run with too many permissions, including RAW network resource access.
How to fix?
Add ALL or NET_RAW to requiredDropCapabilities attribute.
Add ALL or NET_RAW to requiredDropCapabilities attribute.
Example Configuration
resource "kubernetes_pod_security_policy" "allowed1" {
metadata {
name = "example-637a1"
}
spec {
privileged = false
allow_privilege_escalation = false
read_only_root_filesystem = true
required_drop_capabilities = ["all"]
run_as_user {
rule = "MustRunAsNonRoot"
}
se_linux {
rule = "RunAsAny"
}
supplemental_groups {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
fs_group {
rule = "MustRunAs"
range {
min = 1
max = 65535
}
}
}
}