AlienVault® USM Anywhere™

Sophos UTM

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

Device Details
Device vendor Sophos
Device type UTM
Connection type Syslog

Integrating Sophos UTM

Before you configure the integration, you must have the IP address of the USM Anywhere Sensor.

To configure logging for iView

  1. Log onto the WebAdmin of the UTM.
  2. Navigate to Logging & Reporting > Log Settings > Remote Syslog Server.
  3. Activate the Remote Syslog status.
  4. Configure a syslog server:

    • Name — Freely selectable
    • Server — IP or hostname of your Sophos iView
    • Port — UDP 514
  5. Click Apply.
  6. Log onto Sophos iView and do the following:

    1. Navigate to System > Configuration > Device.

      A new device should appear with the designation "device ID: new."

    2. Provide a name for this device.
    3. Activate the device.
    4. Save your changes

The Sophos UTM should now log everything to your Sophos iView.

Plugin Enablement

For plugin enablement information, see Manual Plugin Management.

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.

  • audit_reason
  • bytes_out
  • content_category
  • customfield_0
  • customfield_5
  • customfield_6
  • customfield_7
  • destination_address
  • destination_mac
  • destination_port
  • device_event_category
  • email_recipient
  • email_sender
  • event_action
  • event_category
  • event_description
  • event_name
  • event_severity
  • event_subcategory
  • http_hostname
  • malware_family
  • rep_device_rule_id
  • request_method
  • request_url
  • request_user_agent
  • response_code
  • source_address
  • source_mac
  • source_ntdomain
  • source_port
  • source_username
  • timestamp_occured
  • timestamp_received
  • transport_protocol


For troubleshooting, refer to the vendor documentation: