# Collect IBM Informix logs

Supported in:

This document explains how to ingest IBM Informix logs into Google Security Operations using the Bindplane agent.

IBM Informix is a high-performance relational database management system that provides comprehensive audit logging capabilities through its secure-auditing facility. The Audit to Syslog (ASL) functionality allows audit records to be sent to the syslog daemon for centralized log collection and SIEM integration.

## Before you begin

Make sure you have the following prerequisites:

- A Google SecOps instance
- Windows Server 2016 or later, or a Linux host with `systemd`
- Network connectivity between the Bindplane agent and IBM Informix server
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Administrative access to the IBM Informix server with AAO (Audit Administrator Officer) role
- IBM Informix 12.10 or later (ASL functionality was introduced in version 12.10)
- Audit masks configured for the users or events you want to monitor

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

1. Replace the entire contents of `config.yaml` with the following configuration:

       receivers:
         udplog:
           listen_address: "0.0.0.0:514"

       exporters:
         chronicle/informix:
           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: 'YOUR_CUSTOMER_ID'
           endpoint: chronicle.googleapis.com
           log_type: INFORMIX
           raw_log_field: body
           ingestion_labels:
             env: production
             source: informix_audit

       service:
         pipelines:
           logs/informix_to_chronicle:
             receivers:
               - udplog
             exporters:
               - chronicle/informix

