1.2.17 Ensure that the --insecure-port argument is set to 0

Information

Do not bind to insecure port.

Setting up the apiserver to serve on an insecure port would allow unauthenticated and unencrypted access to your master node. This would allow attackers who could access this port, to easily take control of the cluster.

Solution

None.

Impact:

All components that use the API must connect via the secured port, authenticate themselves, and be authorized to use the API.

This includes:

- kube-controller-manager
- kube-proxy
- kube-scheduler
- kubelets

See Also

https://workbench.cisecurity.org/benchmarks/19464

Item Details

Category: SYSTEM AND SERVICES ACQUISITION

References: 800-53|SA-15, CSCv7|9.4

Plugin: OpenShift

Control ID: 87ca753f0c57243e1b2b9d14b836d7edfd987c81b7d046a68ed0269c2ef8d441