Collect Colinet Trotta GAUS SEGUROS logs

This document explains how to ingest Colinet Trotta GAUS SEGUROS logs to Google Security Operations using the Bindplane agent.

Colinet Trotta GAUS SEGUROS is an insurance management platform developed by Colinet Trotta S.A. (Argentina). It generates user activity and audit logs, including user account details, login events, and system operations. The platform does not provide public documentation for log export; the export process depends on your specific GAUS deployment and requires coordination with Colinet Trotta's technical support team.

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 GAUS SEGUROS server
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Colinet Trotta GAUS SEGUROS platform with administrator permissions
• Access to the GAUS SEGUROS database or reporting module for log export

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

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 the Bindplane agent installation guide.

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

Locate the configuration file

• Linux:

  sudo nano /opt/observiq-otel-collector/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:
      filelog:
          include:
              - /path/to/gaus-seguros-logs/*.log
          start_at: beginning
  
  exporters:
      chronicle/ct_gaus_seguros:
          compression: gzip
          creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
          customer_id: '<customer_id>'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: CT_GAUS_SEGUROS
          raw_log_field: body
          ingestion_labels:
              env: production
  
  service:
      pipelines:
          logs/ct_gaus_seguros_to_chronicle:
              receivers:
                  - filelog
              exporters:
                  - chronicle/ct_gaus_seguros
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • filelog: The receiver type for collecting log files from disk
  • include: List of file paths or glob patterns to monitor:
    • Adjust the path to match your GAUS SEGUROS log file location
    • Use glob patterns (for example, *.log, *.csv) to match multiple files
  • start_at: Set to beginning to read existing log files from the start, or end to only read new entries

• Exporter configuration:

  • ct_gaus_seguros: Descriptive name for the exporter
  • 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 from the previous step
  • 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
  • CT_GAUS_SEGUROS: Log type exactly as it appears in Chronicle
  • ingestion_labels: Optional labels in YAML format (for example, env: production)

• Pipeline configuration:

  • ct_gaus_seguros_to_chronicle: Descriptive name for the pipeline

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, run the following command:

  sudo systemctl restart observiq-otel-collector
  

  1. Verify the service is running:

     sudo systemctl status observiq-otel-collector
     

  2. Check logs for errors:

     sudo journalctl -u observiq-otel-collector -f
     

• To restart the Bindplane agent in Windows, 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.

    4. Verify the service is running:

       sc query observiq-otel-collector
       

    5. Check logs for errors:

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

Export GAUS SEGUROS logs for collection

1. Contact your Colinet Trotta account representative or GAUS SEGUROS system administrator to identify the available log export methods for your deployment.
2. Common approaches for exporting audit data from GAUS SEGUROS include:
   • Database export: GAUS stores user and audit data in a relational database. Your database administrator can export the relevant tables (for example, user account tables with columns for user ID, display name, email, status, and timestamps) as CSV or delimited text files.
   • Application-level export: If your GAUS deployment includes a reporting or audit module, use it to generate periodic audit reports and export them as files.
3. Save the exported log files to the directory monitored by the Bindplane agent (for example, /path/to/gaus-seguros-logs/).

4. (Optional) Schedule regular exports using a cron job or Windows Task Scheduler to automate log file generation.

UDM mapping table

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