Security for virtualizing DMZ servers on your internal production hardware and storage

If we wanted to run our DMZ servers on our internal production hypervisors and storage (iscsi) does that cause any security concerns? I haven’t really heard of anyone hacking their way from one virtual machine to dom0 or to another virtual machine on that hypervisor. Is that a best practice or do most shops have separate physical storage and hardware for their DMZ virtual servers? If this is an acceptable practice are their additional things we should do to ensure it is secured?
LVL 1
wburgiss5805Asked:
Who is Participating?
 
Danny McDanielConnect With a Mentor Clinical Systems AnalystCommented:
I've been looking for documentation that takes a stand on storage sharing between DMZ and internal hosts but haven't found anything.  We use FC and if you have separate LUN's for the DMZ, I don't think it should be a concern with proper zoning but my management wants it in black & white.

here's a thread discussing same host concerns and it has contributions from Ed Haletky who wrote a book on the subject of vSphere security http://communities.vmware.com/message/1701309
0
 
d3ath5tarCommented:
Sharing equipment for DMZ/LAN kind of negates the point of a LAN. We run seperate DMZ/LAN virtual environments.

It must be possible to hack out from one VM to another via the hypervisor otherwise VMWare wouldn't have had to introduce a virtual firewall between VMs (on certain editions.....)
0
 
Svet PaperovConnect With a Mentor IT ManagerCommented:
I don’t see any concerns with running a DMZ VM on an internal hypervisor as long as the DMZ VM uses separated NIC to connect directly to the DMZ network. It is not a good security practice to mix DMZ and internal network traffic on the same media, even on VLANs. However, I am not aware of a way to hack a hypervisor from a virtual machine.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
We use many different types of storage, FC, iSCSI and NFS, all our Virtual hosts use a storage network, using VLANs when using ethernet.

ESX hosts have their own secure VLAN for management which the ESX hosts Management Network is connected to.

DMZ servers have their own DMZ VLAN which all the DMZ servers physical and virtual are connected to.

All servers on the DMZ are behind Cisco-PIX firewalls, and have public IP addresses, and only nominated ports are allowed via the firewalls into the DMZ. Also servers in the DMZ have limited access to each other, depending upon service.

It is extremely unlikely, that "hackers" will be able to reach the host Hypervisor, or Storage Networks from the DMZ.
0
 
kevinhsiehCommented:
If you are a smaller environment, then it is reasonable to use production hosts for DMZ VMs if the VMs use a separate physical NIC dedicated to the DMZ. If you are a high value target, use dedicated equipment and possibly even an air gapped network. I would not me the VM have direct iSCSI access to production storage. FC is probably okay is you know how to zone properly.

Breakout issues from the VM to the host are very rare.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.