I work as a developer in a security heavy finanical services company. As a group we are finding that our Windows 7 workstation security policy is preventing us from performing our jobs. We do not have local administrative rights on our workstations and can only install/use software from an Advertised Program distribution list. This security policy cannot be changed and it was made clear that exceptions are being made for nobody.
I am trying to make a case for allowing developers to use VirtualBox on local VM's. I am sure that they will have a problem a virtual machine that is not Host Only or Internal meaning we couldn't access our various environments in our internal network. Outside internet access isn't necessary from the VM. They are going to state this is insecure because malware could be installed on a local VM that then infects the corporate network.
Since I am preparing for negotiation:
What I REALLY Want
We currently have a VPN token that we can use Cisco Connect on our fully insecure home computer to VPN into the corporate network on a somewhat RESTRICTED subnet. If we could set a Bridged Network connection from our local VM to this VPN network adapter and ONLY THIS VPN NETWORK ADAPTER then I feel this might be an adequate solution. Our local VM could not be any less secure than a home computer. The standard corporate network however I would like the option for this to be disabled or unavailable to VirtualBox at install time. Is this possible and if so then how?
Here is what I will settle for
If I can set up a Host Only network in VirtualBox, then is it possible for us to set up reverse port forwarding such that Guest OS can reach specific internal corporate network resources with Host being a proxy? Is this possible in VirtualBox alone or would this need an additional proxy to be setup?
Furthermore, can VirtualBox be installed with NAT and Bridge networking disabled so that only Host and Internal network adapters can be created?
I appreciate any insight into how this can be achieved.