USM Anywhere™

Malwarebytes Breach Remediation

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

Device Details
Device vendor Malwarebytes
Device type Antivirus
Connection type syslog
Vendor link MBBRGuide.pdf at

Malwarebytes Breach Remediation Integration

Before configuring the log collection, you must have the IP address of the USM Anywhere Sensor.

To configure Breach Remediation to forward log data to USM Anywhere

  1. After launching Breach Remediation, edit the following parameters:

    mbbr settings




    • log.enabled:true
    • log.server:IP address of the USM Anywhere Sensor
    • log.port:514
    • More options:

      •<event_name>:on|off: Specifies whether logging is enabled/disabled for each following potential event that may be logged by Malwarebytes Breach Remediation.

        • ScanStartEvent
        • DetectionEvent
        • RestoreEvent
        • CustomDbUpdateEvent
        • ScanEndEvent
        • RemovalEvent
        • RestoreStartEvent
        • DbUpdateEvent
        • RemoveLastScanEvent
        • RestoreEndEvent
      • log.test: Tries to make contact with the syslog server using the provided host and port specifications. Results of the connection attempt display on the screen.

        Note: This command does not generate an event log entry. No additional parameters are required.

Plugin Enablement

The Malwarebytes Breach Remediation plugin automatically processes all messages whose syslog tag matches the value "Malwarebytes|Malwarebytes Breach Remediation|".

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.

  • customfield_0

  • customfield_1

  • customfield_2

  • customfield_3

  • customfield_4

  • customfield_5

  • customheader_0

  • customheader_1

  • customheader_2

  • customheader_3

  • customheader_4

  • customheader_5

  • destination_mac

  • device_custom_number_1

  • device_custom_number_1_label

  • device_event_category

  • event_action

  • event_description

  • event_name

  • event_outcome

  • event_receipt_time

  • event_severity

  • file_hash

  • file_path

  • highlight_fields

  • malware_family

  • plugin_device

  • rep_device_hostname

  • rep_device_rule_id

  • rep_device_type

  • rep_device_vendor

  • rep_device_version

  • session

  • source_process_commandline

  • source_username

  • time_end

  • time_start


For troubleshooting, refer to the vendor documentation: