Console
    Start free

    Collect Symantec Security Analytics logs

    Supported in:

    This document explains how to ingest Symantec Security Analytics logs to Google Security Operations using Bindplane.

    Symantec Security Analytics (formerly Blue Coat) is a network forensics and packet capture platform that provides deep packet inspection, full network visibility, and threat analysis for on-premise deployments.

    Before you begin

    Make sure you have the following prerequisites:

    • A Google SecOps instance
    • Windows Server 2016 or later, or Linux host with systemd
    • Network connectivity between the Bindplane agent and the Symantec Security Analytics appliance
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to the Symantec Security Analytics appliance with administrator permissions

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

    3. Wait for the installation to complete.

    4. Verify the installation by running:

       sc query observiq-otel-collector

    The service should show as RUNNING.

    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

    3. Wait for the installation to complete.

    4. Verify the installation by running:

       sudo  
systemctl  
status  
observiq-otel-collector

    The service should show as active (running).

    Additional installation resources

    For additional installation options and troubleshooting, see Bindplane agent installation guide .

    Configure Bindplane agent to ingest syslog and send to Google SecOps

    Locate the configuration file

    • Linux:

       sudo  
nano  
/etc/bindplane-agent/config.yaml

    • Windows:

       notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

    Edit the configuration file

    • Replace the entire contents of config.yaml with the following configuration:

        receivers 
 : 
  
 udplog 
 : 
  
 listen_address 
 : 
  
 "0.0.0.0:514" 
 exporters 
 : 
  
 chronicle/symantec_sa 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 SYMANTEC_SA 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/symantec_sa_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/symantec_sa

    Configuration parameters

    Replace the following placeholders:

    • Receiver configuration:

      • listen_address : IP address and port to listen on:
        • 0.0.0.0 to listen on all interfaces (recommended)
        • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

    • Exporter configuration:

      • creds_file_path : Full path to ingestion authentication file:
        • Linux: /etc/bindplane-agent/ingestion-auth.json
        • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
      • customer_id : Customer ID copied from the Google SecOps console
      • endpoint : Regional endpoint URL:
        • US: malachiteingestion-pa.googleapis.com
        • Europe: europe-malachiteingestion-pa.googleapis.com
        • Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
        • See Regional Endpoints for complete list

    Save the configuration file

    • After editing, save the file:
      • Linux: Press Ctrl+O , then Enter , then Ctrl+X
      • Windows: Click File > Save

    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 Symantec Security Analytics syslog forwarding

    1. Sign in to the Symantec Security Analyticsappliance web interface.
    2. Go to System > Alerting > Syslog.
    3. Click Addto create a new syslog destination.
    4. Provide the following configuration details:
      • Syslog Server: Enter the IP address of the Bindplane agent host.
      • Port: Enter 514 .
      • Protocol: Select UDP.
      • Facility: Select Local0or your preferred facility.
    5. Select the log categories to forward (security alerts, system events, network events).
    6. Click Saveto apply the configuration.
    7. Verify that logs are being sent by checking the Bindplane agent logs.

    UDM mapping table

    Log Field UDM Mapping Logic
    		additional.fields Merged from m_label, c_label, start_time_label
    action_name
    		 security_result.action_details Value copied directly
    category
    		 target.resource.type Value copied directly
    cs4
    		 security_result.description Value copied directly
    cs5
    		 security_result.summary Value copied directly
    dmac
    		 target.mac Value copied directly
    dpt
    		 target.port Converted to integer
    dst
    		 target.ip Extracted using grok pattern as dst_ip
    dst
    		 target.asset.ip Extracted using grok pattern as dst_ip
    elapsed_time
    		 security_result.detection_fields Merged from elapsed_time_label
    end
    		 Converted from epoch ms to timestamp (not used in UDM mapping)
    event_id
    		 security_result.rule_id Value copied directly
    event_name
    		 metadata.product_event_type Value copied directly
    evt
    		 metadata.product_event_type Value copied directly
    host
    		 intermediary.hostname Value copied directly
    host
    		 intermediary.asset.hostname Value copied directly
    id
    		 target.resource.id Value copied directly
    ip
    		 principal.ip Extracted using grok pattern as ip_address1
    ip
    		 principal.asset.ip Extracted using grok pattern as ip_address1
    ip_address
    		 principal.ip Extracted using grok pattern as ip_address2
    ip_address
    		 principal.asset.ip Extracted using grok pattern as ip_address2
    logmsg
    		 metadata.description Value copied directly
    m
    		 additional.fields Merged from m_label
    mac_address
    		 principal.mac Value copied directly
    model
    		 target.resource.name Value copied directly
    msgs
    		 metadata.description Value copied directly
    path
    		 target.file.full_path Value copied directly
    query_id
    		 target.resource.attribute.labels Merged from query_id_label
    remote_ip
    		 target.ip Extracted using grok pattern as r_ipaddress
    remote_ip
    		 target.asset.ip Extracted using grok pattern as r_ipaddress
    sequenceId
    		 metadata.product_log_id Value copied directly
    severity
    		 security_result.severity_details Value copied directly
    severity
    		 security_result.severity Set to LOW if in ["0","1","2","3"]; MEDIUM if in ["4","5","6"]; HIGH if in ["7","8"]; CRITICAL if in ["9","10"]; else UNKNOWN_SEVERITY
    smac
    		 principal.mac Value copied directly
    sn
    		 principal.mac Value copied directly
    spt
    		 principal.port Converted to integer
    src
    		 principal.ip Extracted using grok pattern as src_ip
    src
    		 principal.asset.ip Extracted using grok pattern as src_ip
    start
    		 additional.fields Merged from start_time_label
    ts
    		 metadata.collected_timestamp Converted using date match formats
    user
    		 principal.user.userid Value copied directly
    version
    		 metadata.product_version Value copied directly
    		metadata.event_type Set to NETWORK_CONNECTION if has_principal and has_target true; STATUS_UPDATE if has_principal true and has_target false; USER_UNCATEGORIZED if has_principal_user true; else GENERIC_EVENT
    		metadata.product_name Set to "Security Analytics Platform"
    		metadata.vendor_name Set to "Symantec Corporation"

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

    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: