Streaming connections should have timeouts enabled

Documentos > Datadog Security > OOTB Rules > Streaming connections should have timeouts enabled

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

Timeouts on streaming connections should not be disabled. Setting idle timeouts ensures that you are protected against denial-of-service attacks, inactive connections, and running out of ephemeral ports.

Note: By default, --streaming-connection-idle-timeout is set to four hours, which might be too high for your environment. Setting this to the appropriate time would ensure that such streaming connections are timed out after serving legitimate use cases.

Remediation

If using a Kubelet config file, edit the file to set streamingConnectionIdleTimeout to a value other than 0.
If using command line arguments, edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node and set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.

--streaming-connection-idle-timeout=5m

Restart the kubelet service.