Collect SAP Sybase ASE logs

Supported in:

Google secops SIEM

This document explains how to ingest SAP Sybase ASE logs to Google Security Operations using the Bindplane agent.

SAP Sybase Adaptive Server Enterprise (ASE) is a relational database management system that generates audit, error, and security logs. The parser extracts fields from ASE log entries and maps them to the Unified Data Model (UDM), capturing user identity, host information, and additional metadata for database operations.

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 Sybase ASE server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the SAP Sybase ASE server 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 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:
    tcplog:
        listen_address: "0.0.0.0:514"

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

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

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 SAP Sybase ASE syslog forwarding

SAP Sybase ASE stores log files on the server file system. Configure syslog forwarding using the system syslog daemon to send these logs to the Bindplane agent.

Enable auditing in SAP Sybase ASE using the sp_configure command:
```
sp_configure 'auditing', 1
```
Note: Restart the ASE server after enabling auditing for the change to take effect.
Configure the audit system to capture the events you want, using sp_audit:
```
sp_audit "all", "all", "all", "on"
```
Locate the ASE error log file. The default location is typically:
- Linux: $SYBASE/$SYBASE_ASE/install/<server_name>.log
- Windows: %SYBASE%\%SYBASE_ASE%\install\<server_name>.log
Configure the system syslog daemon to monitor and forward ASE log files. On Linux, create a new rsyslog configuration file:
```
sudo nano /etc/rsyslog.d/sap-ase-forward.conf
```
Add the following content:
```
module(load="imfile")
input(type="imfile"
    File="/opt/sybase/ASE-16_0/install/SERVERNAME.log"
    Tag="sap-ase"
    Severity="info"
    Facility="local0")
local0.* @@BINDPLANE_AGENT_IP:514
```
Note: Replace the file path with the actual path to your ASE log file. 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
extrainfo, loginname, dbname, objname, objowner, eventmod, sequence, dbid, xactid, nodeid	additional.fields	Map of additional fields not covered by the standard UDM schema
	metadata.event_type	Type of event (e.g., USER_LOGIN, NETWORK_CONNECTION)
prin_host, hostname	principal.asset.hostname	Hostname of the asset associated with the principal
prin_host, hostname	principal.hostname	Hostname of the principal
suid	principal.user.userid	Unique identifier for the user
	metadata.product_name	Name of the product
	metadata.vendor_name	Name of the vendor or company that produced the product

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