We are discussing the potential of issuing standardized VM images to our staff to use when connecting to our corporate network from their personal computers.
Ideally they could run this VM on any hardware they have available. Since we wouldn't control the hardware or host OS, there would be the fairly high potential of malware infestations, restricted software, bad software interactions, etc. on the host.
What would be the best/simplest way to allow the VM to connect to our corporate network, while at the same time prevent the host computer from connecting?
The solution should:
- allow the user to connect via wireless or ethernet in our office, or over VPN from outside the office
- prevent the host computer from connecting altogether, although our office provides guest wireless access, which would be acceptable for the host computer.
- not disrupt functionality of corporate computers (not personal computers, not VMs) which are under our control
- not be administratively intensive, such as maintaining whitelists of MAC addresses, etc.
- The VMs will likely either be VMWare or VirtualBox based
- The VMs will run Windows XP or Windows 7
- The hosts could be mac/linux/windows