Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: VMware ESX |
|---|---|
| Date: | Mon, 21 Apr 2008 23:49:30 -0400 |
Greetings, My Advice could be to *NOT* do this... This depends, somewhat, on the version of ESX you are running... ESXi is 32MB and presents a much smaller attack surface that ESX. I would never advise implementing ESX itself on both the internal network and the DMZ, but I can't say for sure about implementing ESXi... However keep this Microsoft Advisory in mind -- http://www.microsoft.com/technet/security/Bulletin/MS07-049.mspx It is VirtualPC and VirtualServer but think about that.. Admin access to any single guest, gives you access to all other guests and the host... Who knows if that exists for VMWare and just hasn't been stumbled across yet. Tyler. On Mon, Apr 21, 2008 at 6:54 PM, TVB NOC <tvbnoc@temeculavalleybank.com> wrote:
Actually, I used to work at a company that did it... Because the VMware instances are not aware of each other inside the host, its not a bad solution.. However, if I were going to implement it, I would not do VLANs and Trunking (tagging) between the virtual switch and the physical switch. I would add an additional quad card or other physical network card and physically separate the VM host, plugging each isolated VMhost network connection them directly into the physical switch... Hope this helps... sorry for the grammatical errors too... On Mon, Apr 21, 2008 at 5:23 AM, Paul Heywood <Paul.Heywood@unitypartnership.com> wrote:Hi forum, we've got a VMware ESX group of servers running on the inside of ournetwork. Our server team want to extend this to include some DMZ servers. How vulnerable would this leave the internal network ? Am I correct in thinking that if the VMware cluster was hacked, this would give them access to the internal network**********************************************************************The information in this e-mail is confidential and may be legallyprivileged.It is intended solely for the addressee. Access to this email byanyone elseis unauthorised. If you have received it in error, please notify usimmediatelyby replying to this e-mail and then delete it from your system. This note confirms that this email message has been swept for thepresence ofcomputer viruses, however we advise that in keeping with good ITpractice therecipient should ensure that the e-mail together with any attachmentsare virusfree by running a virus scan themselves. We cannot accept anyresponsibility forany damage or loss caused by software viruses. The Unity Partnership Ltd, registered in England at West Hall, ParvisRoad, West Byfleet, Surrey UK KT14 6EZ.Registered No : 5916336. VAT No : 903761336.**********************************************************************-- "Dear God, save us from the people who believe in you." -- post-9/11 graffiti
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Tutorial on Wireless packet sniffing, Murda Mcloud |
|---|---|
| Next by Date: | Re: Firewall for Windows Server 2003, Khoh Chih Jeun |
| Previous by Thread: | RE: VMware ESX, TVB NOC |
| Next by Thread: | RE: VMware ESX, TVB NOC |
| Indexes: | [Date] [Thread] [Top] [All Lists] |