Cloud

11/14/2018
04:00 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Security Teams Struggle with Container Security Strategy

Fewer than 30% of firms have more than a basic container security plan in place.

A study out today shows that the security community is still coming to grips with the new realities introduced by containerization to aid DevOps and agile development teams in their mission for faster deployments in the enterprise.

Some experts say the rise of containers offers an opportunity for security teams to embed themselves more thoroughly in the continuous delivery workflow. But according to "The State of Container Security" report from StackRox, about seven in 10 organizations today either don't have a container security strategy or are at the most rudimentary stages of establishing that strategy. Among those with an existing strategy, about 35% say it doesn't invest enough to adequately secure containers, and 25% say it isn't detailed enough. 

Digging into the details of where IT professionals believe the biggest risks lie in the use of containers, misconfigurations led the pack by far, above vulnerabilities and attacks. This is not surprising given high-profile breaches like the Tesla cryptomining attack that was disclosed earlier this year, which was made possible by a poorly configured Kubernetes deployment on AWS.

Interestingly, even though the survey shows that most organizations are not yet running containers in production, securing containers in runtime has IT pros more worried than in build or deployment phases.

The concern for runtime is logical given the heavy emphasis that early container strategies have put on pre-production vulnerability scanning, according to Mark Bouchard, vice president of research for analyst firm CyberEdge, who provided analysis for the report.

"That's where their early investments have been, and now their apps are going into production and they realize, 'Yes, I've got to continue to do vulnerability scanning, but the bad guys operate not just against software flaws but on any weaknesses they can find,'" he says "So they recognize they need to do some monitoring of the container environment in runtime to look for that malicious activity."

Ultimately, Bouchard says, containers aren't necessarily any different than any other asset enterprises must protect. 

"We're not talking about reinventing security," he says, explaining that all the basic principles, such as the rule of least privilege, threat monitoring, and vulnerability scanning, all still apply. However, security professionals need to adjust to a couple of new variables that container environments introduced. First and foremost is the speed at which security teams need to work to protect constantly changing container environments. 

"What we're doing with microservices, containers, and DevOps is speeding everything up," Bouchard says. "So we're talking about applying the same security principles on a much faster cycle."

Secondly, he explains that security people need to familiarize themselves better with the architecture and with how containers, nodes, registries, orchestrators, and the like really work.

"Unless you understand what it is you are trying to protect, how can you do a good job protecting it?" Bouchard says. As he explains, many security practitioners came up from the network security world, and application delivery can sometimes be a challenge to wrap their arms around, but it is crucial.

"We're shifting the issue now onto the workload, and that's true for application security in general and most definitely for this world of microservices and containers," Bouchard adds.

Related Content:

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Higher Education: 15 Books to Help Cybersecurity Pros Be Better
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
'PowerSnitch' Hacks Androids via Power Banks
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/8/2018
How Well Is Your Organization Investing Its Cybersecurity Dollars?
Jack Jones, Chairman, FAIR Institute,  12/11/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20136
PUBLISHED: 2018-12-13
XSS exists in FUEL CMS 1.4.3 via the Header or Body in the Layout Variables during new-page creation, as demonstrated by the pages/edit/1?lang=english URI.
CVE-2018-20137
PUBLISHED: 2018-12-13
XSS exists in FUEL CMS 1.4.3 via the Page title, Meta description, or Meta keywords during page data management, as demonstrated by the pages/edit/1?lang=english URI.
CVE-2018-20138
PUBLISHED: 2018-12-13
PHP Scripts Mall Entrepreneur B2B Script 3.0.6 allows Stored XSS via Account Settings fields such as FirstName and LastName, a similar issue to CVE-2018-14541.
CVE-2018-1817
PUBLISHED: 2018-12-13
IBM Security Guardium 10 and 10.5 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 150021.
CVE-2018-1818
PUBLISHED: 2018-12-13
IBM Security Guardium 10 and 10.5 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. IBM X-Force ID: 150022.