Blue Pill will take its toll

Now, here's the part that's going to bake your noodle: While it's possible to detect the root-kitting of a normal PC with "hypervisor malware", how on Earth will you detect the Trojaning of a virtual image running on something like a VMWare box?

That's right, a virtualised root-kit affecting a virtualised OS. Try measuring "perturbed timings" then!

I suppose you could bloat up the actual virtualisation layer (like VMWare's hypervisor, for example) with an AV detection engine designed to scan for this sort of stuff, but ye gads, that means running security software at the virtualisation layer to monitor the operating systems that your other security software runs on! It's enough to turn a reasonable person quite insane.

This blogger muses about it here.

Comments

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

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!

Now, here's the part that's going to bake your noodle: While it's possible to detect the root-kitting of a normal PC with "hypervisor malware", how on Earth will you detect the Trojaning of a virtual image running on something like a VMWare box?

That's right, a virtualised root-kit affecting a virtualised OS. Try measuring "perturbed timings" then!

I suppose you could bloat up the actual virtualisation layer (like VMWare's hypervisor, for example) with an AV detection engine designed to scan for this sort of stuff, but ye gads, that means running security software at the virtualisation layer to monitor the operating systems that your other security software runs on! It's enough to turn a reasonable person quite insane.

This blogger muses about it here.

Avastu Blog: Sustainable Global Clouds

Search This Blog