To ensure compliance of your vSphere objects, vRealize Operations Manager includes compliance alerts for VMware vSphere Security Configuration Guide versions. These Security Configuration guide alerts are now based on object type. To meet industry standard regulatory requirements, you can also install management packs.

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

  • ESXi host is violating vSphere Security Configuration Guide

  • vCenter Server is violating vSphere Security Configuration Guide

  • Virtual machine is violating Risk Profile 1 in vSphere Security Configuration Guide

  • Virtual machine is violating Risk Profile 2 in vSphere Security Configuration Guide

  • Virtual machine is violating Risk Profile 3 in vSphere Security Configuration Guide

  • vSphere Distributed Port Group is violating vSphere Security Configuration Guide

  • vSphere Distributed Virtual Switch is violating vSphere Security Configuration Guide

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.

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

To determine whether an alert triggered against vSphere Security Configuration Guide 6.5, 6.0 or 5.5, you must examine the underlying symptoms. For example, for the alert named ESXi Host is violating vSphere Security Configuration 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 Security Configuration Guide)

  • DCUI service is running (vSphere Security Configuration Guide)

When you customize a policy to enable the HIPAA Hardening Guide alerts, you can enable vSphere alerts for the following object types:

  • ESXi host is violating HIPAA Hardening Guide for vSphere

  • vCenter is violating HIPAA Hardening Guide for vSphere

  • Virtual Machine is violating HIPAA Hardening Guide for vSphere

  • vSphere Distributed Port Group is violating HIPAA Hardening Guide for vSphere

  • vSphere Distributed Virtual Switch is violating HIPAA Hardening Guide for vSphere

When you customize a policy to enable the PCI DSS Hardening Guide alerts, you can enable vSphere alerts for the following object types:

  • ESXi host is violating PCI DSS 3.2 Hardening Guide for vSphere

  • vCenter is violating PCI DSS 3.2 Hardening Guide for vSphere

  • Virtual Machine is violating PCI DSS 3.2 Hardening Guide for vSphere

  • vSphere Distributed Port Group is violating PCI DSS 3.2 Hardening Guide for vSphere

  • vSphere Distributed Virtual Switch is violating PCI DSS 3.2 Hardening Guide for vSphere

When you customize a policy to enable the DISA Hardening Guide for vSphere alerts, you can enable vSphere alerts for the following object types:

  • vCenter is violating DISA Hardening Guide for vSphere

  • vSphere Distributed Port Group is violating DISA Hardening Guide for vSphere

  • vSphere Distributed Virtual Switch is violating DISA Hardening Guide for vSphere

  • ESXi Host is violating DISA Hardening Guide for vSphere

  • Virtual Machine is violating DISA Hardening Guide for vSphere

When you customize a policy to enable the CIS Hardening Guide for vSphere alerts, you can enable vSphere alerts for the following object types:

  • Virtual Machine is violating CIS Hardening Guide for vSphere

  • ESXi Host is violating CIS Hardening Guide for vSphere

When you customize a policy to enable the FISMA Hardening Guide for vSphere alerts, you can enable vSphere alerts for the following object types:

  • vSphere Distributed Virtual Switch is violating FISMA Hardening Guide for vSphere

  • Virtual Machine is violating FISMA Hardening Guide for vSphere

  • vSphere Distributed Port Group is violating FISMA Hardening Guide for vSphere

  • ESXi Host is violating FISMA Hardening Guide for vSphere

  • vCenter is violating FISMA Hardening Guide for vSphere

When you customize a policy to enable the ISO Hardening Guide for vSphere alerts, you can enable vSphere alerts for the following object types:

  • vCenter is violating ISO Hardening Guide for vSphere

  • Virtual Machine is violating ISO Hardening Guide for vSphere

  • ESXi Host is violating ISO Hardening Guide for vSphere

  • vSphere Distributed Port Group is violating ISO Hardening Guide for vSphere

  • vSphere Distributed Virtual Switch is violating ISO Hardening Guide for vSphere

Reset Default Content to Ensure Current Compliance Standards for vSphere Objects

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

When the configured policy is applied to objects, it becomes active. When the configured symptom definitions become true for your vCenter Server instances, hosts, virtual machines, distributed port groups, and distributed switches, vRealize Operations Manager generates compliance related alerts. vRealize Operations Manager displays score cards in the vSphere Compliance page and Compliance tab in the object page.

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.