cyberstrikeus CIS Kubernetes Benchmark v1.12.0 - Control 1.4.1
Profile Applicability
- Level: 1 - Master Node
Description
Disable profiling, if not needed.
Rationale
Profiling allows for the identification of specific performance bottlenecks. It generates a significant amount of program data that could potentially be exploited to uncover system and program details. If you are not experiencing any bottlenecks and do not need the profiler for troubleshooting purposes, it is recommended to turn it off to reduce the potential attack surface.
Impact
Profiling information would not be available.
Audit Procedure
Run the following command on the Control Plane node:
ps -ef | grep kube-scheduler
Verify that the --profiling argument is set to false.
Remediation
Edit the Scheduler pod specification file /etc/kubernetes/manifests/kube-scheduler.yaml file on the Control Plane node and set the below parameter.
--profiling=false
Default Value
By default, profiling is enabled.
References
- https://kubernetes.io/docs/admin/kube-scheduler/
- https://github.com/kubernetes/community/blob/master/contributors/devel/profiling.md
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software | |||
| v7 | 9.2 Ensure Only Approved Ports, Protocols and Services Are Running |
Profile
Level 1 - Master Node (Automated)