Infrastructure as Code (IaC) makes deploying cloud or container configurations scalable and faster. If you are launching a microservice into a Kubernetes cluster, or even building an entire AWS virtual infrastructure, IaC can automate the deployment. By building repeatable templates you can also ensure that deployments happen exactly as you design, every time.

However, errors in infrastructure configuration are now regarded as the second biggest cause of data breaches. There are many ways to give adversaries an advantage through security misconfigurations. Overly permissive storage volumes, unauthenticated database access, or ports left open to the internet have all been a cause of compromise.

The solution? Treat your infrastructure code the same as your application code. During your build process, use tools to scan for infrastructure misconfigurations. When you find them raise alerts or even break the build.

While there are a few tools for a specific IaC platfrom, in practice DevOps use a variety of IaC platfroms. Our approach to this is to be able to handle all of your IaC platforms from one tool and save you multiple scans.

In this session, we will discuss common types of IaC misconfiguration (general and platform specific) and demonstrate how using KICS open-source security tool can help you avoid them.