 Hello, and welcome back to the manager risk across the extended attack surface with Armist. I'm John Furrier, host of theCUBE. Got the demo God here, Brian Inman, sales engineer at Armist. Brian, thanks for coming on. We're looking forward to the demo. How are you doing? I'm doing well, John, thanks for having me. You know, we heard from Nadir, you know, describing Armist's platform, a lot of intelligence. It's like a search engine meets data at scale, intelligent platform around laying out the asset map, if you will, the new vulnerability module, among other things that really solves CISO's problems. A lot of great customer testimonials. And we got the demo here that you're going to give us. What's the demo about? What are we going to see? Well, John, thanks, great question. And truthfully, I think as Nadir has pointed out, what Armist as a baseline has given you is great visibility into every asset that's communicating within your environment. And from there, what we've done is we've layered on known vulnerabilities associated with not just the device, but also what else is on the device? What's, is there certain applications running on that device, the versions of those applications, and what are the vulnerabilities known with that? So that's really gives you great visibility in terms of the devices that folks aren't necessarily have visibility into now. Unmanaged devices, IOT devices, OT and critical infrastructure, medical devices, things that you're not necessarily able to actively stand or put an agent on. So not only is Armist telling you about these devices, but we're also layering on those vulnerabilities all passively and in real time. A lot of great feedback we've heard. I've talked to you, some of your customers. The agent list is a huge deal. The discovery's at awesome. You can see everything and just getting real time information. It's really, really cool. So I'm looking forward to the demo for our guests. Take us on that tour. Let's go with the demo for the guests today. All right, sounds good. So what we're looking at here within the Armist console is just a clean representation of the passive reporting of what Armist has discovered. So we see a lot of different types of devices from your virtual machines and personal computers, things that are relatively easy to manage, but working our way down, you're able to see a lot of different types of devices that are not necessarily easy to get visibility into. Things like your up systems, IP cameras, dash cams, et cetera, lighting systems. And today's day and age where everything is moving to that smart feature, it's great to have that visibility into what's communicating on my network and being able to layer on the risk factors associated with it as well as the vulnerabilities. So let's pivot over to our vulnerabilities tab and talk about the AVM portion, the asset vulnerability management. So what we're looking at is the dashboard where we're reporting another clean representation with customizable dashlets. They gives you visuals and reporting and things like new vulnerabilities as they come in. One of the most critical vulnerabilities that are the newest as they roll in, the vulnerabilities by type. We have hardware, we have application, we have operating systems. As we scroll down, we can see things to break it down by vulnerabilities by the operating system, Windows, Linux, et cetera. We can take, create dashlets that show you views of the number of devices that are impacted by these CDEs. And scrolling down, we can see, you know, how long have these vulnerabilities been sitting within my environment? So how, what are the oldest vulnerabilities we have here? And then also of course, vulnerabilities by applications. So things like Google Chrome, Microsoft Office. So we're able to give a good representation of the amount of vulnerabilities as they're associated to the hardware and applications as well. So we're going to dig in and take a deeper look at one of these vulnerabilities here. So I'm excited to talk today about where ARMS AVM is, but also where it's going as well. So we're not just reporting on things like the CVSS score from NIST NVD. We're also able to report on things like the exploitability of that, right? How, how actively is this, this CVE being exploited in the wild, right? We're reporting EPSS scores, for example, we're able to take open source information as well as a lot of our partnerships that we have with other vendors that are giving us a lot of great value of known vulnerabilities associated with the applications and with hardware, et cetera. But where we're going with this is we're in very near future releases. We're going to be able to take sort of an algorithm approach of what are the most critical CVSSs that we see? How exploitable are those? What are common threat actors doing with these, these CVEs? Have they weaponized these CVEs? Are they actively using those weaponized tools to exploit these within other folks' environments and who's reporting on these? So we're going to take all of these and then really add that armist flavor of we already know what that device is and we can explain and so can the users of it the business criticality of that device, right? So we're able to pivot over to the matches as we see the CVEs, we're able to very cleanly view what exactly are the devices that the CVE resides on, right? And as you can see, we're giving you more than just an IP address or more, you know, a lot more context and we're able to click in and dive into what exactly are these devices? And more importantly, how critical are these devices to my environment? If one of these devices were to go down, if it were to be a server, you know, whatever it may be, I would want to focus on those particular devices and ensuring that that CVE, especially if it's an exploitable CVE, were to be addressed earlier than say the others and really be able to manage and prioritize these. Another great feature about it is, you know, for example, we're looking at a particular CVE in terms of it's patch and build number from Windows 10. So the auto result feature that we have, for example, we've passively detected what this particular personal computer is running Windows 10 and the build and revision numbers on it. And then once Armist passively discovers an update to that firmware and patch level, we can automatically resolve that, giving you confidence that that has been addressed from that particular device. We're also able to customize and look through and potentially select a few of these, say, you know, these particular devices reside on your guest network or an employee Wi-Fi network where we don't necessarily, I don't want to say care, but we don't necessarily value that as much as something, you know, internally that holds significantly more business criticality. So we can select some of these and potentially ignore or resolve for determining reasons, as you see here. I'd be able to really, truly manage and prioritize these CVEs. As I scroll up, I can pivot over to the remediation tab and open up each one of these. So what this is doing is essentially, Armist says, you know, through our knowledge base, been able to work with the vendors and pull down the patches associated with these. And within the remediation portion, we're able to view, for example, if we were to pull down the patch from this particular vendor and apply it to these 60 devices that you see here, right? Now we're able to view, you know, which patches are going to give me the most impact as I prioritize these and take care of these affected devices. And lastly, as I pivot back over, again, where we're at now is we're able to allow the users to customize the organizational priority of this particular CVE to where in terms of, you know, Armist has given us a high CVSS score, but maybe for whatever reasons it may be, maybe the CVE in terms of this particular logical segment of my network, I'm going to give it a low priority for whatever the use case may be. We have compensating controls set in place that render this CVE not impactful to this particular segment of my environment. So we're able to add that organizational priority to that CVE and where we're going, as you can see that popped up here, but where we're going is we're going to start to be able to apply the organizational priority in terms of the actual device level, right? So what we'll see is we'll see a column added to here to where we'll see the business impact of that device based on the importance of that particular segment of your environment or the device type, be it, you know, critical networking device or maybe a critical infrastructure device, PLCs, controllers, et cetera, but really giving you that passive reporting on the CVEs in terms of what the device is within your network. And then finally, we do integrate with your vulnerability management and scanners as well. So if you have a scanner actively scanning these, but potentially they're missing segments of your network or they're not able to actively scan certain devices on your network, that's the power of ARMS being able to come back in and give you that visibility of not only what those devices are for visibility into them, but also what vulnerabilities are associated with those passive devices that aren't being scanned by your network today. So with that, that concludes my demo. So I'll kick it back over to you, John. Awesome, great walk through there. Take me through what you think the most important part of that is the discovery piece is at the interaction. What's your favorite? Honestly, I think my favorite part about that is, you know, in terms of being able to have the visibility into the devices that a lot of folks don't see currently. So those IoT devices, those OT devices, things that you're not able to run a scan on or put an agent on, ARMS is not only giving you visibility into them, but also layering in, as I said before, those vulnerabilities on top of that. That's just visibility that a lot of folks today don't have. So ARMS does a great job of giving you visibility and vulnerabilities and risks associated with those devices. So I have to ask you, when you give this demo to customers and prospects, what's the reaction? Falling out of their chair moment, are they more skeptical? It's almost too good to be true. And to end vulnerability management is a tough nut to crack in terms of solution. Honestly, a lot of clients that we've had, you know, especially within the OT and the medical side, they're blown away because at the end of the day, when we can give them that visibility, as I've said, you know, hey, I didn't even know that those devices resided in that portion, but not only are we showing them what they are and where they are and enrichment on risk factors, et cetera, but then we show them, hey, there's a known, you know, we've worked with that vendor, whatever it may be, and you know, Rockwell, et cetera. And we know that there's vulnerabilities associated with those devices. So they just seem to be blown away by the fact that we can show them so much about those devices from behind one single console. You know, it reminds me of the old days, I'm going to date myself here. Remember the old Google Maps mashup days? This is, customers talk about this as the Google Maps for their assets. And when you have the Google Maps, and you have the Ubers out there, you can look at the trails, you can look at what's happening inside the enterprise. So there's got to be a lot of interest in once you get the assets, what's going on on those networks, or those roads, if you will, because you got in packet movement, you got things happening, you got upgrades, you got changing devices. It's always on kind of living thing. Absolutely. Yeah, it's what's on my network, and more importantly at times, what's on those devices, right? What are the risks associated with the applications running on those? How are those devices communicating? And then as we've seen here, what are the vulnerabilities associated with those and how can I take action with them? All right, real quick, put a plug in for where I can find the demos that online is on YouTube, on the website. Where does someone see this demo? Yeah, the Armist website has a lot of demo content loaded. Get you in touch with folks like, engineers like myself to provide demos whenever needed. All right, Brian, thanks for coming on the show. Appreciate sales engineer Armist, Brian Inman, given the Demo God Award out to him. Good job. Thanks for the demo. Thanks, thanks for having me. Okay, you know, in a moment, we're going to have my closing thoughts on this event and really the impact to business operation side. In a moment, I'm John Furrier of theCUBE. Thanks for watching.