Collect Fortinet FortiAnalyzer logs

Supported in:

Google secops SIEM

This guide explains how you can ingest Fortinet FortiAnalyzer logs to Google Security Operations using Bindplane.

Fortinet FortiAnalyzer is a centralized log management, analytics, and reporting platform for Fortinet Security Fabric devices. It aggregates logs from FortiGate firewalls, FortiMail, FortiWeb, FortiSandbox, and other Fortinet products to provide unified visibility, event correlation, and compliance reporting. FortiAnalyzer can forward aggregated logs via syslog to external SIEM platforms for further analysis.

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 FortiAnalyzer appliance.
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
Privileged access to the Fortinet FortiAnalyzer management console (Super_User or equivalent 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.

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.

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](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](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: bash sudo nano /opt/observiq-otel-collector/config.yaml
Windows: cmd 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:
    # Replace the port and IP address as required
    listen_address: "0.0.0.0:514"

exporters:
  chronicle/fortianalyzer:
    compression: gzip
    # Adjust the path to the credentials file you downloaded in Step 1
    creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
    # Replace with your actual customer ID from Step 2
    customer_id: 'your-customer-id-here'
    endpoint: malachiteingestion-pa.googleapis.com
    log_type: FORTINET_FORTIANALYZER
    raw_log_field: body
    ingestion_labels:
      env: production

service:
  pipelines:
    logs/fortianalyzer_to_chronicle:
      receivers:
        - tcplog
      exporters:
        - chronicle/fortianalyzer

Configuration parameters

Receiver configuration:
- listen_address: IP address and port to listen on. Use 0.0.0.0 to listen on all interfaces. Change the port if needed (for example, 1514).
Exporter configuration:
- creds_file_path: Full path to the ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- customer_id: Your Google SecOps customer ID.
- endpoint: Regional endpoint URL (e.g., malachiteingestion-pa.googleapis.com).
- ingestion_labels: Optional labels in YAML format (for example, env: production).

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 FortiAnalyzer syslog forwarding

Configure FortiAnalyzer to forward logs to the Bindplane agent using syslog output.

Configure syslog server in FortiAnalyzer

Sign in to the FortiAnalyzer web interface.
Go to System Settings > Log Forwarding.
Click Create New to add a new log forwarding rule.
Provide the following configuration details:
- Name: Enter a descriptive name (for example, Chronicle-Bindplane).
- Status: Select Enable.
- Remote Server Type: Select Syslog.
- Server IP/FQDN: Enter the IP address of the Bindplane agent host.
- Server Port: Enter 514 (or the port configured in the Bindplane agent).
- Reliable syslog (RFC 6587): Select Enable to use TCP transport.
- Log Forwarding Format: Select Default or CEF based on your requirements.
In the Log Filters section, configure the log types to forward:
- Select the ADOM (Administrative Domain) from which to forward logs.
- Select the device types and log categories to include (Traffic, Event, Security, DNS, SSH, SSL logs).
Click OK to save the configuration.

Verify log forwarding

Go to System Settings > Log Forwarding.
Verify the forwarding rule shows status as Enabled.
Monitor the Statistics column to confirm logs are being forwarded.
Verify logs are being received by checking the Bindplane agent logs.

UDM mapping table

Log Field	UDM Mapping	Logic
`devname`	`principal.hostname`	Taken from `devname`.
`srcip`	`principal.ip`	Taken from `srcip`.
`srcport`	`principal.port`	Converted to integer.
`srcintf`	`additional.fields`	Key: `srcintf`.
`dstip`	`target.ip`	Taken from `dstip`.
`dstport`	`target.port`	Converted to integer.
`dstintf`	`additional.fields`	Key: `dstintf`.
`proto`	`network.ip_protocol`	Mapped (6=TCP, 17=UDP, 1=ICMP).
`action`	`security_result.action`	`accept/pass` → ALLOW; `deny/drop/block` → BLOCK.
`policyid`	`security_result.rule_id`	Taken from `policyid`.
`policyname`	`security_result.rule_name`	Taken from `policyname`.
`user`	`principal.user.userid`	Taken from `user`.
`app`	`target.application`	Taken from `app`.
`sentbyte`	`network.sent_bytes`	Converted to unsigned integer.
`rcvdbyte`	`network.received_bytes`	Converted to unsigned integer.
`severity`	`security_result.severity`	`information` → INFORMATIONAL, `warning` → MEDIUM, `error` → ERROR, `critical/alert/emergency` → HIGH.
`logid`	`metadata.product_log_id`	Taken from `logid`.
`type`	`metadata.product_event_type`	Taken from `type`.
`subtype`	`metadata.product_event_type`	Appended to type.
`level`	`security_result.severity_details`	Taken from `level`.
N/A	`metadata.vendor_name`	Set to Fortinet.
N/A	`metadata.product_name`	Set to FortiAnalyzer.

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