> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/d-j-integrations/fortinet/fortinet-fortianalyzer-setup-for-workbench.md).
# Fortinet FortiAnalyzer Setup for Workbench
The Fortinet FortiAnalyzer integration allows Expel to retrieve new and updated log events, normalize them, and produce a security signal. In addition, the integration allows investigative actions to be triggered to retrieve information for more effective triage and analysis.
## Prerequisites
* You must be an admin user with the `super_admin` profile, so that you are able to create a REST API administrator account.
## Step 1: Create a REST API Administrator Account in FortiAnalyzer
The REST API administrator account allows automated configuration, backup creation, and monitoring of the FortiGate.
1. Log in to the FortiAnalyzer console and select your administrative domain (ADOM).
The default ADOM is root.
2. Click **System Settings**.
3. From the menu on the left, click **Admin > Administrators**.
4. From the **Create New** dropdown, select **REST API Admin**.
5. Complete the Create New REST API Administrator form:
* **User Name** - provide a meaningful name.
* Select **Administrative Domain**.
* **Admin Profile** - select **Restricted\_User**.
* **JSON API Access** - select **Read**.
6. Choose one of the following options depending on your configuration:
* If you use an [assembler](https://support.expel.io/hc/en-us/articles/1500009628381), add the IP address of the assembler to the **Trusted Hosts** section.
* If you do **not** use an assembler, **add** [**these Expel IP addresses**](/workbench-setup/configure-an-ip-allow-list.md) to the **Trusted Hosts** section.
7. Click **OK**.
8. Generate the API key:
* Select the newly created user.
* Click **Regenerate > Generate**.
* **Copy and save the API key** to a safe location, as you will need it in a later section.
## Step 2: Enable Console Access
In this step you will create a local administrator account necessary to enable console access. Expel requires console access to allow analysts to perform investigation and triage. Without this additional level of information, details cannot be verified by our analysts and an investigation cannot be initiated. For more information, see [Why Expel Asks for Console Access](https://support.expel.io/hc/en-us/articles/12871722483347-Why-Expel-Asks-for-Console-Access).
1. Still in System Settings, on the Administrators page, look for the **Create New** dropdown and select **Administrator**.
2. Complete the Create New Administrator form:
* **User Name** - provide a meaningful name.
* **Admin Type** - select **Local**.
* **Password** - create a password.
* Select the **Administrative Domain**.
* **Admin Profile** - select **Restricted\_User**.
* **JSON API Access** - select **None**.
* **Trusted Hosts** - toggle to **on**.
3. Choose one of the following options depending on your configuration:
* If you use an assembler (not-required), add the IP address of the assembler to the **Trusted Hosts** section.
* If you do **not** use an assembler, **add** [**these Expel IP addresses**](/workbench-setup/configure-an-ip-allow-list.md) to the **Trusted Hosts** section.
4. Click **OK**.
## Step 3: Add Fortinet FortiAnalyzer as a Security Device in Workbench
1. [Log in to Workbench](https://workbench.expel.io/).
2. Navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. Search for and select **FortiAnalyzer**.
5. Specify where your device is hosted:
* For Cloud, click **Cloud**.
* For on-premise configurations, click **On-prem** and **specify the Assembler**.
6. Provide the following information:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName FortiAnalyzer”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
* **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
* **URL** - your FortiAnalyzer fully qualified domain name (FQDN) or IP address, including `https://`.
* **API key** - the key you generated in [Step 1](#uuid-9581f12a-f6b3-aef2-0a70-3400b3544143_bridgehead-idm4560985997502433128558963209).
7. Select **Save**.
8. On the console access screen, select **Set up now (recommended)** and fill in the appropriate fields:
* **Console URL** - the same as your FortiAnalyzer FQDN or IP Address in the previous step.
* **Username** and **Password** - provide the credentials you created in [Step 2](#uuid-9581f12a-f6b3-aef2-0a70-3400b3544143_bridgehead-idm4598690449347234192858581205).
9. Click **Save**.
Your device should be created successfully within a few seconds. A few reminders:
* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.expel.io/connect-your-technology/d-j-integrations/fortinet/fortinet-fortianalyzer-setup-for-workbench.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.