VMware vSphere Hardening Guide Draft posted for public review
VMware announces the first draft of the vSphere Hardening Guide, posted for public comment. A worthy successor to the current VMware Hardening Guide, it contains over 100 guidelines, split into the following sections:
* Introduction
* Virtual Machines
* Host
* vNetwork
* vCenter
* Console OS (for ESX)
Aside from the versioning difference, this newer version of the guide uses a standardized format, and has severity levels for each security recommendation. The Hardening Guide can certainly be used as-is for production environments today, but we can expect changes over the next while in response to comments to the posted draft. While reviewing the draft, you'll see that most guidelines are worded to be "script friendly", which is very nice to see.
The announcement can be found here ==> http://blogs.vmware.com/security/2010/01/announcing-vsphere-40-hardening-guide-public-draft-release.html
The actual hardening guides can be found here ==> http://communities.vmware.com/community/vmtn/general/security?view=documents
Again, each document has a comments form, the authors are actively seeking constructive comments on these documents before going to a final version.
=============== Rob VandenBrink Metafore =================
e107 CMS system website compromised
The website of e107 CMS system was found to be compromised, directing users to malware site but was fixed within a few hours after the news got posted on Bugtraq mailing list. A notice posted on the website after the clean up points to the delay in patching to the latest released e107 software as the problem, as the latest version released few days ago fixed a security vulnerability.
There were also a zip file containing the e107 package that was backdoored. This file was located on the e107.org instead of Sourceforge which is the normal repository for e107. If you are running e107 (version 0.7.17), you might want to download the latest version from Sourceforge and compare source.
Lessons learned, patch quickly, especially if it is software you wrote and/or the public has access to the source code.
Comments