Console
    Start free

    Collect Trellix DLP (formerly McAfee DLP) logs

    Supported in:

    This document explains how to ingest Trellix DLP (formerly known as McAfee DLP) logs to Google Security Operations using Bindplane.

    Trellix DLP is a data loss prevention solution that monitors, detects, and prevents unauthorized transmission of sensitive data across endpoints, networks, and cloud environments. It is managed through Trellix ePO (ePolicy Orchestrator), which provides centralized policy management, event monitoring, and reporting for DLP incidents.

    Before you begin

    Make sure you have the following prerequisites:

    • A Google SecOps instance.
    • A Windows 2016 or later or Linux host with systemd.
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
    • Privileged access to the Trellix ePO (ePolicy Orchestrator) console.
    • Trellix DLP policies configured and generating events in ePO.

    Get Google SecOps ingestion authentication file

    1. Sign in to the Google SecOps console.
    2. Go to SIEM Settings > Collection Agents.
    3. Download the Ingestion Authentication File.
      • Save the file securely on the system where Bindplane will be installed.

    Get Google SecOps customer ID

    1. Sign in to the Google SecOps console.
    2. Go to SIEM Settings > Profile.
    3. Copy and save the Customer IDfrom the Organization Detailssection.

    Install the Bindplane agent

    Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

    Windows installation

    1. Open the Command Promptor PowerShellas an administrator.

    2. Run the following command:

        msiexec 
  
 / 
 i 
  
 "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" 
  
 / 
 quiet

    Linux installation

    1. Open a terminal with root or sudo privileges.

    2. Run the following command:

       sudo  
sh  
-c  
 " 
 $( 
curl  
-fsSlL  
https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh ) 
 " 
  
install_unix.sh

    Additional installation resources

    For additional installation options, consult this installation guide .

    Configure the Bindplane agent to ingest Syslog and send to Google SecOps

    1. Access the configuration file:

      • Locate the config.yaml file. Typically, it's in the /observiq-otel-collector/ directory on Linux or in the installation directory on Windows.
      • Open the file using a text editor (for example, nano , vi , or Notepad).

    2. Edit the config.yaml file as follows:

        ``` 
 yaml 
 receivers 
 : 
  
 tcplog 
 : 
  
 listen_address 
 : 
  
 "0.0.0.0:514" 
 exporters 
 : 
  
 chronicle 
 / 
 chronicle_w_labels 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 ' 
 / 
 path 
 / 
 to 
 / 
 ingestion 
 - 
 authentication 
 - 
 file 
 . 
 json 
 ' 
  
 customer_id 
 : 
  
 ' 
< customer_id 
> ' 
  
 endpoint 
 : 
  
 malachiteingestion 
 - 
 pa 
 . 
 googleapis 
 . 
 com 
  
 log_type 
 : 
  
 MCAFEE_DLP 
  
 raw_log_field 
 : 
  
 body 
  
 ingestion_labels 
 : 
 service 
 : 
  
 pipelines 
 : 
  
 logs 
 / 
 source0__chronicle_w_labels 
 - 
 0 
 : 
  
 receivers 
 : 
  
 - 
  
 tcplog 
  
 exporters 
 : 
  
 - 
  
 chronicle 
 / 
 chronicle_w_labels 
 ```
    • Replace the port and IP address as required in your infrastructure.
    • Replace <customer_id> with the actual Customer ID.
    • Update /path/to/ingestion-authentication-file.json to the file path where the authentication file was saved in the Get Google SecOps ingestion authentication filestep.

    Restart the Bindplane agent to apply the changes

    To restart the Bindplane agent in Linux:

    1. Run the following command:

       sudo  
systemctl  
restart  
observiq-otel-collector

    2. Verify the service is running:

       sudo  
systemctl  
status  
observiq-otel-collector

    3. Check logs for errors:

       sudo  
