2025-05-01 –, Transformation
We’ve all seen WHAT to do to secure your containers, but WHY? What’s the worst that could happen?
There is plenty of advice about things to do when building and deploying containers to make sure we are secure. But why do we need to do them? How important are some of these “best” practices? Can someone take over my entire system because I missed one step? What is the worst that could happen, really?
Join Gene as we explore some of the bad things that can happen when we take shortcuts with securing our containers. We’ll look at some common security recommendations but focus more on the impact of not securing containers properly. We’ll exploit these lapses and discover how to detect them. Nothing reinforces good practices more than seeing what not to do and why.
If you’ve ever wondered how vital those container recommendations are, this is where you can find out.
Gene Gotimer is a DevSecOps Engineer with Praeses, LLC, helping to build products for the US Air Force and other government clients. He loves playing with new tools, focusing on agile processes, making development more secure, and automating everything. Gene considers himself a developer but usually focuses on DevSecOps practices such as continuous integration, repeatable builds, unit testing, automated testing, security tools, and automated deployments. He spends a lot of time helping build security and automated infrastructure into build processes, incrementally improving and moving teams towards DevSecOps. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps crucial to software development.