Twistlock sponsored this demo.
A main part of Twistlock’s 19.03 launch has been about meeting a gap in the need organizations have had for a single security platform that not only covers new cloud native deployments but is also applicable to on-premise and virtual machines (VMs), regardless of the physical environment.
“We’ve really heard a lot of feedback from our customers over the past year telling us that the traditional tools that they’ve been using to protect the VMs that they were running as part of their cloud-native stack we’re typically single-purpose. They ended up with a lot of different tools that often conflicted with each other and they weren’t really modern cloud-native apps themselves,” said John Morello, chief technology officer of Twistlock. “They weren’t programmatically accessible; the data wasn’t easily available via an API and they really liked the approach that we did for containers and asked if we could do those same kinds of things for their traditional VMs as well. And that’s basically been the main focus of this 19.03 release.”
During a demo of 19.03 that Morello gave with that Alex Williams, founder and editor-in-chief of The New Stack, Morello showed how 19.03 works and is applicable for a number of different environments, including, as mentioned above, VMs as well as for cloud native deployments.
Morello began with 19.03 “radar view.” As he noted, the particular radar view, while not particularly exciting, showed only have a single node in this environment. “Typically, you would see for each one of the individual node, you’d see all the connections from the apps that run on it to other applications and be able to see that same kind of topology map that you’ll probably familiar with that we do for containers,” Morello said.
The idea with hosts is “to pivot those not based on the individual node but on the apps that you’re running on that node,” Morello said. “The reason why that makes more sense is the typical way that you’re operating these VMs at scale is you’re operating them with that cattle vs pets mentality,” Morello said. “You know, you’ve got a whole bunch of VMs that are configured more or less identically or very close to identically and so it doesn’t make sense to create this view that’s focused on individual nodes because you don’t care about the nodes, you care about the workloads that they’re running.”
Morello next described and showed how each workload is modeled, the capabilities and information that are provided, and other features “we have in the platform to complete the security story that we have,” Morello said.
At the end of the demo, Morello revisited how the concept behind 19.03 was to “protect against that continual of compute options, including VMs, containers and serverless.”
“That has really driven the product that we built: to give you that singular capability that spends all of those different computer options that are really relevant to the beginning of the lifecycle from development all the way to production and all those different physical environments you might want to run your workloads in,” Morello said.
Feature image via Pixabay.