USM Anywhere™

Carbon Black EDR

When you configure Carbon Black EDR (formerly Carbon Black Endpoint Security) integration to send log data to USM Anywhere, you can use the Cb Response plugin to translate the raw log data into normalized events for analysis.

Device Details
Device vendor Carbon Black
Device type Cb Response
Connection type Syslog
Vendor link https://www.carbonblack.com/resources/resource-library/

Carbon Black EDR Integration

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

To send log data from Carbon Black EDR to USM Anywhere

  1. Install and configure the cb-event-forwarder. See the Carbon Black Event Forwarder Quickstart Guide for instructions.
  2. Modify the /etc/cb/integrations/event-forwarder/cb-event-forwarder.conf file, include the following item:

    udpout=<USM-Anywhere-Sensor-IP-Address>:514

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.

  • audit_reason

  • customfield_0

  • customfield_1

  • customheader_0

  • customheader_1

  • destination_address

  • destination_address_6

  • destination_port

  • device_direction

  • device_external_id

  • event_category

  • event_description

  • event_description_url

  • event_name

  • event_severity

  • file_hash

  • file_hash_algorithm

  • file_path

  • rep_device_rule_id

  • reputation_score

  • security_group_name

  • source_address

  • source_address_6

  • source_nat_address

  • source_process

  • source_hostname

  • time_end

  • timestamp_occured

  • time_start

  • transport_protocol

Troubleshooting

For troubleshooting, refer to the vendor documentation:

https://www.carbonblack.com/resources/resource-library/