Review the following prerequisites to ensure an efficient setup and configuration of the USM Anywhere Sensor on VMware.
Access to VMware ESXi 5.1 or later
Important: If you are using VMware ESXi 5.1 through 6.0, the VMware vSphere Desktop Client is required for deployment of the USM Anywhere Sensor OVF. You cannot use the VMware vSphere Web Client interface for the Sensor deployment.
If you are using VMware ESX 6.5, you must have build 7388607 or later. Earlier builds have an issue with the OVF tools that will cause the Sensor OVF deployment to fail.
- VMware virtual machine with four cores and 12 GB of reserved memory
- 150 GB of disk space (100 GB data device and 50 GB root device)
- Internet connectivity to the network where you plan to install the VMware sensor
A vSphere or vCenter user account to use for Sensor configuration with an assigned role that has permissions equivalent to the Read Only default role
Note: The Read Only role allows a user limited read access to the system without any other privileges. Credentials with this assigned role allow the deployed USM Anywhere Sensor to collect vCenter/vSphere events and run asset discovery.
Installed VMware Tools for hosts in your vSphere or vCenter environment
With configured vSphere or vCenter credentials, the VMware sensor uses the VMware APIs to run asset discovery. For hosts that do not have VMware Tools installed, the asset does not have an assigned IP address and this can result in the asset being missed from asset discovery or in duplicate assets created during subsequent discoveries. These tools also enable the Sensor to collect more detailed information about the asset.
If DHCPNetwork protocol used to dynamically distribute network configuration parameters, such as IP addresses, for interfaces and services. is not available, a configured static IP for the management interface and local DNS information
Important: AlienVault strongly recommends assigning a static IP 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.
- Port mirroringMethod of network monitoring in which a system passively collects network traffic on the same ports as other network devices. setup for network monitoring (see Configuring VMware ESX Virtual Switches for Port Monitoring)
- Administrative credentials for devices that require configuration to forward logs to the VMware sensor
- Administrative credentials for remote hosts to support authenticated asset scans
- Configuration on firewall or other security device to send UDP or TCP syslog (if it is capable of exporting security logs through UDP or TCP syslog)
- Network topology information to run asset discovery
- (Optional) Access to a span port to monitor network traffic for IDS
Before you deploy a USM Anywhere Sensor, you must configure your firewallVirtual or physical device designed to defend against unauthorized access to data, resources, or a private network. A firewall’s primary purpose is to create segregation between two or more network resources, blocking undesirable traffic between them. permissions to enable the required connectivity for the new Sensor.
Note: Initial deployment of a USM Anywhere Sensor requires that you open egress/outbound ports and protocols in the firewall for communication with USM Anywhere and AlienVault cloud resources. After the initial sensor setup, you do not need to open any external inbound ports because the USM Anywhere Sensor receives no inbound connections from outside the firewall.
Communication from the Sensor to the USM Anywhere environment, and from AlienVault for initial setup of the Sensor
Important: Both ingress and egress are required for the initial setup of the Sensor. After the Sensor is connected, you can close all ingress for this port.
|TCP||443||update.alienvault.cloud||Communication with AlienVault for initial setup and future updates of the Sensor|
|TCP||443||reputation.alienvault.com||Ongoing communication with Open Threat Exchange®|
|TCP||443||your USM Anywhere subdomain
|Ongoing communication with USM Anywhere|
|SSL / TCP||7100||your USM Anywhere subdomain
|Ongoing communication with USM Anywhere|
|Synch with NTP services in the AlienVault cloud|
We also recommend that you configure outbound connectivity for port 22 and 443 to prod-usm-saas-tractorbeam.alienvault.cloud to support SSHProgram to securely log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another through SCP. communications with the USM Anywhere Remote Support server. For more information about remote technical support through the USM Anywhere Sensor console, see Troubleshooting and Remote Sensor Support.