We've reorganized our navigation structure to align directly with your operational workflows. See the Google SecOps release notes for more information.

Collect Kiteworks (formerly Accellion) logs

Supported in:

Google secops SIEM

This document explains how to ingest Kiteworks (formerly known as Accellion) logs to Google Security Operations using Bindplane.

Kiteworks is a secure file sharing and governance platform that provides enterprise content communications across email, file sharing, managed file transfer, and web forms. It delivers visibility, compliance, and control over sensitive content moving in and out of the organization.

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 Kiteworks appliance
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the Kiteworks administration console (System Administrator role)

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 Bindplane agent installation guide.

Configure the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

Linux:

sudo nano /status 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:
    udplog:
        listen_address: "0.0.0.0:514"

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

service:
    pipelines:
        logs/accellion_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/accellion

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- listen_address: IP address and port to listen on:
  - 0.0.0.0 to listen on all interfaces (recommended)
  - Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)
Exporter configuration:
- creds_file_path: Full path to ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- customer_id: Customer ID copied from the Google SecOps console
- endpoint: 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

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 syslog forwarding on Kiteworks (formerly Accellion)

Sign in to the Kiteworks administration console as a System Administrator.
Go to the Locations page:
- Legacy admin UI: Go to System > Locations.
- New admin UI: Go to System Setup > Locations.
Select the target location from the list.
Go to the External Services section.
Expand the Syslog Settings panel.
Click Add to create a new syslog server configuration.
Provide the following configuration details:
- Syslog Server: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
- Protocol: Select UDP or TCP, depending on your Bindplane agent receiver configuration.
- Port: Enter the Bindplane agent port number (for example, 514).
- Use TLS: Select this checkbox if you want to transport syslog messages over TLS (available only when TCP is selected as the protocol).
- Format: Select JSON Format (recommended for structured parsing).
Click Save to apply the configuration.

Note: Kiteworks syslog exports all data and administrative events including file movements, file access, errors, access control changes, privilege changes, user on/offboarding, failed and successful logins, and scan failures (AV, ATP, DLP).

UDM mapping table

Log Field	UDM Mapping	Logic
`acct`	`principal.user.user_display_name`	The value of `acct` from the raw log's `msg` field.
`acct`	`target.user.user_display_name`	The value of `acct` from the raw log's `msg` field.
`addr`	`principal.ip`	The value of `addr` from the raw log's `msg` field.
`a0`	`security_result.about.labels.value`	The value of `a0` from the raw log's `msg` field, where the corresponding `key` is "a0".
`a1`	`security_result.about.labels.value`	The value of `a1` from the raw log's `msg` field, where the corresponding `key` is "a1".
`a2`	`security_result.about.labels.value`	The value of `a2` from the raw log's `msg` field, where the corresponding `key` is "a2".
`a3`	`security_result.about.labels.value`	The value of `a3` from the raw log's `msg` field, where the corresponding `key` is "a3".
`arch`	`security_result.about.platform_version`	The value of `arch` from the raw log's `msg` field. Only applicable for `type_name` SYSCALL.
`auid`	`about.user.userid`	The value of `auid` from the raw log's `msg` field.
`auid`	`security_result.detection_fields.value`	The value of `auid` from the raw log's `msg` field, where the corresponding `key` is "auid".
`comm`	`principal.application`	The value of `comm` from the raw log's `msg` field.
`cmd`	`principal.process.command_line`	The value of `cmd` from the raw log's `msg` field.
`cwd`	`security_result.detection_fields.value`	The value of `cwd` from the raw log's `msg` field, where the corresponding `key` is "cwd".
`cwd`	`target.process.file.full_path`	The value of `cwd` from the raw log's `msg` field.
`exe`	`principal.process.file.full_path`	The value of `exe` from the raw log's `msg` field.
`exe`	`target.process.file.full_path`	The value of `exe` from the raw log's `msg` field.
`exit`	`security_result.about.labels.value`	The value of `exit` from the raw log's `msg` field, where the corresponding `key` is "Exit Code".
`hostname`	`principal.hostname`	The value of `hostname` from the raw log's `msg` field.
`key`	`security_result.about.registry.registry_key`	The value of `key` from the raw log's `msg` field. Only applicable for `type_name` SYSCALL.
`log_type`	`metadata.log_type`	The value of `log_type` from the raw log.
`msg`	`security_result.action_details`	The value after `res=` in the `msg` field of the raw log.
`msg`	`security_result.summary`	Combination of fields from the `msg` field of the raw log. Parsed from the `audit` section of the `msg` field in the raw log. Mapped based on the `type` field in the raw log. For example, "USER_START" maps to "USER_LOGIN", "CRED_DISP" maps to "USER_LOGOUT", "CRED_ACQ" maps to "USER_LOGIN", "USER_END" maps to "USER_LOGOUT", "CRED_REFR" maps to "USER_LOGIN", "USER_CMD" maps to "USER_LOGIN", "CWD" maps to "STATUS_UPDATE", "PROCTITLE" maps to "STATUS_UPDATE", "USER_ACCT" maps to "USER_UNCATEGORIZED", and "SYSCALL" maps to "USER_UNCATEGORIZED".
`node`	`principal.hostname`	The value of `node` from the raw log's `msg` field.
`pid`	`principal.process.pid`	The value of `pid` from the raw log's `msg` field.
`ppid`	`principal.process.parent_process.pid`	The value of `ppid` from the raw log's `msg` field.
`proctitle`	`target.process.file.full_path`	Decoded hexadecimal value of `proctitle` from the raw log's `msg` field. Hardcoded to "LINUX". Set to "ALLOW" if `res=success` is present in the raw log's `msg` field.
`ses`	`network.session_id`	The value of `ses` from the raw log's `msg` field.
`syscall`	`security_result.about.labels.value`	The value of `syscall` from the raw log's `msg` field, where the corresponding `key` is "Syscall".
`success`	`security_result.summary`	Combined with other fields to form the summary. For SYSCALL events, the logic is: if success=yes, then "yes, The System call succeeded", otherwise "no, The System call failed".
`terminal`	`principal.terminal`	The value of `terminal` from the raw log's `msg` field.
`timestamp`	`timestamp`	The value of `timestamp` from the raw log entry.
`tty`	`principal.terminal`	The value of `tty` from the raw log's `msg` field.
`type`	`metadata.product_event_type`	The value of `type` from the raw log's `msg` field.
`uid`	`about.user.userid`	The value of `uid` from the raw log's `msg` field. Only applicable for `type_name` SYSCALL.
`uid`	`target.user.userid`	The value of `uid` from the raw log's `msg` field. Set to "SETTING" if `type` is "USER_ACCT".

Change Log

View the Change Log for this parser

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