Policy allows `privileged` containers Affecting Deployment 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/ Best Practices
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-ControlsCSA-CCM
- Snyk IDSNYK-CC-00629
- creditSnyk Research Team
Description
Pods will be able to run with privileged mode.
How to fix?
Remove privileged attribute, or set vault to false.
Remove privileged attribute, or set vault to false.
Example Configuration
resource "kubernetes_pod_security_policy" "allowed1" {
metadata {
name = "example-629a1"
}
spec {
privileged = false
allow_privilege_escalation = false
read_only_root_filesystem = true
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
}
}
}
}