# Collect Evision FircoSoft logs

**Parser Version:** 1.0
Supported in:

This document explains how to ingest Evision FircoSoft logs to Google Security Operations using the Bindplane agent.

Evision FircoSoft (now part of LexisNexis Risk Solutions as Firco Compliance Link) is an on-premises financial crime compliance screening platform for financial institutions. It detects sanctions violations, PEP matches, and AML risks in transactions and messages. The application stores audit records including screening decisions, user access events, table access events, and configuration changes as log files on the local file system.

## Before you begin

Make sure you have the following prerequisites:

- A Google SecOps instance
- Windows Server 2016 or later with `observiq-otel-collector` service support
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Administrative access to the FircoSoft (Firco Compliance Link) server and its log directory

## 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 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**.

### Additional installation resources

For additional installation options and troubleshooting, see the [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 the Bindplane agent to ingest logs and send to Google SecOps

### Locate the configuration file

- **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:
        filelog:
          include:
            - C:\FircoSoft\logs\*.log
          start_at: beginning

      exporters:
        chronicle/evision_fircosoft:
          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: 'C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json'
          customer_id: '<customer_id>'
          endpoint: chronicle.googleapis.com
          log_type: EVISION_FIRCOSOFT
          raw_log_field: body
          ingestion_labels:
            env: production

      service:
        pipelines:
          logs/fircosoft_to_chronicle:
            receivers:
              - filelog
            exporters:
              - chronicle/evision_fircosoft

### Configuration parameters

Replace the following placeholders:

- **Receiver configuration:**

  - `filelog`: The receiver type for collecting log files from disk
  - `include`: List of file paths to monitor. Set this to the location where FircoSoft writes its log files (for example, `C:\FircoSoft\logs\*.log`). Adjust the path to match your installation directory
  - `start_at`: Set to `beginning` to read existing logs or `end` to only read new entries
- **Exporter configuration:**

  - `evision_fircosoft`: Descriptive name for the exporter
  - `creds_file_path`: Full path to the service account JSON key file (Option 1):
    - **Windows** : `C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json`
  - `<customer_id>`: 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`.
  - `EVISION_FIRCOSOFT`: Log type exactly as it appears in Chronicle
  - `ingestion_labels`: Optional labels in YAML format (for example, `env: production`)
- **Pipeline configuration:**

  - `fircosoft_to_chronicle`: Descriptive name for the pipeline

### 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/evision_fircosoft:
          compression: gzip
          creds_file_path: 'C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json'
          customer_id: '<customer_id>'
          endpoint: malachiteingestion-pa.googleapis.com
          log_type: EVISION_FIRCOSOFT
          raw_log_field: body
          ingestion_labels:
            env: production

> [!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:
  - **Windows** : Click **File \> Save**

## Restart the Bindplane agent to apply the changes

- 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"

## Identify FircoSoft log file locations

FircoSoft (Firco Compliance Link) writes audit and operational log files to the local file system. The exact location depends on your installation configuration.

1. Common default log directories:

   - `C:\FircoSoft\logs\`
   - `C:\Program Files\FircoSoft\Firco Compliance Link\logs\`
   - A custom directory configured during installation
2. To determine the log directory for your deployment:

   1. Sign in to the **FircoSoft** (Firco Compliance Link) administration console.
   2. Go to **Administration \> System Configuration** (or **Server Settings**).
   3. Locate the **Log directory** or **Output directory** setting.
   4. Note the configured path.
3. FircoSoft typically writes the following log file types:

   - Audit trail logs (user access, screening decisions, configuration changes)
   - Statistics logs (transaction screening volumes and results)
   - Application operational logs
4. Update the `include` path in the Bindplane agent `config.yaml` to match the actual log directory on your server:

       receivers:
         filelog:
           include:
             - C:\FircoSoft\logs\*.log

   - Replace \`C:\\FircoSoft\\logs\` with the actual path from step 2.
   - Use wildcard patterns (`*.log`, `*.txt`, `*.xml`) to match the log file format used in your deployment.

   > [!NOTE]
   > **Note:** The Bindplane agent service account must have read access to the log directory. FircoSoft log files may be in delimited text or XML format depending on the deployment configuration.

## UDM mapping table

| Log Field | UDM Mapping | Logic |
|---|---|---|
| date, time | metadata.event_timestamp | Converted using format: yyyy-MM-dd HH:mm:ss.SSS |
|   | metadata.event_type | Set to "USER_RESOURCE_ACCESS" |
| nature | metadata.product_event_type | Set to "Estadisticas" if nature == "C", else "Otros" if nature == "A" |
| user | principal.user.userid | Value copied directly |
| success | security_result.action | Set to "ALLOW" if success =\~ "SI", else "BLOCK" if success =\~ "NO" |
| details | security_result.action_details | Value copied directly |
| table | target.resource.name | Value copied directly |
|   | metadata.product_name | Set to "Fircosoft" |
|   | metadata.vendor_name | Set to "eVision" |

## Change Log

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

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