Streaming connections should have timeouts enabled and not be disabled

문서 > Datadog 보안 > OOTB Rules > Streaming connections should have timeouts enabled and not be disabled

Classification:

compliance

Framework:

cis-kubernetes

Control:

4.2.5

Set up the kubernetes integration.

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Description

Do not disable timeouts on streaming connections.

Rationale

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 as appropriate would additionally ensure that such streaming connections are timed out after serving legitimate use cases.

Audit

Run the following command on each node: ps -ef | grep kubelet. Verify that the --streaming-connection-idle-timeout argument is not set to 0. If the argument is not present, and there is a Kubelet config file specified by --config, check that it does not set streamingConnectionIdleTimeout to 0.

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

Based on your system, restart the kubelet service. For example: systemctl daemon-reload systemctl restart kubelet.service

Impact

Long-lived connections could be interrupted.

Default value

By default, --streaming-connection-idle-timeout is set to four hours.

References

CIS controls

Version 6.9 Limitation and Control of Network Ports, Protocols, and Services