now the last element here in this logical section, making sure that our virtual machines are secured.
Um, again, Cloud service providers. Responsibility, Right. They provide us with the hyper visor, the virtual machine. All we're really leasing from them is a virtual machine. We set up that virtual machine, we create our network. From that point forward, we talked about the difference between
ah, hyper visors, type one and two. And like we said, our cloud service providers are gonna be riding running type one hyper visors. They're more secure.
Ah, One consideration is a cave iam, a kernel based VM, and that's actually a function with insert versions of Lennox. You know, a Olynyk system is obviously, uh, scaled back. It's obviously more secure than
other operating systems,
So not all other operating systems. But what I'm saying is this would be a good solution for a hyper visor in the various. You know, in certain situations, they're tamper warnings, so that gives me some security in case there's a modification.
There's locked down on the firmware circuit board can't be modified. So if you look through these,
you know, really, what we're looking for is a secure system a secure hyper visor because once that hyper visor is compromised, there's nothing you can do from that point. So in many instances, a K V M iss used for the device itself that's providing the hyper visor
in the virtual ization.