lystn

A lot of organizations these days are moving to creating and working with cloud-native applications. If your organization is one of them, then you are most likely working with Kubernetes. Kubernetes, after all, is the de facto standard for building containerized applications around the world. In fact, according to a recent CNCF report, 96% of organizations are either already using Kubernetes or evaluating the prospect of using Kubernetes to build and manage their applications. Kubernetes has over 5.6 million users spread all over the globe, which when you look objectively, you realize represents 31% of back-end developers. 31% may not sound too huge, but remember it is 31% of developers using one single platform – that is huge. The remaining 69% is divided between so many different platforms. Now, that is a significant market share. Moreover, this figure grows year-over-year, pushing up the amount of data that Kubernetes generates as well, in turn helping improve the platform.Kubernetes security mistakesDefault ConfigurationsMultiple AdminsUnrestricted AccessAssuming IsolationVulnerable Imported YAMLsKeeping Sensitive Information in ConfigMapsSkipping Regular ScansAll these things are such simple, easy things to do, which is also probably why it gets skipped maybe? But not everything should have complex solutions and elaborate mechanisms. Sometimes, simple does the trick just fine, isn’t it? So is Kubernetes security. Ensure you don’t make these mistakes and you are already on your way to enhancing the security of your clusters. With that, we come to the end of this week’s episode of the Cognixia podcast. We hope you enjoyed listening to us today.