Skip to main content

Virtualization: Security concerns are here to stay

Unless ofcourse start considering the security as the "default" option when purchasing Virtualization software for your IT infrastructure. Adoption is getting quicker and don't forget to add security shields as standard installation with every virtualization installation.

Lamb says that his post isn't intended to smear VMware specifically, but rather to point out vulnerabilities in virtualization software in general. Virtualization allows enterprises to convert physical hardware, such as servers and desktop PCs, into software, which can then be consolidated onto a single machine, saving energy and hardware costs. But according to Lamb, that consolidation may also turn a business's IT infrastructure into a larger, more unified target for hackers.

"Instead of 30 discrete servers, now they're all on one physical machine. You could potentially compromise and own the whole system," he says.

In fact, Internet Security Systems released a vulnerability on Wednesday that could potentially be used to compromise several of VMware's products. The bug, found in VMware's Dynamic Host Configuration Protocol, (DHCP) could theoretically be exploited to allow hackers to access and run commands on not just the "guest" desktop PCs in a virtualization set-up, but also the physical server that hosts those machines.


Read on...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op