Kubernetes customers battle with safety, Purple Hat survey says

Safety is a major concern for Kubernetes and container-based growth, in accordance with Purple Hat’s State of Kubernetes Safety report for 2022.

In truth, 93% of survey respondents skilled a minimum of one safety incident of their Kubernetes and container environments previously 12 months, typically resulting in the lack of clients or income. This was possible the results of quite a lot of components, together with an absence of safety data about containers and Kubernetes, insufficient instruments, and central safety groups unable to maintain up with software growth groups. Purple Hat additionally notes that Kubernetes and containers have been designed for developer productiveness, not essentially safety.

Printed final month, the report analyzed tendencies in Kubernetes, container, and cloud-native safety. It was primarily based on a survey of greater than 300 devops, engineering, and safety professionals. Purple Hat revealed the next key findings:

• 55% of respondents delayed or slowed down software deployment attributable to safety concern.
• 53% detected a misconfiguration in Kubernetes previously 12 months.
• 57% fear probably the most about securing workloads at runtime.
• 78% have a devsecops initiative both in starting or superior levels.
• 43% take into account devops because the function most accountable for Kubernetes safety.
• 38% have had a serious vulnerability to remediate pertaining to containers and/or Kubernetes within the earlier 12 months.

Organizations adopting containers, Kubernetes, and a cloud-native ecosystems danger the safety of their important functions if they don’t spend money on safety methods and instruments, Purple Hat stated. However devsecops—which builds safety processes and instruments into the devops pipeline—is seeing mass adoption.

Kubernetes is a extremely customizable container orchestrator with numerous configuration choices affecting software safety, in accordance with the report. Safety instruments ought to present the guard rails to configure Kubernetes extra securely. Runtime, specifically, represents the container lifecycle section organizations fear about probably the most. However runtime safety points sometimes are attributable to lapses reminiscent of a misconfiguration on the construct or deploy stage.

Purple Hat made the next suggestions to attain higher safety:

• Use Kubernetes-native safety architectures and controls.
• Safety ought to begin early and prolong throughout the total lifecycle.
• Portability needs to be required throughout hybrid environments.
• Builders needs to be remodeled into safety customers by bridging devops and safety.