Collect Fortinet Web Proxy logs
This document explains how to ingest Fortinet Web Proxy logs to Google Security Operations using the Bindplane agent.
Fortinet FortiGate web proxy generates logs for explicit and transparent proxy sessions, capturing HTTP/HTTPS traffic, URL filtering decisions, and web access events. The logs use syslog key-value format and include network metadata, security actions, and user identity information.
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 FortiGate appliance
- If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
- Privileged access to the FortiGate appliance with administrator permissions
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 IDfrom the Organization Detailssection.
Install the Bindplane agent
Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.
Windows installation
- Open Command Promptor PowerShellas 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-collectorThe 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-collectorThe 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.yamlwith the following configuration:receivers : udplog : listen_address : "0.0.0.0:514" exporters : chronicle/fortinet_webproxy : compression : gzip creds_file_path : '/etc/bindplane-agent/ingestion-auth.json' customer_id : '<customer_id>' endpoint : malachiteingestion-pa.googleapis.com log_type : FORTINET_WEBPROXY raw_log_field : body ingestion_labels : env : production service : pipelines : logs/webproxy_to_chronicle : receivers : - udplog exporters : - chronicle/fortinet_webproxy
Configuration parameters
Replace the following placeholders:
-
Receiver configuration:
-
udplog: The receiver type based on protocol:-
udplogfor UDP syslog -
tcplogfor TCP syslog
-
-
0.0.0.0: IP address to listen on:-
0.0.0.0to 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:
-
fortinet_webproxy: Descriptive name for the exporter -
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
- Linux:
-
<customer_id>: Customer ID from the previous step -
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
- US:
-
FORTINET_WEBPROXY: Log type exactly as it appears in Chronicle -
ingestion_labels: Optional labels in YAML format (for example,env: production)
-
-
Pipeline configuration:
-
webproxy_to_chronicle: Descriptive name for the pipeline
-
Save the configuration file
- After editing, save the file:
- Linux: Press
Ctrl+O, thenEnter, thenCtrl+X - Windows: Click File > Save
- Linux: Press
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:
- Press
Win+R, typeservices.msc, and press Enter. - Locate observIQ OpenTelemetry Collector.
- 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"
- Press
-
Configure Fortinet FortiGate web proxy syslog forwarding
- Sign in to the FortiGateweb interface.
- Go to Log & Report > Log Settings.
- Scroll down to the Remote Logging and Archivingsection.
- Under Syslog, click Add.
- Provide the following configuration details:
- Name: Enter a descriptive name (for example,
Chronicle-Bindplane). - IP Address/FQDN: Enter the IP address of the Bindplane agent host (for example,
192.168.1.100). - Port: Enter
514(must match the Bindplane agent receiver port). - Protocol: Select UDP.
- Minimum Level: Select Informationor Notification.
- Name: Enter a descriptive name (for example,
-
Ensure the Web Proxylog category is enabled. Alternatively, use the CLI to configure the syslog filter:
config log syslogd setting set status enable set server <BINDPLANE_AGENT_IP> set port 514 end config log syslogd filter set filter "logid(0300)" set filter-type include end- The
0300log ID range covers web proxy events. Adjust the filter according to your environment. - Replace
<BINDPLANE_AGENT_IP>with the IP address of the Bindplane agent host.
- The
-
Click OKto save.
-
Click Applyat the top right to apply the configuration.
-
Verify that syslog messages are being received by checking the Bindplane agent logs.
UDM mapping table
| Log Field | UDM Mapping | Logic |
|---|---|---|
|
group, profile, agent, subtype, catdesc, reqtype
|
additional.fields | Merged with labels created from each field |
|
action, has_network, has_principal, has_target
|
metadata.event_type | Set to USER_LOGIN if action is auth-logon, else NETWORK_HTTP if has_network true, else NETWORK_CONNECTION if has_principal and has_target true, else STATUS_UPDATE if has_principal true, else GENERIC_EVENT |
|
eventtype
|
metadata.product_event_type | Value copied directly |
|
logid
|
metadata.product_log_id | Value copied directly |
| |
metadata.product_name | Set to "FORTINET_WEBPROXY" |
| |
metadata.vendor_name | Set to "FORTINET_WEBPROXY" |
|
service
|
network.application_protocol | Value copied directly if service in HTTP, HTTPS |
|
direction
|
network.direction | Set to INBOUND if direction in incoming, inbound, response, else OUTBOUND if in outgoing, outbound |
|
httpmethod
|
network.http.method | Value copied directly if httpmethod in GET, POST |
|
referralurl
|
network.http.referral_url | Value copied directly |
|
proto, subtype, service
|
network.ip_protocol | Set to UDP if proto=17, TCP if proto=6 or subtype=wad, IP6IN4 if proto=41, ICMP if service=PING or proto=1 or service matches ICMP |
|
rcvdbyte
|
network.received_bytes | Converted to unsigned integer |
|
sentbyte
|
network.sent_bytes | Converted to unsigned integer |
|
sessionid
|
network.session_id | Value copied directly |
|
devname
|
principal.asset.hostname | Value copied directly |
|
srcip
|
principal.asset.ip | Value copied directly |
|
devname
|
principal.hostname | Value copied directly |
|
srcip
|
principal.ip | Value copied directly |
|
srccountry
|
principal.location.country_or_region | Value copied directly if not Reserved and not empty |
|
srcport
|
principal.port | Converted to integer |
|
srcuuid
|
principal.user.product_object_id | Value copied directly |
|
vd
|
principal.user.user_display_name | Value copied directly |
|
user
|
principal.user.userid | Value copied directly |
|
filtername
|
security_result.about.resource.attribute.labels | Merged with label created from filtername if not empty and not - |
|
action
|
security_result.action | Set to BLOCK if action=blocked, ALLOW if action in accept, passthrough |
|
devid, policyid, srcintf, srcintfrole, ratemethod, cat
|
security_result.detection_fields | Merged with labels created from each field |
|
msg
|
security_result.description | Value copied directly |
|
poluuid
|
security_result.rule_id | Value copied directly |
|
policytype
|
security_result.rule_type | Value copied directly |
|
level
|
security_result.severity | Set to HIGH if level=warning, MEDIUM if level=notice |
|
type
|
security_result.summary | Value copied directly |
|
dstip
|
target.asset.ip | Value copied directly |
|
filename
|
target.file.full_path | Value copied directly |
|
filetype
|
target.file.mime_type | Value copied directly |
|
filesize
|
target.file.size | Converted to unsigned integer |
|
hostname
|
target.hostname | Value copied directly |
|
dstip
|
target.ip | Value copied directly |
|
dstcountry
|
target.location.country_or_region | Value copied directly |
|
dstport
|
target.port | Converted to integer |
|
dstintf, dstintfrole
|
target.resource.attribute.labels | Merged with labels created from each field |
|
dstuuid
|
target.resource.product_object_id | Value copied directly |
|
url
|
target.url | Value copied directly |
Need more help? Get answers from Community members and Google SecOps professionals.

