USM Anywhere™

VMware vCenter

When you configure VMware vCenter to send log data to USM Anywhere, you can use the VMware vCenter plugin to translate raw log data into normalized events for analysis. The table below provides some basic information for the plugin:

Plugin Information
Device Details
Vendor VMware
Device Type Virtual machine management
Connection Type Syslog

Integrating VMware vCenter

To configure VMware vCenter to send log data to USM Anywhere

  1. Follow the VMware vSphere documentation to configure log forwarding in the vCenter Server Appliance Management Interface.

    Note: The link above provides instructions for vCenter 6.7. Please search the vendor documentation if you are using a different version.

  2. Enter the IP address of the USM Anywhere Sensor as the destination host.
  3. Select the Protocol and Port to use.

    USM Anywhere listens for syslog at UDP port 514, TCP port 601, or TLS/TCP port 6514.

    If using TLS+TCP, you need to download the certificate from USM Anywhere or upload your own certificate to USM Anywhere. For instructions, see Configure Syslog on Your Data Sources.

Plugin Enablement

For plugin enablement information, see Adding AlienApps to an Asset.

Available Plugin Fields

The following plugin fields are important attributes extracted from the syslog message. The USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.

  • access_control_outcome
  • customfield_0
  • destination_address
  • destination_hostname
  • destination_ntdomain
  • destination_port
  • event_name
  • event_outcome
  • event_severity
  • file_path
  • rep_device_inbound_interface
  • rep_device_mac
  • session
  • source_address
  • source_hostname
  • source_port
  • source_process
  • source_process_commandline
  • source_userid
  • source_username
  • timestamp_occured
  • timestamp_received
  • transport_protocol

Additional Resources and Troubleshooting

For troubleshooting, refer to the vendor documentation: