Collect SAP Web Dispatcher logs

Supported in:

Google secops SIEM

This document explains how to ingest SAP Web Dispatcher logs to Google Security Operations using Bindplane.

SAP Web Dispatcher is a reverse proxy and load balancer for SAP systems that generates HTTP access, security, and error logs. The parser extracts fields from SAP Web Dispatcher log entries and maps them to the Unified Data Model (UDM), capturing HTTP request details, network connections, TLS 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 SAP Web Dispatcher host
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the SAP Web Dispatcher host 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](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](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 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/sap_webdisp:
    compression: gzip
    creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
    customer_id: '<customer_id>'
    endpoint: malachiteingestion-pa.googleapis.com
    log_type: SAP_WEBDISP
    raw_log_field: body

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

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:

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.
Verify the service is running:
```
sc query observiq-otel-collector
```

Check logs for errors:

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

Configure SAP Web Dispatcher syslog forwarding

SAP Web Dispatcher stores log files locally on the server filesystem. Configure syslog forwarding using the system syslog daemon to send these logs to the Bindplane agent.

Locate the SAP Web Dispatcher log files. The default paths are:
- Linux: /usr/sap/<SID>/DVEBMGS<NR>/work/dev_icm_sec*
- Windows: C:\usr\sap\<SID>\DVEBMGS<NR>\work\dev_icm_sec*
Note: Replace <SID> with your SAP System ID and <NR> with the instance number.
Configure the system syslog daemon to monitor and forward SAP Web Dispatcher log files. On Linux, create a new rsyslog configuration file:
```
sudo nano /etc/rsyslog.d/sap-webdisp-forward.conf
```
Add the following content:
```
module(load="imfile")
input(type="imfile"
    File="/usr/sap/PRD/DVEBMGS00/work/dev_icm_sec*"
    Tag="sap-webdisp"
    Severity="info"
    Facility="local0")
local0.* @@BINDPLANE_AGENT_IP:514
```
Note: Replace the file path with the actual path to your SAP Web Dispatcher log files. Replace BINDPLANE_AGENT_IP with the IP address of the Bindplane agent host. Use @@ for TCP or @ for UDP.
Restart the rsyslog service:
```
sudo systemctl restart rsyslog
```

UDM mapping table

Log Field	UDM Mapping	Logic
app_protocol	network.application_protocol	Value copied directly if in ["HTTP","HTTPS"]
desc	metadata.description	Value copied directly
dest_host	target.asset.hostname	Value copied directly
dest_host	target.hostname	Value copied directly
event_type	metadata.event_type	Value from event_type if not empty, else set to "GENERIC_EVENT"
http_method	network.http.method	Value copied directly
http_version	network.application_protocol_version	Value copied directly
referral_url	network.http.referral_url	Value copied directly
referral_url	target.url	Value copied directly
response_code	network.http.response_code	Value copied directly, converted to integer
src_ip	principal.asset.ip	Value copied directly
src_ip	principal.ip	Value copied directly
tls_version	network.tls.version	Value copied directly
	metadata.event_type	Set to "NETWORK_HTTP" if has_principal true and has_target true and network.http not empty, else "STATUS_UPDATE" if has_principal true
	metadata.product_name	Set to "SAP_WEBDISP"
	metadata.vendor_name	Set to "SAP_WEBDISP"

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