When you purchase through links on our site, we may earn an affiliate commission.Heres how it works.
This concern is fairly valid it seems.
So, why are organizations struggling with Kubernetes security on this scale?
Global Field CTO at Veeam.
Fail fast
People often describe security as a race.
Containers have been in use for more than a decade.
Containing the chaos
Kubernetes vulnerabilities often come down to misconfiguration during the design and development phase.
The already-mentioned timeline is a factor here, but a lack of K8-specific knowledge is often the key ingredient.
It’s similar to having a flimsy lock on a sports car, with the keys in the ignition.
The other common vulnerability is misconfigured clusters, exposing clusters to the public in some places.
Internet access is another door for attackers to break in through.
If the door didnt exist, it wouldn’t be an issue.
Its just a result of knowledge gaps and fast development timelines.
In time, as developers become more experienced with cloud-native platforms, these issues will become less common.
This makes the need for robust backup and recovery processes even greater.
Cyber resiliency is multi-layered.
Unfortunately, this is another area of Kubernetes where we are seeing a steep learning curve.
This is a problem.
Cloud-native applications require cloud-native backup solutions.
That means when you try and recover the data it can lead to performance issues anddata loss.
If security and recovery are fundamentally flawed, businesses are leaving themselves fully exposed to attacks like ransomware.
This isnt an appeal to avoid or stop using Kubernetes or container-based applications, far from it.
We’ve featured the best IT infrastructure management service.
The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc.
If you are interested in contributing find out more here:https://www.techradar.com/news/submit-your-story-to-techradar-pro
