Skip to main content

Economist: Use virtualization to dodge security issues

A better idea is to adopt something called virtualisation—a technique that’s been around for ages, but has only lately come back into fashion. Virtualisation provides a way of hiding a computer’s resources—its central processor, operating system, internal memory, network controller, and storage devices—behind a software curtain. The idea is to give users (not to mention nefarious strangers) the impression they have control of the machine, when really they are dealing with a simulacrum created entirely in software.

The technique was invented by IBM back in the 1960s, when software was relatively cheap and hardware incredibly expensive. By using virtualisation, one costly mainframe could be partitioned so as to run many different applications all at the same time—each within its own “virtual machine” in a layer of software running on top of the physical machine’s actual operating system.

With modern hardware so cheap, Intel-based servers that dish out applications and data have proliferated like rabbits. In most cases, only 10% to 15% of their resources are actually used. VMware, a company based in Palo Alto, California, was founded in the late 1990s to capitalise on this waste of resources. Helping companies get the most out of their hardware has made VMware one of the fastest growing software firms in decades.


Link

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