In the last few years, more responsibilities have shifted to development teams. With the widespread adoption of Kubernetes, configurations become a developer issue first and foremost. This responsibility means that developers need to be aware of the security risks involved in their configurations. Just by themselves, those configuration security risks might not be so harmful, but with other vulnerable components in the production environment, like the libraries used in the application, or a malicious container, potential attackers can build a multi-steps attack vector, using all of these risks together. Developers should give the necessary attention to those risks and make sure that our applications and clusters are as secure as possible. In this hands-on presentation, you’ll see a demonstration on some of the key security issues that affect your Kubernetes configuration. You’ll hear what they actually mean, what an attacker can do to your cluster and howto fix them.
Author Name: DevSecCon
Author Description:
DevSecCon is the global community dedicated to DevSecOps to help implement security in the overall development process. If you’re a security enthusiast & you want to learn more about how to better secure your team, then check out our community & resources.