Collect Trellix EPO logs

This document explains how to ingest Trellix ePO logs to Google Security Operations using the Bindplane agent.

Trellix ePO (formerly McAfee ePolicy Orchestrator) is a centralized security management platform that provides unified policy enforcement, real-time visibility, and automated compliance across endpoint security products. It allows administrators to manage security policies, deploy agents, monitor threats, and generate reports from a single web-based console.

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 console with administrator privileges

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.
4. 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 ID from the Organization Details section.

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 Prompt or PowerShell as 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 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 /etc/bindplane-agent/ 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:

   receivers:
     tcplog:
       # Replace the port and IP address as required
       listen_address: "0.0.0.0:514"
   
   exporters:
     chronicle/chronicle_w_labels:
       compression: gzip
       # Adjust the path to the credentials file you downloaded in Step 1
       creds_file_path: '/path/to/ingestion-authentication-file.json'
       # Replace with your actual customer ID from Step 2
       customer_id: YOUR_CUSTOMER_ID_HERE
       endpoint: malachiteingestion-pa.googleapis.com
       # Add optional ingestion labels for better organization
       log_type: 'MCAFEE_EPO'
       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 YOUR_CUSTOMER_ID_HERE with the actual Customer ID.
   • Update /path/to/ingestion-authentication-file.json to the file path where the authentication file was saved in Step 1.
   • Update the endpoint value to match your tenant's region.

Restart Bindplane Agent to apply the changes

1. To restart the Bindplane agent in Linux, run the following command:

   sudo systemctl restart observiq-otel-collector
   

2. To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

   net stop observiq-otel-collector && net start observiq-otel-collector
   

Configure Trellix ePO syslog forwarding

1. Sign in to the Trellix ePO console with administrator credentials.
2. Go to Menu > Configuration > Registered Servers.
3. Click New Server.
4. In the Server type drop-down list, select Syslog.
5. In the Name field, enter a descriptive name (for example, Chronicle-Bindplane).
6. Click Next.
7. In the Syslog Server field, enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
8. In the Port field, enter 514 (or the port configured in Bindplane).
9. In the Protocol drop-down list, select TCP.
10. In the Event format drop-down list, select Common Event Format (CEF).
11. Click Test Connection to verify connectivity to the Bindplane agent.
12. Click Save.
13. Go to Menu > Automation > Automatic Responses.
14. Click New Response to create a new automatic response rule.
15. In the Name field, enter a descriptive name (for example, Syslog-Chronicle).
16. In the Event Group drop-down list, select the event groups to forward:
    • ePO Notification Events
    • Threat Events
    • Client Events
17. Click Next.
18. In the Filter tab, configure any event filters as needed (or leave defaults to forward all events).
19. Click Next.
20. In the Actions section, select Send Syslog.
21. In the Syslog Server drop-down list, select the registered syslog server (Chronicle-Bindplane).
22. Click Next.

23. Review the configuration and click Save.

UDM mapping table

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