Skip to main content

Static Security? It's Virtualized Dynamic Security



Greg talks about the shift! The Shift!

Virtualization promises to clearly demarcate security technologies into two camps: 1) the dynamic and 2) the dead.

Now lets talk about some of the specific challenges that virtualization is bringing to security vendors.

THE NEW HYPERVISOR LAYER REQUIRES NEW SECURITY THINKING

The emergence of the hypervisor looks at this point like the biggest thing in IT since the PC; or the equivalent of the first new operating system in 15 years. By decoupling hardware from the OS it has, in effect, created an entirely new data center OS, an entirely new potential for slicing and dicing processing power into virtual machines that can be created, moved, and erased at the speed of electrons.

One of the more subtle outcomes of the hypervisor layer is that the network is now exposed on the server. This is good news and bad news – good in that it allows a new guard post on the servers, which can provide “zone defense” for the VMs without any footprint on the VMs; bad in that it presents a new target that can be exploited by hackers. It has been said that virtualization is changing everything. Security is obviously no exception.


Interesting read!

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