C-0151 - Ensure that the Scheduler --profiling argument is set to false

Framework

cis-v1.23-t1.0.1

Severity

Low

Description of the the issue

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.

Related resources

Pod

What does this control test

Disable profiling, if not needed.

How to check it manually

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

Impact Statement

Profiling information would not be available.

Default Value

By default, profiling is enabled.

Example

No example