AlienVault® USM Anywhere™

Symantec DLP

When you configure Symantec DLP to send log data to USM Anywhere, you can use the Symantec DLP 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 Symantec
Device Type Endpoint Protection
Connection Type Syslog

Integrating Symantec DLP

Before you configure the Symantec DLP integration, you must have the IP Address of the USM Anywhere Sensor.

To configure Symantec DLP to send log data to the USM Anywhere Sensor

  1. Locate and open the config\ file. This file is located in the \SymantecDLP\Protect\config directory on Windows machines and the /opt/SymantecDLP/Protect/config directory on Linux machines.
  2. Uncomment the line and specify the USM Anywhere Sensor IP address, that is:

  3. Uncomment the systemevent.syslog.port= line and specify 514 as the port to accept connections from the Symantec Enforce Server, that is:


  4. Uncomment the systemevent.syslog.format= [{0}] {1} - {2} line and specify the system event message format to be sent to the USM Anywhere Sensor.

    Wthout any changes, the notification messages are sent in the format:

    [server name] summary - details

    The format variables referenced in the syslog format line are the following:

    {0} - the name of the server on which the event occurred

    {1} - the event summary

    {2} - the event detail

  5. After making all the changes necessary, save and close the properties file.

Plugin Enablement

The Symantec DLP plugin automatically processes all messages when the raw message contains "Symantec|DLP".

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.

  • application_protocol
  • base_event_count
  • customfield_0
  • customfield_1
  • customfield_2
  • customfield_3
  • customfield_4
  • customfield_5
  • customfield_6
  • customfield_7
  • customheader_0
  • customheader_1
  • customheader_2
  • customheader_3
  • customheader_4
  • customheader_5
  • customheader_6
  • customheader_7
  • destination_service_name
  • event_description_url
  • event_severity
  • file_name
  • file_owner
  • file_path
  • incident_id
  • request_url
  • rep_device_hostname
  • rep_device_rule_id
  • source_user_email

Additional Resources and Troubleshooting

For troubleshooting, refer to the vendor documentation: