Container Security Automation: Keeping Up With The DevOps Crowd

This article was originally published in InfoWorld.com, New Tech Forum. 

From development to deployment, one of the most distinctive traits of using containers is speed. The development cycle is not only rapid, but divided into multiple, bite-sized components that are constantly updated. At runtime, frequent updates and sometimes ephemeral workloads make it a challenge to lock down any environment. This scenario perfectly exemplifies why speed has always been the enemy of security, but in container-based development environments, there is a way to nip this problem in the bud: automation, automation, and more automation.

In DevOps environments, automation is par for the course, but traditional security tools and methods were not designed for CI/CD settings, and they are usually ill-suited to address key elements of container security. Simply put, it is not possible to keep up with container image updates, deliver reliable alerts, and detect anomalies if we continue relying on a manual, start-and-stop system.

What needs to be automated? Check out the blog for answers.