Docker, Twistlock, CoreOS, and the state of container security

Cryptographic hardware keys, inspecting for flawed software, and end-to-end trust add up to secure containers

When Docker turned container technology into a commodity, one question immediately sprung up: "What can we do with them?" With that query out of the way, a much larger one looms: "How do we keep them secure?"

After that inquiry, a horde of others follow. What does "secure" mean in this context? Are you securing access to the container or checking to make sure what's inside it is valid? What do you do about software already inside a container that might be riddled with security issues?

Copyright © 2015 IDG Communications, Inc.

How to choose a low-code development platform