Collect Symantec Endpoint Protection logs

This document explains how to ingest Symantec Endpoint Protection logs to Google Security Operations using Bindplane. The parser processes logs in SYSLOG or KV format, first extracting timestamps from various formats within the log data. Then, it utilizes a separate configuration file (sep_pt2.include) to perform further parsing and structuring of the log events, ensuring successful processing only if the initial timestamp extraction is successful.

Before you begin

Ensure that you have the following prerequisites:

• Google SecOps instance
• Windows 2016 or later or Linux host with systemd
• If running behind a proxy, firewall ports are open
• Privileged access to the Symantec Endpoint Protection platform

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

Install the Bindplane agent

The following sections describe how to install the Bindplane agent.

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 the 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 /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:
       udplog:
           # 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: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           ingestion_labels:
               log_type: 'CES'
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

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

  sudo systemctl restart bindplane-agent
  

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

  net stop BindPlaneAgent && net start BindPlaneAgent
  

Configure Syslog in Symantec Endpoint Protection

1. Sign in to your Symantec Endpoint Protection Manager web UI.
2. Click the Admin icon.
3. Locate the View Servers section, and click Servers.
4. Click Local Site > Configure External Logging.
5. Select the Enable Transmission of Logs to a Syslog Server checkbox.
6. Provide the following configuration details:
   • Syslog Server: Enter the Bindplane IP address.
   • UDP Destination Port: Enter the Bindplane port number (for example, 514 for UDP).
   • Log Facility: Enter Local6.
   • Select the Audit Logs checkbox.
   • Select the Security Logs checkbox.
   • Select the Risks checkbox.
7. Click OK.

UDM mapping table

UDM mapping delta reference

On August 26, 2025, Google SecOps released a new version of the Symantec Endpoint Protection parser, which includes significant changes to the mapping of Symantec Endpoint Protection log fields to UDM fields and changes to the mapping of event types.

Log-field mapping delta

The following table lists the mapping delta for Symantec Endpoint Protection log-to-UDM fields exposed prior to August 26, 2025 and subsequently (listed in the Old mapping and Current mapping columns respectively).

Event-type mapping delta

Multiple events that were classified before as generic events are now properly classified with meaningful event types.

The following table lists the delta for the handling of Symantec Endpoint Protection event types prior to August 26, 2025 and subsequently (listed in the Old event_type and Current event_type columns respectively).

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