60% of Organizations Suffered a Container Security Incident in 2018, Finds Study

by Ray Lapena on January 7, 2019

Many organizations have DevOps on their mind going into 2019. This is a global movement. In fact, Puppet and Splunk received responses for their 2018 State of DevOps Report from organizations on every continent except Antarctica. Those organizations varied in their industry, size and level of DevOps maturity, but they were all interested in learning how they could advance their DevOps evolution going forward.

They’ll face challenges along the way. Organizations will confront growing complexity and risk as they work to scale their DevOps initiatives in 2019. Part of this risk will come from their containers, for many organizations still lack transparency into these software pieces. If they are to adequately mitigate their risk and minimize their exposure to digital threats, organizations will need to secure their containers. But are they prepared to do this?

The answer lies in Tripwire’s State of Container Security Report. For its study, Tripwire surveyed 311 IT security professionals who manage environments with containers at companies with over 100 employees.

Their responses illustrated that organizations have already experienced real consequences with respect to securing their container deployments: 60 percent admitted that their organized had been hit with at least one container security incident within the past year.

Eighty-six percent of surveyd organizations had containers in production at the time of the Tripwire’s study; the more containers in production, the more likely it was they experienced a a container security incident… Of those organizations with over 100 containers in production, 75 percent had suffered a security event. It’s therefore no wonder that 94 percent of respondents said they have container security concerns. Seventy-one percent of individuals went so far as to predict that container security incidents would increase in the new year.

94% container