Controller Manager profiling should be disabled

Docs > Datadog Security > OOTB Rules > Controller Manager profiling should be disabled

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.3.2

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-controller-manager

Verify that the --profiling argument is set to false.

Remediation

Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml 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

CIS controls

Version 6.14 Controlled Access Based on the Need to Know

Version 7.4 Controlled Use of Administrative Privileges