{"id":9712,"date":"2019-12-13T07:00:17","date_gmt":"2019-12-13T15:00:17","guid":{"rendered":"http:\/\/formtek.com\/blog\/?p=9712"},"modified":"2019-10-21T11:45:48","modified_gmt":"2019-10-21T19:45:48","slug":"containers-and-security-complexity-makes-it-easy-to-overlook-problems","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/containers-and-security-complexity-makes-it-easy-to-overlook-problems\/","title":{"rendered":"Containers and Security: Complexity Makes it Easy to Overlook Problems"},"content":{"rendered":"\n

Is container security a problem? Not really. But the nature of containers mean that container security needs to be done carefully and early in an implementation.<\/p>\n\n\n\n

Container and non-container security issues that arise are actually not so different. For example, one of the biggest problems in both types of environments is simply ignoring security, like keeping default security permissions.<\/p>\n\n\n\n

But the complexity of automated environments that use containers mean that if security of the underlying components aren’t properly configured, they can cause problem that are harder to find and much harder to correct later.<\/p>\n\n\n\n

Amir Jerbi<\/a>, co-founder and CTO of Aqua Security, told InformationWeek<\/a> that “vulnerabilities in container images — running containers with too many privileges, not properly hardening hosts that run containers, not configuring Kubernetes in a secure way — any of these, if not addressed adequately, can put applications at risk.” <\/p>\n\n\n\n

Richard Henderson<\/a>, head of global threat intelligence for Lastline, said that <\/a>“containers, while a boon to many developers and IT organizations, are just as susceptible to bugs and vulnerabilities as any other technology tool or platform. Keeping that in mind, it means we have to keep our eyes open for threats targeting the underlying products we’re using and make patching a critical imperative. Attackers waste no time exploiting issues that are disclosed.”<\/p>\n

\"Digg<\/a><\/div>
\"Reddit<\/a><\/div>
\"Stumble<\/a><\/div>
\"Buzz<\/a><\/div>
\"Vote<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Kick<\/a><\/div>
\"Shout<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Post<\/a><\/div>
\"Google<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"

Is container security a problem? Not really. But the nature of containers mean that container security needs to be done carefully and early in an implementation. Container and non-container security issues that arise are actually not so different. For example,…<\/span><\/p>\n

Read more ›<\/a><\/div>\n

<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[61],"tags":[],"class_list":["post-9712","post","type-post","status-publish","format-standard","hentry","category-containers"],"_links":{"self":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9712","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/comments?post=9712"}],"version-history":[{"count":1,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9712\/revisions"}],"predecessor-version":[{"id":9713,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/9712\/revisions\/9713"}],"wp:attachment":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/media?parent=9712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/categories?post=9712"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/tags?post=9712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}