--profiling argument is set to false (Scheduler)
Incident Management is now generally available! Incident Management is now generally available!
<  Back to rules search

--profiling argument is set to false (Scheduler)

kubernetes

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.4.1

Set up the kubernetes integration.

Overview

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.

Remediation

Edit the Scheduler pod specification file /etc/kubernetes/manifests/kube-scheduler.yaml file on the master node and set the below parameter:

--profiling=false

Impact

Profiling information would not be available.

Default Value

By default, profiling is enabled.

References

  1. https://kubernetes.io/docs/admin/kube-scheduler/
  2. 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