Let's Be Blunt: It’s Time to End the Add on Insanity

For the third time in a week, researchers have discovered a zero-day vulnerability in Adobe’s Flash Player browser plugin. Like the previous two discoveries, this one came to light only after hackers dumped online huge troves of documents stolen from Hacking Team — an Italian security firm that sells software exploits to governments around the world.

This quote is from Brian Krebs, who very rightfully goes on to advise that everyone “please consider removing or at least hobbling this program.” Now, that is fine for the most part. I mean, who really needs Adobe Flash these days? Don’t most services we use have other methods of handing us the content we need want? The Apple iPhone doesn’t have Adobe Flash, so why do we need it on our laptops?

The fact is, that most end users probably don’t need to have Adobe Flash installed any more, but a lot of us sysadmins do. Why? Well, in my world one major culprit is the VMware vSphere Web Client. The Web Client has gotten it’s fair share of ill-repute over the last few years, but the latest edition in vSphere 6 is pretty responsive and quite pleasant to use. That’s until you contemplate that it still needs Adobe Flash installed on the client. The same goes for any other admin interface that requires Adobe Flash, or even Java for that matter.

Any administrative interface that requires a browser add on to work, should be bagged, kidnapped and flung in the back of a van and driven off somewhere never to be seen again. Sure, I understand that it’s no easy task to rework all of these interfaces, and it takes real effort by skilled people. But please, please make it happen as soon as possible, and retrofit it it into your existing systems – don’t keep those stuck on older releases hanging, and only provide a solution for the latest and greatest version.

While we as admins and consultants are used to having to patch our systems, and keep current, please help us limiting our own attack surface by removing requirements for add ons and “special juice” just to be able to administer the solutions we depend upon to keep our businesses running. That can’t be too much to ask, can it?

Installing and running VMware Compliance Checker for vSphere

The first version of the new VMware Compliance Checker for vSphere tool is now available for download.

VMware Compliance Checker for vSphere lets you scan your ESX and ESXi hosts for compliance with the VMware vSphere hardening guidelines to make sure your hosts are properly configured. It also lets you save and print your assessment results, so you can track your compliance level over time, or use them as documentation for internal audits.

Installing VMware Compliance Checker for vSphere

After downloading the VMwareComplianceCheckerForvSphere.msi installing is done in a matter of seconds, using the all to familiar click Next to continue Windows installation routine. The tool is Windows only at this point.


The tool is Java based, so the client machine you run it on needs to have it installed locally before you can use it.

Running a Compliance Scan

Running a compliance scan is very easy. Start up VMware Compliance Checker for vSphere and point it towards either a ESX/ESXi host, or towards your vCenter installation.

The tool runs for a while, and in the end you’ll be presented with a nice HTML based report highlighting all your compliance shortcomings!

Impressions/Conclusion

VMware Compliance Checker for vSphere looks like it can be a valuable tool to add to your vAdmin tool-belt. In it’s first version it does a good job of identifying potential issues with your environment. As far as I can see, William Lam’s Perl based vSphere Security Hardening Report Script does more extensive checks for now.

The vSphere Security Hardening Report Script also has a couple of other advantages, one being that it’s operating system agnostic (since it’s Perl based) another advantage is that since it’s written in a scripting language you can set up automated cron jobs that performs the scanning for you. As far as I can see the VMware tool is missing the ability to schedule scans, which is something I really hope VMware will add to it in the not to distant future.