Collect Symantec Web Isolation logs

This document explains how to ingest Symantec Web Isolation logs to Google Security Operations using Bindplane. The parser handles two primary message types from Symantec Web Isolation: data trace messages and device messages. It extracts fields from JSON-formatted logs, performs data transformations like date parsing and user agent conversion, and maps the extracted data to the Unified Data Model (UDM) handling different log structures based on the traceId and event_type fields.

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 Web Isolation 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

Windows installation

1. Open the Command Prompt or PowerShell as an administrator.

2. Run the following command:

   ```cmd
   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:

   ```bash
   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: 'SYMANTEC_WEB_ISOLATION'
                   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 Web Isolation platform

1. Sign in to your Symantec Web Isolation web UI.
2. Go to System Configuration > External Log Server > New External Log Server > Syslog Server.
3. Provide the following configuration details:
   • Status: Select the checkbox to Enable.
   • Host: Enter the Bindplane agent IP address.
   • Port: Enter the Bindplane agent port number (for example, 514 for UDP).
   • Protocol: Select UDP.
   • Appname: Enter a Tag to identify the Web Isolation platform.
   • Facility: Syslog facility name related to Web Isolation logs.
4. Click Create.
5. Go to Reports > Log Forwarding.
6. Click Edit.
7. Provide the following configuration details:
   • Activity Logs: Select the newly added Bindplane server.
   • Management Audit Logs: Select the newly added Bindplane server.
   • Gateway Audit Logs: Select the newly added Bindplane server.
8. Click Update.

UDM mapping table

Changes

2022-07-08

Enhancement:

• Modified mapping for device.user.organization.id from target.user.groupid to target.user.group_identifiers.
• Modified mapping for device.user.organization.name from target.user.group_identifiers to target.user.department.

2022-06-20

Enhancement:

• Changed UDM field name from metada.product_name to metadata.product_name.
• Added conditional checks for fields original_source_ip, url_host and destination_ip.
• Dropped the logs having invalid JSON format.

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