Monitor vSphere for ransomware vulnerabilities
Check your vSphere environment against VMware's security configuration guides and get SCOM alerts for risks.
Applies to: OpsLogix VMware Management Pack (all versions) with the VMware Ransomware Vulnerability Monitoring add-on · SCOM 2019, 2022, 2025 · vSphere 7.0, 8.0, 9.0
Last updated: October 2026 · Reading time: 3 minutes
Goal
Find out whether your vSphere environment is vulnerable to attacks such as ransomware. The VMware Ransomware Vulnerability Monitoring add-on runs on top of your existing VMware monitoring. It turns most compliance checks from VMware's Security Configuration Guides for vSphere into SCOM monitors. When a check isn't compliant, you get a SCOM alert. The knowledge of the monitor, shown in Health Explorer and in the alert details, explains how to fix it, usually with a PowerCLI command.
There's a separate Security Configuration Guide, and a separate management pack, for each vSphere version. The installation package contains management packs for vSphere 7.0 (V70), 8.0 (V80) and 9.0 (V90). The V90 management pack is based on the VMware Cloud Foundation 9.0 security controls. See the vSphere Security Configuration Guide and the VCF 9.0 Security Configuration and Hardening Guide in the Broadcom documentation.
Prerequisites
- The VMware Management Pack is installed and monitoring your environment.
- The VMware Management Pack installation package.
Steps
- In the installation package, open the Management Packs\Ransomware Vulnerability Monitoring folder.
- Import the management pack that matches the version of your vCenter Server. The collector chooses the set of checks by the vCenter version of the connection, not by the ESXi version of each host.
- Optional: to get detailed compliance checks for virtual machines, also import the group management pack for your version (for example OpsLogix.IMP.VMWare.RansomwareVulnerability.MonitoringV70.Groups). This creates a group called VMware V70 VMs with Full Ransomware Vulnerability Check Enabled (the name depends on the version), and enables the virtual machine checks for the members of that group.
- vSphere 7.0: add the virtual machines you want to check to this group.
- vSphere 8.0 and 9.0: the group management packs for these versions are sealed, so you can't change the group membership in the Operations Console. Instead, create your own group with the virtual machines you want to check, save it in an unsealed management pack, and override the virtual machine monitors of the V80 or V90 management pack with Enabled = True for that group.
What gets monitored
- Monitors are added to VMware ESX Server, VMware Virtual Machine and VMware Distributed Virtual Switch objects, under the Security rollup category.
- All compliance monitors for ESXi servers and distributed virtual switches are enabled by default.
- The detailed monitors for virtual machines are disabled by default. They're enabled for the VMs you selected in step 3.
- Each target has an overall monitor, enabled by default, that shows the status of all compliance checks.
- The monitoring interval is 6 hours. If you change it, change it for all monitors. Otherwise you break the cookdown and increase the load on SCOM.
Mixed vCenter versions: if you monitor vCenter servers of more than one version, for example 8.0 and 9.0, import the management packs for both. A management pack only runs its checks for connections with its own vCenter version, but its overall monitor still shows a state for every host, virtual machine and switch. That can cause duplicate overall monitors and alerts.
For the full list of checks per version, see Security checks in the Ransomware Vulnerability Management Packs.
Verify it worked
Open Health Explorer for an ESXi host and expand the Security category. You should see the ransomware vulnerability monitors and their overall monitor.
See also
- Choose which VMware MP files to import
- Security checks in the Ransomware Vulnerability Management Packs
- Install VMware PowerCLI on Windows Server
- Rules and monitors