Skip to main content

VMware loses another high profile executive; Security Chief Nand to run openDNS

The head of VMware's security group has left to join San Francisco's OpenDNS, a startup that provides Internet infrastructure services.

Nand Mulchandani took over as CEO of the DNS (domain name system) service provider on Nov. 5, replacing founder David Ulevitch, who will remain as the company's chief technology officer, according to a company spokeswoman.

Mulchandani is the latest VMware executive to depart after company co-founder and CEO Diane Green was ousted in July of this year. In September another VMware co-founder, Chief Scientist Mendel Rosenblum, resigned. Richard Sarwal, who led the company's research and development efforts, also left around the same time.

Mulchandani had been with VMware just over a year, after the virtualization software vendor acquired his security company, Determina. As VMware's senior director for security products, Mulchandani was in charge of VMware's security strategy, considered critical to the company's future success. VMware is publicly traded, but the majority of the company is owned by storage vendor EMC.



Security

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