Speaker: Stefania Chaplin

One of the advantages of microservices architecture is that teams can develop, maintain, and deploy each microservice independently. With single-responsibility, services can be scaled separately as required and doing so with a DevOps mentality substantially improves agility. 

How do we secure microservices and their deployments? Who owns what? Do we know what is in our microservices? Preventing vulnerability traversal is a must. Systems must be designed securely, and security as an afterthought does not scale. Platform engineers and SREs need to quickly identify owners and fix deployment vulnerabilities from inception to production. If log4j taught us anything, teams must have ownership, accountability and the power to make changes fast to keep their systems secure.

In this session, we’ll be looking at OWASP recommendations and Kubernetes best practices to find out more about how to secure your microservices and reduce vulnerability traversal.