- Microsoft Security Blog warns Kubernetes users on helmet graphics with default settings
- These parameters are often delivered with open ports, low references and other risks
- Microsoft Users of Kubernetes to examine their parameters
Kubernete bar graphics can expose data without users never knowing it, have warned Microsoft Security researchers, urging Kubernetes users to be careful and review the default configuration of their bar graphics.
Kubernetes is an open source platform to automate the deployment, scaling and management of containerized applications. Helm, on the other hand, is a package manager that simplifies the deployment and management of applications on Kubernetes using preconfigured models called graphics.
It allows users to define, install and upgrade the Kubernetes complex applications with a minimum manual configuration.
Default configurations
In a new blog article, entitled “The risk of default configuration: how the barrels of ready -to -use bar can violate your cluster”, the authors Michael Katchinskiy, and Yossi Weizman argued that in many cases, the graphics of bar require no authentication, keep certain open ports and use passwords easy to disguise or take away.
This happens when bar graphics are deployed with default settings, which is often the case with inexperienced cloud users.
“The default configurations lack of appropriate security controls create a threat of severe security,” said the blog. “Without carefully examining the Yaml manifests and bar graphs, organizations can unfold services without knowing it without form of protection, leaving them fully exposed to attackers.”
Katchinskiy and Weizman added that the risk is “particularly worrying” when the applications deployed can question the sensitive API or allow administrative actions. »»
They distinguished three cases where bar graphics put entirely risk of Kubernetes at risk – Pinot Apache, Meshery and Selenium Grid.
The best way to mitigate the risk is to be careful when deploying the bar, not to use default configurations and to assess the configuration of a safety point of view to ensure that it includes authentication and isolation of the network.
In addition, Microsoft recommends users to perform regular analyzes for configuration errors that can expose interfaces to the public and keep a careful eye on containers for unjustified activity.
Via Bleeping Compompute
