USM Anywhere™

FireEye MPS

When you configure FireEye MPS integration to send log data to USM Anywhere, you can use the FireEye MPS plugin to translate the raw log data into normalized events for analysis.

Device Details
Device vendor FireEye
Device type Malware protection system
Connection type syslog
Vendor link

Integrating FireEye MPS

To configure FireEye MPS to send log data to USM Anywhere

  1. Log in to FireEye as administrator.
  2. Go to Settings > Notifications.
  3. Select rsyslog, then select Event Type.
  4. Next to the Add rsyslog Server button, type AlienVault.
  5. Click Add the Rsyslog Server.
  6. In the Rsyslog Server Listing dialog box, type the IP address of the USM Anywhere Sensor in the IP Address field.
  7. Make sure that the other settings display the following:

    • Format — Default (CEF)
    • Delivery — Per event
    • Send as — Alert
    • Protocol — UDP or TCP.

      If using UDP for Protocol, you will also need to apply the special 4096 max chunk size.

Plugin Enablement

The FireEye MPS plugin automatically processes all messages whose syslog tag matches the value "\\|FireEye\\|eMPS\\|".

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.

  • destination_address
  • destination_mac
  • destination_port
  • event_description_url
  • event_name
  • event_receipt_time
  • event_severity
  • external_id
  • file_hash
  • rep_device_address
  • rep_device_hostname
  • rep_device_rule_id
  • rep_device_type
  • rep_device_vendor
  • rep_device_version
  • request_url
  • source_address
  • source_hostname
  • source_mac
  • source_port
  • suppressed
  • timestamp_occured
  • timestamp_received
  • transport_protocol
  • customfield_0
  • customfield_2
  • customfield_3
  • customfield_4
  • customfield_5
  • customheader_0
  • customheader_2
  • customheader_3
  • customheader_4
  • customheader_5
  • device_custom_number_1
  • device_custom_number_1_label
  • device_custom_number_3
  • device_custom_number_3_label


For troubleshooting, refer to the vendor documentation: