More thoughts on presence: Leveraging Virtualization
All too often, I run into security problems when working remotely for a client. I need to access a network resource, but since I am remote, I must wait until a sysadmin can help me or I find a less than ideal workaround.
This morning, I thought of a workaround:
Basically, I can prepare my own VM image with visual studio and all of my other development toys. I ask the sysadmin of the client's network to host my VM somewhere in his internal network. This way, I can VPN in to the client's network, access the VM via remote-desktop and viola! I have my own computer in their office.
This is a nice for me, because I have as much access as anyone else in the office. It is nice for the client (and the syadmin) because they don't need to loosen any of their security policies on my behalf.
This morning, I thought of a workaround:
Basically, I can prepare my own VM image with visual studio and all of my other development toys. I ask the sysadmin of the client's network to host my VM somewhere in his internal network. This way, I can VPN in to the client's network, access the VM via remote-desktop and viola! I have my own computer in their office.This is a nice for me, because I have as much access as anyone else in the office. It is nice for the client (and the syadmin) because they don't need to loosen any of their security policies on my behalf.
posted by Peter Weissbrod at
5:57 AM
2 Comments:
I don't understand. If you can VPN in, doesn't that give you the same LAN access/security as a VM on the LAN would?
Consider this scenario:
Your VM is a member of the client's active directory domain.
Your Laptop is not.
Post a Comment
<< Home