The Controller Manager profiling should be disabled

Documentos > Datadog Security > OOTB Rules > The Controller Manager profiling should be disabled

Set up the kubernetes integration.

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Description

Controller manager profiling should be disabled if not required. Profiling allows for the identification of specific performance bottlenecks, and 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.

Remediation

Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml on the master node and set the following parameter:

--profiling=false