# Collect Stealthbits StealthDEFEND logs

Supported in:

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 credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

- **New deployments**: Use the Chronicle API (Option 1).
- **Legacy deployments**: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

### Option 1: Create a service account for the Chronicle API (recommended)

1. Sign in to the [Google Cloud console](https://console.cloud.google.com/) and select the Google Cloud project that is linked to your Google SecOps instance.
2. Go to **IAM \& Admin \> Service Accounts**.
3. Click **Create service account**.
4. Provide the following configuration details:
   - **Service account name** : Enter a name for the account (for example, `bindplane-ingest`).
   - **Service account description** : Enter a description (for example, `Bindplane agent log ingestion`).
5. Click **Create and continue**.
6. In the **Grant this service account access to project** section, click **Select a role** and select **Chronicle Editor**.
7. Click **Continue** , and then click **Done**.
8. Click the service account you created, and then go to the **Keys** tab.
9. Click **Add key \> Create new key**.
10. Select **JSON** and click **Create**. The key file is downloaded to your computer.
11. Save the key file as `ingestion-auth.json` in the Bindplane collector directory (`/opt/observiq-otel-collector/ingestion-auth.json` on Linux or `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json` on Windows), or update `creds_file_path` in `config.yaml` to match the path where you save it.
12. Go to **IAM \& Admin \> Settings** and copy the **Project number**. You'll need it for the exporter configuration.

> [!NOTE]
> **Note:** The JSON key is a credential. Restrict access to the file on the Bindplane host and rotate the key according to your organization's policy.

### Option 2: Download the ingestion authentication file (legacy)

1. Sign in to the Google SecOps console.
2. Go to **Settings \> Data Management \> Collection Agents** . If you are on a SIEM-only platform, go to **Settings \> Collection Agents**.
3. Download the **ingestion authentication file**.
4. Save the file securely on the system where the Bindplane agent will be installed.

> [!NOTE]
> **Note:** This file authenticates the agent to the legacy Ingestion API (`malachiteingestion-pa.googleapis.com`), which Google has scheduled for end of life on July 20, 2027. Plan to move to Option 1 before that date.

## Get Google SecOps customer ID

1. Sign in to the Google SecOps console.
2. Go to **Settings \> Administration \> Profile** . If you are on a SIEM-only platform, go to **Settings \> Profile**.
3. Copy and save the **Customer ID** from the **Organization Details** section.

   > [!NOTE]
   > **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

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](https://docs.cloud.google.com/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).

> [!NOTE]
> **Note:** The Chronicle API exporter configuration requires Bindplane collector v1.106.0 or later. The previous commands install the latest release. If you're updating an existing installation, upgrade the collector before changing the configuration.

## 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:
          protocol: https
          # Region of your instance, for example us, europe, asia-southeast1
          location: <LOCATION>
          # Project number of the Google Cloud project linked to the instance
          project: '<PROJECT_NUMBER>'
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: '<customer_id>'
          endpoint: chronicle.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
  - `location`: Replace `<LOCATION>` with the region of your Google SecOps instance (for example, `us`, `europe`, or `asia-southeast1`). The exporter prefixes `chronicle.googleapis.com` with this value. See [Regional Endpoints](https://docs.cloud.google.com/chronicle/docs/reference/rest?rep_location=us#regional-service-endpoint) for the complete list.
  - `project`: Replace `<PROJECT_NUMBER>` with the project number from **IAM \& Admin \> Settings**.
  - `endpoint`: Keep set to `chronicle.googleapis.com`.
  - Adjust the `creds_file_path` to the path of your service account JSON key file (Option 1), depending on the platform:
    - **Linux** : `/opt/observiq-otel-collector/ingestion-auth.json`
    - **Windows** : `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json`

### Legacy ingestion API exporter

- If you use the ingestion authentication file from Option 2, replace the `exporters` block with the following. Set `creds_file_path` to the path to the ingestion authentication file, and if your instance is outside the US, replace `malachiteingestion-pa.googleapis.com` with your [regional endpoint](https://docs.cloud.google.com/chronicle/docs/reference/ingestion-api#regional-endpoints) (for example, `europe-malachiteingestion-pa.googleapis.com`).

      exporters:
        chronicle/stealthbits_defend:
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: '<customer_id>'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: STEALTHBITS_DEFEND
          raw_log_field: body

> [!NOTE]
> **Note:** This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

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

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

1. Sign in to the **StealthDEFEND** management console.
2. Go to **Configuration \> SIEM**.
3. Click **Add** to create a new SIEM integration.
4. 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).
5. Select the event categories to forward (for example, threat alerts, AD changes, authentication events).
6. Click **Save**.

   > [!NOTE]
   > **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 |

## Change Log

[View the Change Log for this parser](https://docs.cloud.google.com/chronicle/docs/ingestion/parser-list/stealthbits-defend-changelog)

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)