So when we do look at the hyper visor
I just mentioned there. Two types of hyper visors. Definitely testable. Um,
ultimately, the idea is hyper visor may feel the same to end. Users really will feel the same, right? You're not going to know it's a type one or type two, but it's really important from an administrative standpoint,
So the first type of hyper visor is a type one.
Your cloud service providers are gonna be running type one hyper visors, sometimes called bare metal. So if you look at S X, I feel like it's in server financial here, um called hardware based. And the idea is the sit directly on top of the hardware,
right? You don't have an operating system between
the hyper visor and the hardware that hyper visor directly interfaces, and you can use that to create your own separate virtual systems. Whereas what a lot of end users have seen virtual virtual PC, or perhaps being workstation, where
you install the software on top of windows or on top of some sort of client based operating system.
And within your operating system, you can access virtual machines
again. That's for client based usage and a lot of times clients, you know, end users. They're not even using that. So absolutely Type one hyper Fizer is what your cloud service providers will be using. It's more secure, their less moving pieces.
I don't wanna have to filter commands from the operating system to the hyper visor to the hardware.
I don't want that layer of operating system that has its own vulnerabilities, right? So definitely our preference in any sort of environment. A network environment of any degree of security is going to be that type one. So much smaller attack surface. That's the phrase you'll hear with Type one
There is much more control over the direct interface with hardware because it's not going through an operating system. I hope that makes sense. You know, anything you install in the U. S. Has the vulnerabilities off the operating system of the OS, and that's a type to so much larger tax space.
Lots of vulnerabilities. It's easier to get
at the hyper visor when it's installed as a separate entity on top of an operating system, okay, and some of the threats that we have to think about in relation to hyper. Uh, no, no, no, no,
Done with hyper visor.
Sorry. Kind of screwed that up. This next piece
Pausing to start the last slide
and then, um, this slide off. Do you have a minute review?