Skip to main content

Patching Virtual Infrastructure smartly



BlueLane folks are getting lots of raving reviews for their hardwork and dedication towards providing a smarter and intelligent patching system.

Perhaps IT's least-favorite necessary evil, security patches are disruptive, time-consuming, and risky. They arrive unannounced or on the vendor's timetable, with no respect for your own well-considered change management processes. And like any change, they need testing before deployment. Even if testing goes smoothly, there's always a chance they'll introduce some new problem or other. Thus the need for security is pitted against another datacenter imperative: system availability.

The founders of Blue Lane had a better idea: implement security patches in a network appliance that fronts the servers, and every server could be protected against software vulnerabilities without having to make changes to the servers themselves. IT could install the actual patches later, on its own timetable.


Read the rest of the article.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more