Collect MicroStrategy logs

Supported in:

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

MicroStrategy is a business intelligence and analytics platform. It generates audit logs for report execution, user sessions, data access, and admin operations. The parser extracts fields from MicroStrategy log messages and maps them to the Unified Data Model (UDM), capturing user identity, session details, server information, and security metadata.

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 MicroStrategy Intelligence Server
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the MicroStrategy Intelligence Server (administrator role or server filesystem access)

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

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

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

Locate the configuration file

  • Linux:

    sudo systemctl status observiq-otel-collector
    
  • 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:
      tcplog:
        listen_address: "0.0.0.0:514"
    
    exporters:
      chronicle/microstrategy:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: MICROSTRATEGY
        raw_log_field: body
    
    service:
      pipelines:
        logs/microstrategy:
          receivers:
            - tcplog
          exporters:
            - chronicle/microstrategy
    

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • tcplog: The receiver type based on protocol:
      • udplog for UDP syslog
      • tcplog for TCP syslog
      • syslog for RFC 3164/5424 syslog
    • 0.0.0.0: IP address to listen on:
      • 0.0.0.0 to listen on all interfaces (recommended)
      • Specific IP address to listen on one interface
    • 514: Port number to listen on (for example, 514, 1514, 6514)
  • Exporter configuration:

    • <customer_id>: Customer ID from the earlier step
    • malachiteingestion-pa.googleapis.com: 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
    • Adjust the creds_file_path depending on the platform:
      • Linux: /etc/bindplane-agent/ingestion-auth.json
      • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json

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 MicroStrategy syslog forwarding

MicroStrategy Intelligence Server writes log files locally to the filesystem. Configure syslog forwarding using the system syslog daemon to send these logs to the Bindplane agent.

  1. Locate the MicroStrategy log directory:

    • Windows: C:\Program Files\Common Files\MicroStrategy\Log\
    • Linux: /var/log/Strategy/
  2. Configure the system syslog daemon to monitor and forward MicroStrategy log files to the Bindplane agent.

On Linux (rsyslog):

  1. Create a new rsyslog configuration file:

    sudo nano /etc/rsyslog.d/microstrategy-forward.conf
    
  2. Add the following content to forward MicroStrategy logs:

    module(load="imfile")
    input(type="imfile"
        File="/var/log/Strategy/DSSErrors.log"
        Tag="microstrategy"
        Severity="info"
        Facility="local0")
    local0.* @BINDPLANE_AGENT_IP:514
    
  3. Restart the rsyslog service:

    sudo systemctl restart rsyslog
    

On Windows:

Use a log forwarder utility (such as NXLog or Snare) to monitor the MicroStrategy log directory and forward events via syslog to the Bindplane agent IP and port.

UDM mapping table

Log Field UDM Mapping Logic
Account_Creation_Timestamp, Account_Modification_Timestamp, Timestamp additional.fields Merged with labels created from fields if not empty
Authentication_message metadata.description Value copied directly
Event_start metadata.event_timestamp Converted using date filter with format "MMM dd HH:mm:ss"
metadata.event_type Set to "USER_UNCATEGORIZED" if has_principal and has_target, else "STATUS_UPDATE" if has_principal, else "GENERIC_EVENT"
Session network.session_id Value copied directly
Source_server principal.application Value copied directly
Hostname principal.asset.hostname Value copied directly
server_ip principal.asset.ip Value copied directly
Hostname principal.hostname Value copied directly
server_ip principal.ip Value copied directly
level principal.platform_patch_level Value copied directly
User_Group_Name principal.user.group_identifiers Value copied directly
Account_Name, User principal.user.user_display_name Value from Account_Name if not empty, else User
id, Account_Login, Account principal.user.userid Value from id if not empty, else Account_Login if not empty, else Account
Log_level security_result.detection_fields Merged with label created from field if not empty
Source_host src.asset.hostname Value copied directly
Source_host src.hostname Value copied directly
module target.application Value copied directly
client_ip target.asset.ip Value copied directly
client_ip target.ip Value copied directly
PID target.process.pid Value copied directly
Thread_ID, SID, method, Account_Status_DESC target.resource.attribute.labels Merged with labels created from fields if not empty
OID target.resource.id Value copied directly
Object_Owner_Name target.resource.name Value copied directly
user target.user.user_display_name Value copied directly
UID target.user.userid Value copied directly
metadata.product_name Set to "MICROSTRATEGY"
metadata.vendor_name Set to "MICROSTRATEGY"

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