Docker, Twistlock, CoreOS, and the state of container security
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?
With current container technology moving away from dependency on a single vendor and more toward an open ecosystem -- especially regarding security -- it's unlikely any one solution will deal with these issues. Instead, we're seeing a panoply of answers to the different container security questions.
To read this article in full or to leave a comment, please click here