Kubernetes exposed to the internet

Caute_cautim — Mon, 09 Oct 2023 10:11:30 GMT

HI All

Well we have been talking about it, and now the reality has been realised.

Back to the Shared Responsibility Model from the cloud provider; who responsibility when we know those who do not read the documentation i.e. the client - you must not should place a gateway in front of all public access to your stack. A load balancer is not sufficient, a Web Application Firewall is a good idea, but remember there are many high end ports left open by default by Cloud Providers, which can provide direct insights from the internet directly. So read, read again, and check with the cloud provider and other sources to validate that you are protected or not.

https://www.darkreading.com/application-security/more-than-eight-in-10-kubernetes-api-servers-exposed-to-the-internet?utm_source=dlvr.it&utm_medium=linkedin

Regards

Caute_Cautim

Re: Kubernetes exposed to the internet

AppDefects — Sat, 21 May 2022 14:34:00 GMT

This is a serious call for action. Review your K8S clusters for ingress control now!

topic Re: Kubernetes exposed to the internet in Cloud Security

Kubernetes exposed to the internet

Re: Kubernetes exposed to the internet