The move to break up traditional monolithic systems and adopt microservices in cloud-native architectures like Kubernetes and OpenShift ushers in a brand-new security mandate for DevOps teams. Except, well, maybe it doesn’t. Where once it made sense to deploy a traditional firewall to protect an environment’s perimeter from external threats, the rise of container-based microservices necessitates also defending micro-perimeters within the containerized environment. Doing so calls for a new security model congruent with how containerized applications are developed, deployed, and run in production, in order to implement effective safeguards across the critical build-ship-run lifecycle. Plus, cat references! DevOpsCon attendees will learn:

• Why the new hotness of infrastructure-as-code compromised age-old assumptions about underlying security. 
• When to trust your “what’s old is new again” feeling in your gut. Yes, maybe you’ve seen this before.
• How true peace can be attained among Security, Ops and Dev teams. No, really. Pizza for all!
• The place where vulnerability scanning fits in but, more importantly, where it falls short.
• It’s too late to stop the ever-morphing data center that is growing inside your data center. The winner of the shadow-IT wars might not be who your thought it was.