With the release of Twistlock 2.1 we bring a highly sought-after feature (at least it was something that I wanted when I was a customer so therefore it *must* be highly sought after!) – Twistlock Collections.
“What are these Collections, Ashley?” I hear you cry.
Well, unlike collections in the office where you have to chip in some money for someone’s leaving card, Collections in Twistlock are a means of logically grouping container-things into groups. Hence, Collections. See? Simple.
Let’s take a little look at putting a collection in place.
Settings –> System –> Collections
By default we have a single Collection called ‘All’ which is pretty self explanatory.
If we add a collection then we can begin to see the power that is available.
Name and Description fields are pretty clear, as is picking the color, but notice that the other fields use that same great regular expression-driven model for selections. We’re using the same language and styles to define our collections as we are our compliance, runtime, access, and vulnerability rules!
Go ahead and pop some rules in there to select some images – the generated drop down selection list is pretty neat isn’t it?
Now that you have at least one collection, and it’s populated, has an appropriate name, description, and color, we can take a deeper look at it. Head on over to the Monitor –> Vulnerabilities page. Take a second to gaze over the lovely headline graphs. Not just because I think they’re pretty but also because we’re going to change the collection and see what happens. OK, taken a good long look? Let’s select the drop down box in the top right.
Drop it down to your collection… and voila! Things have changed. You now have a means of getting all the in-depth information you normally get from Twistlock but tailored to a specific group of _things_ – hosts, images, containers, labels.
Now if we head on over to Monitor –> Compliance, notice that we’ve remembered the collection you were looking at. It’s going to follow you around. But fear not, one glance up to the top right tells you the collections that you are viewing. Go ahead and click to deselect your collection or even select multiple collections.
And we can easily deselect one collection and choose another.
That’s it in a nutshell.
The last point is that we also tell you all the collections that an entity is a member of. Here’s my lab host and you can see it is a member of a number of collections. And we do this for all container entities – hosts, images, registries, containers… In fact, all the container-things!
Collections – a simple and yet really useful feature. Did I mention that you can use it in the API too? I didn’t need to… you already knew that we release proper software that is fully API driven!
Let us know what you think about Twistlock Collections and tell us a little about how you’re using it when you contact us. Also, follow our blog and Twistlock Twitter to get more deep dives, container security news, and cloud-native updates!
Follow us on Twitter
Keep up to date with the latest news from TwistlockLabs and TwistlockTeam.
Serverless Comparison: Lambda vs. Azure vs. GCP vs. OpenWhisk
Serverless computing adoption is growing at exponential rates. As with...
DevSecOps in Practice
If you understand DevOps, you probably also intuitively understand Dev...
Squaring the Circle: Making CI/CD Fast and Secure
Today, most DevOps teams place priorities on software delivery speed a...
Securing Istio with Twistlock
This article is about Istio, a new service mesh management platform th...
Twistlock Releases Serverless Runtime Defense
A few months ago, we wrote a piece on “The Continuum of Cloud Native...