Client Side Virtualization

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

12 hours 9 minutes
Video Transcription
this is less than 12 dot to client side virtualization. This lesson. We're going to jump and dive into virtualization, gonna talk about some key concepts there, and also some things that you need to be aware off and consider when moving into the virtual environment. So let's go and get started.
Virtualization versus ation is one physical machine running multiple operating systems at the same time. Ah, virtual or pseudo machine running on top of the host machine. Basically, all of these machines, the virtual and the hardware machines,
they're independent one another. They have their own operating system. They have their own resource. Is
eso their act as separate machines? The host machine in virtual machines are independent of one another. Each machine has his own operating system, and resource is, But it's only one physical machine that you're dealing with the workstation with other virtual machines on dedicated server or virtual hope machines as well.
So there's different concepts that you can deploy this in,
say first is there's work star workstations that you have multiple virtual machines on that could be an office setting or for testing or a lap or a dedicated server in an enterprise or business can house virtual machines as well. So there's different setups that you can do for virtualization.
The software that's on the host machine and runs and manages those virtual machines is called the Hyper Visor. Another name is the virtual machine manager. The host may have a CPU that supports virtualization Now that hyper visor software or the host machine is gonna manage all the resource is
of all the virtual machines is gonna manage the CPU,
the security and the network so that our host machine has its hands full and it's doing a lot. Not only is it Helling, its own resource is, but it's Helling. The resource is for those virtual machines as well.
Resource requirements, CPU support. There's there's hardware that you can turn on virtualization support right into CPU. And if you're using an intel, AM D. C. P. You. These are the type of key words you need to look for when you're building out of system
for Intel. See, Peale's It's called Virtual Ization Technology, or VT
on a MDs is gonna be a M D. V.
Now, the memory when you're looking at the memory for a host machine or a potential is machine, it must support the host and the virtual machines. You want to take that in consideration. Look at the operating system requirements, and you want to upgrade that ram as much as you can to make sure they can provide.
It ran for itself as well as the virtual machines.
This space. Each virtual machine will have its own image plus storage network. Each guest has its own configuration, where that's gonna be a stand alone and there are private to themselves or can be a net, which is network address, translation or bridged. Whatever the case may be,
the network has to be configured for each of those virtual machines,
and some technologies also allow you to have a virtual switch. This is advanced configurations where you can set up things called V lands right in your virtual environment. And those virtual machines
may talk with just one another, but not the outside world, so it depends on your configuration. But these are the configuration that you can do in the technology that will provide this for you
virtualization and emulation. Now virtualization is running at a virtual operating system that is native to the hardware on your host machine. Now, On the other side of that is emulation. Inflation is a host machine running an op operating system that is completely different architectures
one devices immolating or pretending to be another
original software and code is used, but it's interpreted for another architecture. So because of this interpretation going on, there's gonna be a lot of translation talking from one language to another language. So because of that, you will probably have reduced performance when you're emulating something that's not native to that machine.
Security requirements is something else you need to consider.
Virtualization can be a potential target for Attackers, as critical systems are being moved to virtual ization. The front point is lesson than it would if it was multiple machines. Right now, there's no known vulnerabilities, however you want to be aware of of a fault that were called VM. Escaping
it was safer as value was. Now where was loaded on the host, and it comprises
the hyper viers orbited moves to the guest machines. Many hosted service is virtually virtual environments could be a potential for this. This has since been closed down by patches from vendors, but This is just one example of how having virtual machines on a centralized hosts
could be potential downfall. So that's something that you want to consider
as you're moving into a hosted environment. And again, things have come a long way, and security has come a long way as well. Each guest operating system need to be treated as a real computer. This would kind of help you in your Linus far security. Each machine is a self contained and he's protected, just like you would do any other machine on your network.
Same method supply here
and a virus firewall, etcetera. So again, these are virtual machines, but yet you wanna handle them like they're real physical machines and your protection on your network only install V EMS from a trusted source As you're in deploying your V EMS. You may be getting of Eames from 1/3 party, but only get those from a trusted source because again,
these are
computers running on your system, and there could be any type of rogue software running on that. What's been such problems in your network
network requirements There, somebody of ways that shouldn't configure your V EMS for network Access bridge network access. The VM is the device on the network. It's just like a physical device. It's pulling D A C p from your DCP server, and it's just like another device on the network. There's also shared network access
on the virtual machines. Used the same I P address as the host
uses a private I p address internally and uses net to convert that to the physical host i. P. So that's another way of doing it. Or it could be a private i p address. It doesn't communicate with the outside VM network at all.
So different virtual ization concepts. We talked about the hyper visor in its role and also resource requirements, emulator requirements, security requirements in network warm. It's things you need to be aware of when you're moving to the virtual ization environment. So that is it for this lesson, and we will see you in the next lesson.
Up Next