Collect Stealthbits StealthDEFEND logs

Supported in:

Google secops SIEM

This document explains how to ingest Stealthbits StealthDEFEND logs to Google Security Operations using the Bindplane agent.

Stealthbits (now Netwrix) StealthDEFEND is a real-time threat detection platform that identifies and responds to attacks targeting Active Directory and file systems. It generates alerts in LEEF format covering authentication anomalies, privilege escalation, and AD object modifications. The parser extracts fields from StealthDEFEND log entries and maps them to the Unified Data Model (UDM), capturing principal and target identifiers, security results, and vulnerability scan details.

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 StealthDEFEND server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the StealthDEFEND console with administrator permissions

Get Google SecOps ingestion authentication file

Sign in to the Google SecOps console.
Go to SIEM Settings > Collection Agents.
Download the Ingestion Authentication File.
Save the file securely on the system where Bindplane will be installed.

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
Copy and save the Customer ID from the Organization Details section.

Note: The customer ID is required for configuring the Bindplane agent exporter.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

Open Command Prompt or PowerShell as an administrator.

Run the following command:

msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

Wait for the installation to complete.
Verify the installation by running:
```
sc query observiq-otel-collector
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

Wait for the installation to complete.
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 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:
    tcplog:
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/stealthbits_defend:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: STEALTHBITS_DEFEND
        raw_log_field: body

service:
    pipelines:
        logs/stealthbits_defend:
            receivers:
                - tcplog
            exporters:
                - chronicle/stealthbits_defend

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

sudo systemctl restart observiq-otel-collector

Verify the service is running:

sudo systemctl status observiq-otel-collector

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

Configure StealthDEFEND syslog forwarding

StealthDEFEND supports SIEM integration via syslog in LEEF format. Configure the syslog export to forward alerts and events to the Bindplane agent.

Sign in to the StealthDEFEND management console.
Go to Configuration > SIEM.
Click Add to create a new SIEM integration.
Provide the following configuration details:
- Type: Select Syslog.
- Format: Select LEEF.
- Host: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
- Port: Enter 514 (must match the Bindplane receiver port).
- Protocol: Select TCP (must match the Bindplane receiver type).
Select the event categories to forward (for example, threat alerts, AD changes, authentication events).
Click Save.

Note: StealthDEFEND sends logs in LEEF (Log Event Extended Format). Ensure the Bindplane receiver is configured to accept TCP connections on the specified port.

UDM mapping table

Log Field	UDM Mapping	Logic
attack_host	about.hostname	Hostname associated with additional entities
	extensions.auth.type	Type of authentication used
Ended	extensions.vulns.vulnerabilities.scan_end_time	End time of the vulnerability scan
Started	extensions.vulns.vulnerabilities.scan_start_time	Start time of the vulnerability scan
intermediary_hostname	intermediary.hostname	Hostname of the intermediary device
SettingName	metadata.description	Description of the event
event_type	metadata.event_type	Type of event
product_event	metadata.product_event_type	Product-specific event type
device_version	metadata.product_version	Version of the product
domain	principal.administrative_domain	Administrative domain of the principal
source_domain	principal.domain.name	Domain name of the principal
src, shost, AttackingHost, breached_from_host	principal.hostname	Hostname of the principal
src, shost, AttackingHostIp	principal.ip	IP address of the principal
DistinguishedName	principal.user.group_identifiers	Group identifiers for the principal user
AffectedObject	principal.user.user_display_name	Display name of the principal user
suser, usrName	principal.user.userid	User ID of the principal
protocol_label	security_result.about.labels	Labels for the security result about section
sec_result_action	security_result.action	Action taken by the security system
category	security_result.category_details	Detailed category of the security result
AlertText, operation	security_result.description	Description of the security result
policy_name	security_result.rule_name	Name of the rule that triggered the result
Severity	security_result.severity	Severity of the security result
Reason, att_name	security_result.summary	Summary of the security result
OrigServer, AttackedHost	target.hostname	Hostname of the target
dst, AttackedHostIp	target.ip	IP address of the target
duser, UserName	target.user.userid	User ID of the target
UserSID	target.user.windows_sid	Windows SID of the target user
device_product	metadata.product_name	Name of the product
device_vendor	metadata.vendor_name	Name of the vendor

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