Collect Airlock Digital Application Allowlisting logs

Parser Version: 1.0

Supported in:

Google SecOps SIEM

This document explains how to ingest Airlock Digital Application Allowlisting logs to Google Security Operations using the Bindplane agent.

Airlock Digital is an application allowlisting and execution control platform that enforces a deny-by-default security model on endpoints, ensuring only trusted applications, scripts, and processes are permitted to execute. The platform provides granular policy control at the file, path, publisher, and parent process level, along with comprehensive audit trails for compliance and threat management. Airlock Digital generates logs for execution events, blocked executions, policy changes, and administrative actions, which can be forwarded to SIEM solutions using syslog, CEF, JSON, or HTTP(S).

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 Airlock Digital Server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
An Airlock Digital Server (on-premise or cloud) with administrator access
Airlock Digital v4.7 or later (for syslog external logging support)

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)

Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
Go to IAM & Admin > Service Accounts.
Click Create service account.
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).
Click Create and continue.
In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
Click Continue, and then click Done.
Click the service account you created, and then go to the Keys tab.
Click Add key > Create new key.
Select JSON and click Create. The key file is downloaded to your computer.
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.
Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Option 2: Download the ingestion authentication file (legacy)

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 the Bindplane agent will be installed.

Get a 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/airlock_digital:
    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: AIRLOCK_DIGITAL
    raw_log_field: body

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

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 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 (for example, europe-malachiteingestion-pa.googleapis.com).
```
exporters:
  chronicle/airlock_digital:
    compression: gzip
    creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
    customer_id: '<customer_id>'
    endpoint: malachiteingestion-pa.googleapis.com
    log_type: AIRLOCK_DIGITAL
    raw_log_field: body
```

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 Airlock Digital external logging

Configure the Airlock Digital Server to forward logs using syslog to the Bindplane agent. Airlock Digital supports multiple external logging formats, including Generic Syslog, CEF, JSON, HTTP(S), and GELF.

Sign in to the Airlock Digital Server Console with an administrator account.
Go to System > External Logging.
Click Add to create a new external logging configuration.
In the Logging Type dropdown, select Generic Syslog.

Note: Generic Syslog is recommended for Google SecOps ingestion. The Google SecOps parser for Airlock Digital supports both syslog and JSON log formats.
Provide the following configuration details:
- Server Address: Enter the IP address or hostname of the Bindplane agent host (for example, 192.168.1.100)
- Port: Enter 514 (or the port configured in the Bindplane agent)
- Protocol: Select TCP
Note: Use TCP to ensure reliable log delivery. If you select UDP, update the Bindplane agent receiver to udplog accordingly.
In the Log Categories section, select the event types to forward:
- Execution Events (blocked and allowed executions)
- Policy Changes
- Administrative Actions
- Agent Events
- Server Activity
Note: For comprehensive security monitoring, select all available log categories.
Click Save to apply the external logging configuration.
Verify that logs are being forwarded by checking the Bindplane agent logs or reviewing the External Logging status in the Airlock Digital Server Console.

Note: If the Airlock Digital Server cannot connect to the syslog destination over TCP, the service will queue log events and retry. Ensure network connectivity and firewall rules permit traffic from the Airlock Digital Server to the Bindplane agent on the configured port.

For more information about Airlock Digital SIEM integrations, see the Airlock Digital SIEM integration page.

UDM mapping table

Log Field	UDM Mapping	Logic
`event_type`	`extensions.auth.type`	Mapped: `ServerActivityMessage` → `SSO`
`product_event_type`	`extensions.auth.type`	Mapped: `(?i)Login` → `SSO`
`task`	`extensions.auth.type`	Mapped: `Login` → `AUTHTYPE_UNSPECIFIED`, `Logout` → `AUTHTYPE_UNSPECIFIED`
`intermediary_hostname`	`intermediary.hostname`	Directly mapped
`description`	`metadata.description`	Directly mapped
`metadata_description`	`metadata.description`	Directly mapped
`event_timestamp`	`metadata.event_timestamp`	Parsed as `yyyy-MM-dd HH:mm:ss.SSS`
`ingestion_time`	`metadata.event_timestamp`	Parsed as `RFC 3339`
`event_type`	`metadata.event_type`	Mapped: `FileActivityMessage` → `STATUS_UPDATE`, `ServerActivityMessage` → `USER_LOGIN`, `Se...
`has_principal`	`metadata.event_type`	Mapped: `true` → `FILE_UNCATEGORIZED`
`product_event_type`	`metadata.event_type`	Mapped: `(?i)Login` → `USER_LOGIN`
`task`	`metadata.event_type`	Mapped: `Login` → `USER_LOGIN`, `Logout` → `USER_LOGOUT`
`event_type`	`metadata.product_event_type`	Directly mapped
`product_event_type`	`metadata.product_event_type`	Directly mapped
`checkpoint`	`metadata.product_log_id`	Directly mapped
`browser`	`network.http.user_agent`	Directly mapped
`netdomain`	`principal.administrative_domain`	Directly mapped
`asset_category`	`principal.asset.category`	Directly mapped
`hostname`	`principal.asset.hostname`	Directly mapped
`srcip`	`principal.asset.ip`	Merged
`software`	`principal.asset.software`	Merged
`hostname`	`principal.hostname`	Directly mapped
`principal_hostname`	`principal.hostname`	Directly mapped
`srcip`	`principal.ip`	Merged
`process_file_path`	`principal.process.file.full_path`	Directly mapped
`file_md5`	`principal.process.file.md5`	Directly mapped
`process_file_name`	`principal.process.file.names`	Merged
`file_sha256`	`principal.process.file.sha256`	Directly mapped
`parent_process_file`	`principal.process.parent_process.file.full_path`	Directly mapped
`principal_user_userid`	`principal.user.userid`	Directly mapped
`description`	`security_result.action`	Mapped: `Invalid login attempt` → `security_result_action`
`metadata_description`	`security_result.action`	Mapped: `logged in success` → `security_result_action`
`security_result_action`	`security_result.action`	Merged
`file_sha128_label`	`security_result.detection_fields`	Merged
`policyname_label`	`security_result.detection_fields`	Merged
`policyver_label`	`security_result.detection_fields`	Merged
`ppolicy_label`	`security_result.detection_fields`	Merged
`sha128_label`	`security_result.detection_fields`	Merged
`sha384_label`	`security_result.detection_fields`	Merged
`sha512_label`	`security_result.detection_fields`	Merged
`type_label`	`security_result.detection_fields`	Merged
`source_file`	`src.file.full_path`	Directly mapped
`source_file_name`	`src.file.full_path`	Directly mapped
`filename`	`target.file.full_path`	Directly mapped
`sha256`	`target.file.sha256`	Directly mapped
`commandline`	`target.process.command_line`	Directly mapped
`filename`	`target.process.file.full_path`	Directly mapped
`InstanceURL`	`target.url`	Directly mapped
`principal_user_userid`	`target.user.userid`	Directly mapped
`user`	`target.user.userid`	Directly mapped
N/A	`extensions.auth.type`	Constant: `AUTHTYPE_UNSPECIFIED`
N/A	`metadata.event_type`	Constant: `USER_LOGIN`
N/A	`metadata.product_name`	Constant: `Airlock Digital`
N/A	`metadata.vendor_name`	Constant: `Airlock Digital`

Change Log

View the Change Log for this parser

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