Scheduler profiling should be disabled
Set up the kubernetes integration.
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.
Audit
Run the following command on the master node:
ps -ef | grep kube-scheduler
Verify that the --profiling argument is set to false.
Edit the Scheduler pod specification file /etc/kubernetes/manifests/kube-scheduler.yaml file on the master node and set the below parameter:
Impact
Profiling information would not be available.
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
Version 6 14 Controlled Access Based on the Need to Know Controlled Access Based on the Need to Know Version 7 4 Controlled Use of Administrative Privileges Controlled Use of Administrative Privileges
