> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/firewalls/fortinet.md).

# Fortinet FortiGate

The ThreatDefence platform integrates with **Fortinet® FortiGate®** by forwarding syslog to the **ThreatDefence Syslog Forwarder VM**. This enables SOC monitoring of traffic, policy events, and threat activity.

***

## Requirements

* Deployed and reachable **ThreatDefence Syslog Forwarder VM**
* Admin access to FortiGate (CLI or Web UI)
* SSH/console access for CLI configuration (preferred)

***

## Step 1 — Configure Syslog Forwarding (CLI — Preferred)

1. Connect to the FortiGate via SSH or console and sign in as an administrator.
2. Run the following commands (replace `<syslog_forwarder_ip>` with your TD Syslog Forwarder IP):

```
    config log syslogd setting  
      set status enable  
      set server <syslog_forwarder_ip>  
      set mode udp  
      set port 11514
      set format default  
    end
```

> **Important:** Keep the format as **default** (do **not** use CEF), otherwise parsing issues will occur.
>
> **Note:** The support person assigned will provide you with the required destination port.

***

## Step 1 (Alternative) — Configure via Web UI

1. Sign in to the FortiGate Web UI.
2. Go to **Log & Report → Log Settings** (Global Settings).
3. Set:
   * **Event Logging:** `All`
   * **Local Traffic Logging:** `All`
   * **Syslog Logging:** `Enable`
   * **IP address/FQDN:** *ThreatDefence Syslog Forwarder VM IP*
4. Click **Apply**.

> **Note:** Do not switch the logging format to CEF.

***

## Step 2 — Register the Log Source with ThreatDefence

After forwarding is enabled, raise a request with ThreatDefence Support so we can activate and normalize the Fortinet source:

* **Service Desk Ticket**
  * **Category:** `Onboarding`
  * **Sub-category:** `Syslog Log Sources`
  * **Include:**
    * FortiGate **source IP** sending syslog
    * **Model & firmware** version (e.g., FG-100F, v7.2.x)
    * Confirmation that syslog to the **forwarder IP:11514/UDP** is enabled

***

## Verification

ThreatDefence SOC will confirm that Fortinet logs are:

* Ingested by the Syslog Forwarder
* Parsed and normalized correctly
* Visible in dashboards for monitoring and detections

> If needed, we’ll advise on tuning (e.g., additional event types, traffic logging scope, or multiple tenants/sources).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/siem-integrations/firewalls/fortinet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.