To ensure compliance of your vSphere 6.0 and 5.5 objects, vRealize Operations Manager includes compliance alerts for VMware vSphere Hardening Guide versions 6.0 and 5.5. These hardening guide alerts are now based on object type.

When you customize a policy to enable the vSphere Hardening Guide alerts, you can enable vSphere 6.0 and 5.5 alerts for the following object types and versions:

ESXi host is violating vSphere Hardening Guide (5.5 and 6.0)

vCenter Server is violating vSphere Hardening Guide (6.0)

Virtual machine is violating Risk Profile 1 in vSphere Hardening Guide (5.5 and 6.0)

Virtual machine is violating Risk Profile 2 in vSphere Hardening Guide (5.5 and 6.0)

Virtual machine is violating Risk Profile 3 in vSphere Hardening Guide (5.5 and 6.0)

vSphere Distributed Port Group is violating vSphere Hardening Guide (6.0)

vSphere Distributed Virtual Switch is violating vSphere Hardening Guide (6.0)

By default, the alert named Virtual machine is violating Risk Profile 1 is the only active alert among the risk profiles. You can configure this profile later, and choose one of the other risk profiles.

To determine whether an alert triggered against vSphere Hardening Guide 6.0 or 5.5, you must examine the underlying symptoms. For example, for the alert named ESXi Host is violating vSphere Hardening Guide, the following underlying symptoms for the alert include:

ESXi.set-account-lockout - The count failed login attempts before the account is locked out exceeded maximum (vSphere Hardening Guide 6.0)

DCUI service is running (vSphere Hardening Guide 5.5)

You can find the vSphere Hardening Guides at http://www.vmware.com/security/hardening-guides.html.

Alert definitions and symptom definitions now include the compliance standards for both vSphere 6.0 and 5.5. When you upgrade your current version of vRealize Operations Manager, you must select the option to overwrite alert definitions and symptom definitions.

If you do not overwrite your alert definitions and symptom definitions with the new content provided with this release, some compliance rules will include the new alert and symptom definitions, while other compliance rules will continue to use outdated alert and symptom definitions.