cyberstrikeus CIS Kubernetes Benchmark v1.12.0 - Control 4.2.13
Description
Ensure that the Kubelet sets limits on the number of PIDs that can be created by pods running on the node.
Rationale
By default pods running in a cluster can consume any number of PIDs, potentially exhausting the resources available on the node. Setting an appropriate limit reduces the risk of a denial of service attack on cluster nodes.
Impact
Setting this value will restrict the number of processes per pod. If this limit is lower than the number of PIDs required by a pod it will not operate.
Audit Procedure
Review the Kubelet's start-up parameters for the value of --pod-max-pids, and check the Kubelet configuration file for the PodPidsLimit. If neither of these values is set, then there is no limit in place.
Remediation
Decide on an appropriate level for this parameter and set it, either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
Default Value
By default the number of PIDs is not limited.
References
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 16.11 Leverage Vetted Modules or Services for Application Security ComponentsLeverage vetted modules or services for application security components, such as identity management, encryption, and auditing and logging. | ● | ● | |
| v7 | 9.2 Ensure Only Approved Ports, Protocols and Services Are RunningEnsure that only network ports, protocols, and services listening on a system with validated business needs, are running on each system. | ● | ● |
Profile Applicability
- Level 1 - Worker Node
Assessment Status
Manual