4.2 Client-side Virtualization Flashcards
Virtualization
- run multiple OS on one computer simultaneously
Sandboxing
- use of virtualization as an isolated testing environment
- try some code, nothing is affected
- roll back to a previous snapshot
Test Development
- develop and test applications in a virtual environment that is very similar to what the production network might be
Legacy Software/OS Virtualization
Used when:
- running different application versions on the same system
- application only runs on a previous OS version
Cross-Platform Virtualization
- running Windows/macOS/Linux simultaneously
- each OS has strengths and weaknesses
- no need to partition hard drive
- no rebooting to switch
Hypervisor
Virtual Machine Manager
- manages the virtual platform and guest OS
- may require a CPU that supports virtualization
- manage the CPU, networking, security, etc
Virtualization Resource Requirements
CPU Processor Support
- Intel: Virtualization Technology (VT)
- AMD: AMD-V
A lot of RAM: above and beyond host OS requirements
Plenty of disk space
Network: make sure each OS has proper network configuration
Virtualization Security Requirements
- VMs should have the same security controls as a physical computer
- host-based firewall, anti-virus
Rogue VMs
- third-party VMs downloaded from the Internet could potentially have malware
- it’s always best to build your own VM for safety
VM Escaping
- malware on a VM gains access to parts of the hypervisor
- malware can then hop to other virtualized systems managed by that hypervisor
Virtualization Network Requirements
- most client-side VMs have their own virtual network
Network Configurations:
Shared Network Address
- the VM shares the same IP address as the physical host
- uses a private IP address internally
Bridged Network Address
- each VM had its own IP address
Private Address
- no communication outside of the virtual network
VM Sprawl
Occurs when the number of VMs on a network reaches the point where administrators can no longer manage them properly
