Application Security

Container Deployments Bring Security Woes at DevOps Speed

Nearly half of all companies know that they're deploying containers with security flaws, according to a new survey.

Companies are rushing to deploy containers in their application infrastructure — and in that rush, they're deploying containers that they know are insecure. That's one of the conclusions reached in a new report that looks at the state of container security.

The Tripwire State of Container Security Report was conducted in partnership with Dimensional Research. The study finds that companies are unsure about container security, and they're paying a price for that insecurity.

That price is paid in security incidents: 60% of those surveyed say that their organization suffered a container security breach in the last year. Tim Erlin, vice president of product management and strategy at Tripwire, says that he was surprised by that number because there are relatively few reports of container breaches in the news media.

And the security issues don't mean that companies aren't concerned with security. Ninety-four percent of respondents to the survey say that security is one of their significant container concerns. "The first thing they want is how to detect bad things happening; the second is how to prevent those bad things," says Erlin.

Not surprisingly, the level of concern tends to rise with the number of deployed containers. Thirty-four percent of those with fewer than 10 containers describe themselves as "very concerned" about security, while 54% of those with more than 100 containers deployed describe themselves with the same language.

The solution for the container security problem lies in the development cycle, Erlin says. "The way to address container security is to build security controls into the DevOps process. If you're looking for vulnerabilities or mis-compliance, you want to find them in the build ahead of deployment, and you want to make sure the process will allow them to be fixed before deploying," he explains.

Too many companies are using traditional security scanning processes, in which they scan for vulnerabilities when the application is deployed, and then try to fix issues in a DevOps process — and they're finding that it doesn't work, Erlin says. The problem isn't primarily with the tools they're using.

"I don't think this is a technology challenge as much as an adoption challenge. There are tools available today in a variety of quality from a variety of companies, but we haven't seen DevOps organizations adopting them as part of the build process," Erlin says. Looking ahead, though, he sees promise in the form of new employees being hired to work with containers.

"I was talking to an analyst this morning, and he said that companies are seeing new hires bring the container technology with them from their time in colleges and universities," he says. Still, the new hires are no quick fix: 71% of those in the survey say that they expect to see more container security incidents in the coming year.

Related Content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
PaulChau
50%
50%
PaulChau,
User Rank: Apprentice
1/28/2019 | 9:22:56 PM
Bigger things are coming
I would not be surprised if those figures continue to increase in the coming years. People are starting to realise that there is value in targeting information held in storage containers in companies and more importantly in cloud storage spaces. Such easy access for people who are looking for a payout...
EdwardThirlwall
50%
50%
EdwardThirlwall,
User Rank: Apprentice
1/27/2019 | 11:16:32 PM
Put a stop now
It is good that they are aware of their current situation now as opposed to being exposed to the truth only at a much later date when too much damage might have already been done. On their next phase of deploying storage containers, they need to already have an alternative put in motion should they wish to put a stop to this underlying issue.
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7715
PUBLISHED: 2019-03-26
An issue was discovered in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. The main shell handler function uses the value of the environment variable ipcom.shell.greeting as the first argument to printf(). Setting this variable using the sysvar command results in a user-c...
CVE-2019-8981
PUBLISHED: 2019-03-26
tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need_bytes value is mismanaged.
CVE-2019-10061
PUBLISHED: 2019-03-26
utils/find-opencv.js in node-opencv (aka OpenCV bindings for Node.js) prior to 6.1.0 is vulnerable to Command Injection. It does not validate user input allowing attackers to execute arbitrary commands.
CVE-2019-7711
PUBLISHED: 2019-03-26
An issue was discovered in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. The undocumented shell command "prompt" sets the (user controlled) shell's prompt value, which is used as a format string input to printf, resulting in an information leak of memory addre...
CVE-2019-7712
PUBLISHED: 2019-03-26
An issue was discovered in handler_ipcom_shell_pwd in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. When using the pwd command, the current working directory path is used as the first argument to printf() without a proper check. An attacker may thus forge a path contain...