journalctl  
-u  
observiq-otel-collector  
-f

    To restart the Bindplane agent in Windows:

    1. Choose one of the following options:

      • Command Prompt or PowerShell as administrator:
       net stop observiq-otel-collector && net start observiq-otel-collector
      • Services console:
        1. Press Win+R , type services.msc , and press Enter.
        2. Locate observIQ OpenTelemetry Collector.
        3. Right-click and select Restart.

    2. Verify the service is running:

       sc query observiq-otel-collector

    3. Check logs for errors:

        type 
  
 "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

    Configure Trellix DLP syslog forwarding

    Syslog forwarding for Trellix DLP is configured through the Trellix ePO (ePolicy Orchestrator) console by registering a syslog server.

    1. Sign in to the Trellix ePOconsole.
    2. Go to Menu > Configuration > Registered Servers.
    3. Click New Server.
    4. In the Server typedropdown, select Syslog.
    5. In the Namefield, enter a descriptive name (for example, Chronicle-Bindplane ).
    6. Click Next.
    7. Provide the following configuration details:
      • Syslog Server: Enter the IP address of the Bindplane agent host.
      • Port: Enter 514 .
      • Protocol: Select TCP.
      • Event format: Select Common Event Format (CEF).
    8. Click Test Connectionto verify connectivity to the Bindplane agent.
    9. Click Saveto save the registered syslog server.

    Enable DLP event forwarding

    1. Go to Menu > Automation > Automatic Responses.
    2. Click New Responseto create a new automatic response rule.
    3. In the Namefield, enter a descriptive name (for example, DLP Syslog Forwarding ).
    4. In the Event Groupdropdown, select DLP Events.
    5. In the Event Typedropdown, select DLP Incident Events.
    6. Click Next.
    7. In the Filterstab, configure filters as needed or leave defaults to forward all DLP events.
    8. Click Next.
    9. In the Actionstab, click Add Action.
    10. In the Action typedropdown, select Send Syslog.
    11. In the Syslog Serverdropdown, select the registered syslog server ( Chronicle-Bindplane ).
    12. Click Next.

    13. Review the summary and click Save.

    UDM mapping table

    Log Field UDM Mapping Logic
    additional_field_0
    		additional.fields Merged
    additional_field_1
    		additional.fields Merged
    additional_field_2
    		additional.fields Merged
    additional_field_3
    		additional.fields Merged
    additional_field_4
    		additional.fields Merged
    additional_field_5
    		additional.fields Merged
    additional_field_6
    		additional.fields Merged
    expected_act
    		additional.fields Merged
    res_id
    		additional.fields Merged
    status_label
    		additional.fields Merged
    local_date
    		metadata.event_timestamp Parsed as yyyy-MM-d HH:mm:ss
    has_principal
    		metadata.event_type Mapped: true → STATUS_UPDATE
    has_principal_user
    		metadata.event_type Mapped: true → USER_UNCATEGORIZED
    inc_type
    		metadata.event_type Mapped: "10000","10001","10002","40101","40400","40500","40700" → SCAN_NETWORK , 40102 ...
    inc_type
    		metadata.product_event_type Directly mapped
    inc_id
    		metadata.product_log_id Directly mapped
    agent_ver
    		metadata.product_version Directly mapped
    device_name
    		principal.asset.hostname Directly mapped
    ip_address
    		principal.asset.ip Merged
    device_name
    		principal.hostname Directly mapped
    status_id
    		principal.investigation.status Mapped: "1","2" → NEW , "3","4" → CLOSED , "5","6" → REVIEWED
    ip_address
    		principal.ip Merged
    group_label
    		principal.user.attribute.labels Merged
    user_ou
    		principal.user.group_identifiers Mapped: ^.{0,255}$ → user_ou
    name
    		principal.user.user_display_name Directly mapped
    user
    		principal.user.userid Directly mapped
    sec_action
    		security_result.action Merged
    action
    		security_result.action_details Directly mapped
    fail_reason
    		security_result.description Mapped: 0 → No Failure
    encryption_label
    		security_result.detection_fields Merged
    usb_label
    		security_result.detection_fields Merged
    volume_label
    		security_result.detection_fields Merged
    rule_set_label
    		security_result.rule_labels Merged
    rule_name
    		security_result.rule_name Directly mapped
    sev
    		security_result.severity Mapped values (5 total, for example 1 → INFORMATIONAL , 2 → ERROR , 3 → LOW )
    sev
    		security_result.severity_details Directly mapped
    dst_app
    		target.application Directly mapped
    dst
    		target.asset.hostname Directly mapped
    file
    		target.file.full_path Directly mapped
    file_size
    		target.file.size Renamed/mapped
    dst
    		target.hostname Directly mapped
    process_name
    		target.process.file.full_path Directly mapped
    dst_url
    		target.url Directly mapped
    dst
    		target.user.userid Directly mapped
    N/A
    		 metadata.event_type Constant: SCAN_NETWORK
    N/A
    		 metadata.product_name Constant: Mcafee DLP
    N/A
    		 metadata.vendor_name Constant: Mcafee
    N/A
    		 principal.investigation.status Constant: NEW
    N/A
    		 security_result.description Constant: No Failure
    N/A
    		 security_result.severity Constant: INFORMATIONAL

    Change Log

    View the Change Log for this parser

    Need more help? Get answers from Community members and Google SecOps professionals.

    Design a Mobile Site
    View Site in Mobile | Classic
    Share by: