Collect Fortinet Firewall logs

This document explains how to collect and ingest Fortinet logs to Google Security Operations by using Bindplane. The parser extracts fields from logs, handling both JSON and SYSLOG (with key-value pair) formats. It normalizes the extracted fields into the Unified Data Model (UDM), including network connections, user activity, DNS events, and security findings, while also handling various log formats and edge cases.

Before you begin

• Ensure that you have a Google Security Operations instance.
• Ensure that you are using Windows 2016 or later, or a Linux host with systemd.
• If running behind a proxy, ensure firewall ports are open.
• Ensure that you have privileged access to a Fortinet Firewall appliance.

Get Google SecOps ingestion authentication file

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agents.
3. Download the Ingestion Authentication File. Save the file securely on the system where Bindplane will be installed.

Get Google SecOps customer ID

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Profile.
3. Copy and save the Customer ID from the Organization Details section.

Install the Bindplane agent

Windows installation

1. Open the 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
   

Linux installation

1. Open a terminal with root or sudo privileges.

2. Run the following command:

   sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh
   

Additional installation resources

• For additional installation options, consult this installation guide.

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

1. Access the configuration file:

   1. Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   2. Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   ```yaml
   receivers:
       udplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           ingestion_labels:
               log_type: FORTINET_FIREWALL
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   ```
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

• To restart the Bindplane agent in Linux, run the following command:

  sudo systemctl restart bindplane-agent
  

• To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

  net stop BindPlaneAgent && net start BindPlaneAgent
  

Configure Syslog on FortiGate using CLI

1. Sign in to the command line interface on your Fortinet FortiGate appliance.

2. Type the following commands in the same order (replace the variables with values that align with your environment).

   sh full-configuration | grep -f syslogd
   config log syslogd setting
       set status enable
       set server IP_ADDRESS
       set mode udp
       set port PORT
       set facility LOCAL
       set reliable enable or disable
       set source-ip FIEWALL_IP
   end
   

3. Update the following values:

   • IP_ADDRESS: enter the IPv4 address of the Bindplane agent.
   • PORT: enter the port number for the Bindplane agent; for example, 514.
   • LOCAL: set facility level as local6 (you can also select other as local0, local1, local2, local3, local4, local5, or local7 for informational logs).
   • enable or disable: enter disable to send data as UDP (If you set the value of reliable as enable, it sends data as TCP).
   • FIEWALL_IP: enter the IPv4 address of the Firewall.

Configure Syslog on FortiGate using GUI

1. Sign in to the Fortinet Fortigate web UI.
2. Go to Log & Report > Log Settings.
3. Edit the following configurations:
   • Send logs to Syslog: select to Enable.
   • IP Address / FQDN: enter the IPv4 address of the Bindplane agent.
   • Event Logging: select All.
   • Local Traffic Log: select All.

4. Go to Policy & Objects > Firewall Policy

   • Enable log level to All (do not set to Disable & UTM) for every firewall policy.
   • Ensure Implicit Deny policy should also be in log level All.

5. Open CLI and enter the following commands.

   1. Get your firewall applicance IP:

      Show full-configuration | grep -f syslogd
      

   2. Set source IP & Facility:

      • LOCAL: Set facility level as local6 (you can also select other as local0, local1, local2, local3, local4, local5, or local7 for informational logs).

      • FIEWALL_IP: Enter the IPv4 address of the Firewall.

        config log syslogd setting
        set source-ip FIEWALL_IP
        set facility LOCAL
        end
        

   3. Enable resolve-ip for each fortigate device:

      config log setting
      set resolve-ip enable
      

6. Repeat the process for each device which needs to be onboarded to Google SecOps.

Optional: Additional Fortigate Syslog configuration options

1. For FortiGate v5.X, to enable extended logs, run the following commands:

   config antivirus profile
       edit default
           set extended-utm-log enable
       end
   config application
       edit default
           set extended-utm-log enable
       end
   config webfilter
       edit default
           set extended-utm-log enable
       end
   config spamfilter
       edit default
           set extended-utm-log enable
       end
   config dlp
       edit default
           set extended-utm-log enable
       end
   config ips
       edit default
           set extended-utm-log enable
       end
   

UDM Mapping Table

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