2. Replace the following placeholders:

   - Receiver configuration:

     - `listen_address`: IP address and port to listen on:

       - `0.0.0.0:514` to listen on all interfaces on port 514 (standard syslog port)
       - Use port `1514` or higher if running as non-root user on Linux
       - Adjust port number to match your Informix syslog configuration
   - Exporter configuration:

     - `creds_file_path`: Full path to the service account JSON key file (Option 1). Make sure that you save the credentials file as `ingestion-auth.json` in one of the following locations:

       - **Linux** : `/opt/observiq-otel-collector/ingestion-auth.json`
       - **Windows** : `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json`
     - `customer_id`: Replace `YOUR_CUSTOMER_ID` with the customer ID from the previous 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`.

     - `log_type`: Set to `INFORMIX`

     - `ingestion_labels`: Optional labels to categorize logs (customize as needed)

### Example configuration for TCP syslog

- If you prefer TCP for reliable delivery, use this configuration instead:

      receivers:
        tcplog:
          listen_address: "0.0.0.0:514"

      exporters:
        chronicle/informix:
          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: 'YOUR_CUSTOMER_ID'
          endpoint: chronicle.googleapis.com
          log_type: INFORMIX
          raw_log_field: body

      service:
        pipelines:
          logs/informix_to_chronicle:
            receivers:
              - tcplog
            exporters:
              - chronicle/informix

### 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/informix:
          compression: gzip
          creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
          customer_id: 'YOUR_CUSTOMER_ID'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: INFORMIX
          raw_log_field: body
          ingestion_labels:
            env: production
            source: informix_audit

> [!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:

  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 IBM Informix syslog forwarding

### Create audit masks

Before enabling auditing, you must create audit masks to define which events to audit for which users.

1. Connect to the IBM Informix server as a user with AAO role.

2. Create a default audit mask for all users to audit common database events:

       onaudit -a -u _default -e +OPDB,GRDB,CRTB,ALTB,DRTB

   This command creates the `_default` mask and audits the following events:
   - **OPDB**: Open Database
   - **GRDB**: Grant Database Access
   - **CRTB**: Create Table
   - **ALTB**: Alter Table
   - **DRTB**: Drop Table
3. To enable row-level auditing for data modifications, create a mask with row-level events:

       onaudit -a -u _require -e +DLRW,INRW,UPRW,RDRW

   This command creates the `_require` mask and audits:
   - **DLRW**: Delete Row
   - **INRW**: Insert Row
   - **UPRW**: Update Row
   - **RDRW**: Read Row

   > [!NOTE]
   > **Note:** Row-level auditing events (DLRW, INRW, UPRW, RDRW) are only audited on tables that have the AUDIT flag set. Enable row-level auditing with `onaudit -R 1` after creating the masks.

4. To create a mask for a specific user, replace `_default` with the username:

       onaudit -a -u username -e +OPDB,GRDB,CRTB,ALTB,DRTB,DLRW,INRW,UPRW

5. Verify the audit masks were created:

       onaudit -o

### Enable Audit to Syslog (ASL)

1. Enable ASL auditing and configure syslog parameters:

       onaudit -E on -F LOG_LOCAL0 -I informix_audit -P LOG_INFO

   This command:
   - `-E on`: Enables Audit to Syslog functionality
   - `-F LOG_LOCAL0`: Sets syslog facility to LOG_LOCAL0 (recommended for filtering)
   - `-I informix_audit`: Sets syslog identifier to `informix_audit` (appears in syslog messages)
   - `-P LOG_INFO`: Sets syslog priority to LOG_INFO

   > [!NOTE]
   > **Note:** Available facilities are LOG_USER (default), LOG_LOCAL0 through LOG_LOCAL7, LOG_AUTH, or LOG_AUTHPRIV. LOG_LOCAL0 through LOG_LOCAL7 are recommended for custom applications.

2. Enable mandatory auditing for database administrators:

       onaudit -A on -S on

   This command:
   - `-A on`: Enables mandatory auditing for DBSA (Database Server Administrator) group
   - `-S on`: Enables mandatory auditing for DBSSO (Database Security Officer) group
3. If you want to enable row-level auditing for tables with the AUDIT flag:

       onaudit -R 1

   This sets the ADTROWS parameter to 1, enabling selective row-level auditing.
4. Verify the audit configuration:

       onaudit -c

   The output should show:
   - `ADT_SYSLOG_ENABLED = 1`
   - `ADT_SYSLOG_FACILITY = LOG_LOCAL0`
   - `ADT_SYSLOG_IDENTIFIER = informix_audit`
   - `ADT_SYSLOG_PRIORITY = LOG_INFO`
   - `ADT_DBSA = 1` (if enabled)
   - `ADT_DBSSO = 1` (if enabled)

### Configure syslog daemon to forward to Bindplane agent

The Informix ASL functionality sends audit records to the local syslog daemon. You must configure the syslog daemon to forward these messages to the Bindplane agent.

**For rsyslog (most common on Linux):**

1. Create a new rsyslog configuration file:

       sudo nano /etc/rsyslog.d/30-informix-audit.conf

2. Add the following configuration to forward Informix audit logs:

       # Forward Informix audit logs to Bindplane agent
       local0.* @127.0.0.1:514

   If you configured a different facility in the `onaudit -F` command, replace `local0` with your facility (for example, `local1`, `local2`, etc.).

   If the Bindplane agent is on a different server, replace `127.0.0.1` with the Bindplane agent's IP address.

   For TCP forwarding (more reliable), use `@@` instead of `@`:

       local0.* @@127.0.0.1:514

3. Save the file and restart rsyslog:

       sudo systemctl restart rsyslog

4. Verify rsyslog is running:

       sudo systemctl status rsyslog

**For syslog-ng:**

1. Edit the syslog-ng configuration file:

       sudo nano /etc/syslog-ng/syslog-ng.conf

2. Add the following configuration:

       # Define destination for Bindplane agent
       destination d_bindplane {
           udp("127.0.0.1" port(514));
       };

       # Filter for Informix audit logs
       filter f_informix {
           facility(local0);
       };

       # Log path to forward Informix logs
       log {
           source(s_src);
           filter(f_informix);
           destination(d_bindplane);
       };

3. Save the file and restart syslog-ng:

       sudo systemctl restart syslog-ng

### Test the configuration

1. Generate a test audit event by connecting to a database:

       dbaccess stores_demo

   Then exit the database.
2. Check the Bindplane agent logs to verify audit records are being received:

   **Linux:**

       sudo journalctl -u observiq-otel-collector -f | grep informix

   **Windows:**

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

3. You can also use the `onshowaudit` utility to view audit records from the syslog files:

       onshowaudit -f /var/log/syslog -u your_username

   > [!NOTE]
   > **Note:** The syslog daemon adds timestamp and hostname information before the Informix audit record. The Informix record begins with the server status (for example, `ONLN|`) followed by pipe-delimited fields.

### Audit log format

- Informix audit logs sent via syslog have the following format:

      Jan 12 11:59:21 hostname informix_audit: ONLN|2021-01-12 18:59:21.512|hostname|31055|servername|username|0:OPDB:stores_demo:0:-

  The format includes:
  - Syslog timestamp and hostname (added by syslog daemon)
  - Syslog identifier (configured with `-I` option)
  - Server status (ONLN = online)
  - Informix timestamp
  - Hostname
  - Process ID
  - Server name
  - Username
  - Event code and details (pipe-delimited)

### Additional configuration options

- **To set syslog options:**

      onaudit -O LOG_NDELAY,LOG_PID

  Available options:
  - `LOG_NDELAY`: Open connection immediately (default)
  - `LOG_ODELAY`: Delay opening connection (mutually exclusive with LOG_NDELAY)
  - `LOG_PID`: Include process ID in messages
  - `LOG_CONS`: Write to console if syslog unavailable
  - `LOG_PERROR`: Write to stderr as well as syslog
- **To change the audit file path (for classic auditing):**

      onaudit -p /path/to/audit/directory

- **To set maximum audit file size:**

      onaudit -s 50000000

  This sets the maximum size to 50 MB (value in bytes).
- **To start a new audit file manually:**

      onaudit -n

- **To set error handling mode:**

      onaudit -e 1

Error modes:

- `0`: Continue processing and log error (default)
- `1`: Suspend thread until audit record can be written
- `3`: Shut down the server

## UDM mapping table

| Log Field | UDM Mapping | Logic |
|---|---|---|
| id, dequeue_count, RequestId | about.labels | Merged with labels for 'Message Id', 'Dequeue Count', 'Request Id' |
| timestamp | metadata.event_timestamp | Converted using format: yyyy-MM-dd HH:mm:ss.SSS |
| type | metadata.event_type | Set to 'GENERIC_EVENT' if type == 'ERROR', else 'SYSTEM_AUDIT_LOG_UNCATEGORIZED' |
| serverName | principal.asset.asset_id | Concatenated from "PRODUCT_SPECIFIC_ID: " and serverName if type != 'ERROR' |
| hostName | principal.hostname | Value copied directly if type != 'ERROR' |
| processId | principal.process.pid | Value copied directly if type != 'ERROR' |
| eventOutput, eventName | principal.resource.attribute.labels | Merged with labels for 'Event Output', 'Event Name' |
| dbName | principal.resource.name | Value copied directly if data != "" |
|   | principal.resource.type | Set to "DATABASE" if data != "" |
| userName | principal.user.userid | Value copied directly if type != 'ERROR' |
| errorCode, type | security_result.action | Set to 'BLOCK' if type == 'ERROR', else 'ALLOW' if errorCode == '0', else 'BLOCK' |
| Exception | security_result.description | Value copied directly if kv_data_1 != "" |
| ErrorCode | security_result.rule_name | Value copied directly if kv_data_1 != "" |
| description | security_result.summary | Value copied directly if description != "" |
| blob_name, file_name | target.file.full_path | Value from blob_name if type == 'ERROR', else file_name |
|   | metadata.product_name | Set to "INFORMIX" |
|   | metadata.vendor_name | Set to "IBM" |

## Change Log

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

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