Security as Code: How Repeatable Policy-Driven ... : vimarsa

While the approach has many benefits, traditional security approaches typically slow down the software development life cycle and can evaporate the benefits of using IaC. That s why there is a real need for organizations to take a security as code (SaC) approach to fully recognize the benefits of automation that composable, repeatable, and fully auditable infrastructure can provide.
IaC Requires A New Security Approach
Simply put, securing automation code is critical because in many cases it literally runs our businesses. IaC systems are automatically deploying resources and applications. A vulnerability or a misconfiguration in an IaC workflow could have a cascading impact, across multiple workloads and deployments that could enable a potential attacker to cause a lot of damage. IaC is very powerful, so when mistakes happen, they happen fast, and exponentially.