Skip to main content

Greg Ness: Key to Virtualization kingdom is security!

Just like Applications , as I mentioned in the previous post, security will also change dramatically.

Changes can be Painful for many Security Solutions

In production environments effortless movement and changes of VM states (snapshot, revert, online, offline, VMotion, etc) can generate extreme operational challenges for critical security activities like vulnerability scanning, patching and security. Vulnerability scans, a critical tool for tracking software vulnerabilities, can become obsolete in seconds. Bottom line: The constant change enabled by virtualization can place dynamic demands on the most commonly deployed static security solutions, in even small virtualized production infrastructures.


All the tricks, flips and tools that make software more nimble and powerful will not matter unless the production infrastructure can be effectively secured from attack. Yet many of the leading network security vendors have been caught flat-footed by virtualization. Some are even trying to cram ASIC-driven IPS solutions onto commodity processors, taking up sizable chunks of server/blade processing power and introducing unacceptable levels of latency, in a nonsensical effort to match suspicious virtual server traffic with a growing library of signatures. That game promises to get even more complicated and resource-consuming as hackers shift to mutating attacks.


Taking the challenges a step further into the virtualized data center made up of blade server fabrics: just how many enterprises will be returning to the ASIC security world with bigger boxes, bigger signature libraries and the promise of constant tuning and traffic headaches while the rest of their infrastructure becomes more powerful, more flexible and more efficient?


How many ASIC-driven security players (and their hardware-centric channel partners) are likewise talking a hard look at the pure software model of virtualization (and much lower margins) and seriously contemplating “serving up their children and their channel allies” to deliver a core technology that in its current state is likely unfit for commoditized processing? That’s an Innovators Dilemma that might even make Clay Christensen cringe.
Clay's my hero too, Greg ;-)

Strongly suggest you to read Greg's post.

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