Skip to main content
Review the following prerequisites to ensure an efficient setup and configuration of a USM Anywhere Sensor on Microsoft Hyper-V.

​
Minimum Requirements

These are the minimum requirements needed to set up and configure a USM Anywhere Sensor on Hyper-V:
  • Operating system (OS) must be Windows Server 2012 R2, 2016, 2019, or 2022.
  • Using Hyper-V Manager or Microsoft System Center Virtual Machine Manager (SCVMM).
  • Dedicated 178 GB of disk space (128 GB data device and 50 GB root device).
  • Dedicated 4 CPUs and 12 GB of statically assigned memory.
  • Internet connectivity from the virtual machine.
Important: Because the needs of a sensor differ based on the varying demands of different deployment environments and the complexity of events being processed, the number of events per second (EPS) a sensor can process varies.Depending on your environment, you may need to deploy additional sensors to ensure that all events are processed.
These are the recommended requirements needed to set up and configure a USM Anywhere Sensor on Hyper-V:
  • If Dynamic Host Configuration Protocol (DHCP) is unavailable, a static IP for the management interface and local Domain Name System (DNS) information
    Important: LevelBlue strongly recommends assigning a static IP address to deploy the USM Anywhere Sensor.If DHCP changes the IP address of the sensor, you must update all the IP addresses on all the devices that are forwarding logs to the sensor through syslog.
  • Network topology information to run asset discovery
  • setup for network monitoring (see Direct Traffic from Your Physical Network to the Hyper-V Sensor for more information)
  • Administrative credentials for remote hosts to support authenticated asset scans
  • Administrative credentials for devices that require configuration to forward logs to the Hyper-V Sensor
  • To access network-based intrusion detection system (NIDS) functionality on the sensor, an ethernet port on the host must be available to receive data from a Switched Port Analyzer (SPAN) or Test Access Point (TAP) port

​
Sensor Ports and Connectivity

Before deploying a USM Anywhere Sensor, you must configure your firewall permissions to enable the required connectivity for the new sensor. Initial deployment of a sensor requires that you open egress and outbound ports and protocols in the firewall for communication with USM Anywhere and LevelBlue Secure Cloud resources. The sensor receives no inbound connections from outside the firewall.
Note: To launch the USM Anywhere Sensor web UI during the initial setup, you need to allow inbound traffic to the sensor IP address through TCP port 80. You can remove access to this port after the sensor successfully connects to USM Anywhere. You do not need to allow inbound traffic to this port from the Internet.
The following tables list the inbound and outbound ports. Sensor Ports and Connectivity (Outbound Ports) Sensor Ports and Connectivity (Inbound Ports)

​
USM Anywhere IP Addresses for Allowlisting

Your sensor is connected to a USM Anywhere instance deployed in one of the Amazon Web Services (AWS) endpoint regions based on your location. If you need to configure your firewall to allow communication between the sensor and the USM Anywhere instance, refer to the following table with the reserved IP address ranges for each region.
Important: The Update Server and the AlienVault Agent always use the 3.235.189.112/28 range no matter where your USM Anywhere is deployed. The LevelBlue TDR for Gov Update Server uses the 3.32.190.224/28 range.
Note: The regional IP ranges listed in this table are limited to the control nodes (subdomain). You must also meet all requirements provided in the Sensor Ports and Connectivity (Outbound Ports) table.
AWS Regions Where USM Anywhere Instance Is Available

​
Hyper-V Machine Deployment

You can deploy a Hyper-V virtual machine (VM) using either of the following management tools:
  • Microsoft Hyper-V Manager, which is an administrative tool for managing local and remote Hyper-V servers. See Create the VM with Hyper-V Manager for more information.
  • System Center Virtual Machine Manager 2012, which is designed for managing large numbers of virtual servers, based on Microsoft Virtual Server and Hyper-V. See Create the VM with SCVMM 2012 for more information.