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

# FortiSOAR Integration

Set up a FortiSOAR connector to send alerts to ilert and automate incident workflows.

Integrating [FortiSOAR](https://www.fortinet.com/products/fortisoar) with ilert enables automated alerting and incident response by sending alert events from FortiSOAR to ilert. This integration helps streamline your security operations and reduces mean time to respond (MTTR) by linking playbook-based automation with ilert's alert management platform.

## In ilert: Create a FortiSOAR alert source

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **FortiSOAR**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-71ccb4e22d5fa58761c78e9b23028ab9bc4342cc%2Falert-source-fortisoar.png?alt=media" alt="The Settings tab of a FortiSOAR alert source in ilert, showing the integration type, the masked integration key, and the FortiSOAR URL."><figcaption></figcaption></figure>

## Prerequisites: Download the ilert FortiSOAR integration connector

* <https://github.com/iLert/ilert-fortisoar>

## In FortiSOAR: Installation and setup of ilert connector

1. In the FortiSOAR sidebar, navigate to **Content Hub**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fn9YYYG6fd0mXdvyP7ARP%2F1.png?alt=media&amp;token=1f7c4fef-3b92-4eb2-97e9-60225d6b0ef8" alt=""><figcaption></figcaption></figure>

2. Navigate to the **Manage** tab.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FGCWNhnEs9MsMmAsJpO5S%2F23.png?alt=media&amp;token=63bebc4d-d95b-4d1f-b670-6ffb98c3b54e" alt=""><figcaption></figcaption></figure>

3. Click **Upload Connector**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FKJXQRDiZPsPMTDDmP3hk%2F24.png?alt=media&amp;token=3cf9ea8f-2fe5-494d-94aa-3ec4c4264ae7" alt=""><figcaption></figcaption></figure>

4. Upload the downloaded plugin from [this step](#prerequisites-download-the-ilert-fortisoar-integration-connector).

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FG4AhHhTCCc6PK5pZdpAl%2F25.png?alt=media&amp;token=896ed136-e5db-49a9-8391-080acb591d91" alt=""><figcaption></figcaption></figure>

5. Provide a **Configuration Name**.
6. Paste the previously copied **Integration URL** from ilert.
7. Click **Save**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FY2eHMAZp38WjZokfZSE9%2F3.png?alt=media&amp;token=79750568-667f-456e-949a-eddb1301cca7" alt=""><figcaption></figcaption></figure>

8. The configuration connector status will now be displayed.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FrE1RvWwCqwSo3UMTY4H8%2F4.png?alt=media&amp;token=7fa02b44-a5ed-4c0e-b455-c0682a829abe" alt=""><figcaption></figcaption></figure>

## In FortiSOAR: Add new playbooks to send alerts to ilert

### Create a playbook triggered on alert creation

1. Navigate to **Automation → Playbooks**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FocvyiN1F3ve3h6SsylzL%2F5.png?alt=media&amp;token=e914bf64-342c-4a37-b568-95f01e3d19f9" alt=""><figcaption></figcaption></figure>

2. Select an existing **Collection** or create a new one.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FLdX4jR51J6mDvz2DT1tO%2F6.png?alt=media&amp;token=802b0f62-5e8c-4644-92f1-af8881575add" alt=""><figcaption></figcaption></figure>

3. Click **Add Playbook**.
4. Enter a name and click **Create**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FDO9bDRL5KLea2KDtCO1H%2F7.png?alt=media&amp;token=d5e56e5b-384c-4b3a-aff9-59caab9e81a8" alt=""><figcaption></figcaption></figure>

5. Choose **On Create** as the trigger step.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FTkJ0yTcaJ3cBq9X84KgG%2F8.png?alt=media&amp;token=df44f959-f4b6-45b5-8d07-6741f95215a9" alt=""><figcaption></figcaption></figure>

6. Enter a **Step Name**, select **Alerts** as the resource, then click **Save**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FCAARcI7yBSun4AnBleup%2F9.png?alt=media&amp;token=5fe41d83-6828-4c8b-afd9-877c44359197" alt=""><figcaption></figcaption></figure>

7. Add the next step by selecting **Connector** under the **EXECUTE** section.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FDYEsdUfhDttGzGh8iI8J%2F10.png?alt=media&amp;token=d67beb40-0891-4a37-8cc8-13f90576ede4" alt=""><figcaption></figcaption></figure>

8. Search for `ilert` and select the ilert connector.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fz3HDbu4kO8h2tm5RQ9JA%2F11.png?alt=media&amp;token=e9226ab6-234f-4cbb-b0a6-f951042f597e" alt=""><figcaption></figcaption></figure>

9. Enter a **Step Name**, select your previously created ilert configuration, and choose **Send alert event** as the action.
10. In **Inputs → alert**, enter: `{{vars.input.records[0]}}`.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FEBxM9uwKi3kKG6kXPkjM%2F12.png?alt=media&amp;token=65eaf798-d768-493b-a0a5-64f00bd16a45" alt=""><figcaption></figcaption></figure>

11. Save the Playbook.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FbUICscbXruC6riPVt46z%2F13.png?alt=media&amp;token=709fc710-21be-470d-b885-7945df921e6d" alt=""><figcaption></figcaption></figure>

### Create a playbook triggered on alert update

1. Navigate back to your **Collection**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FieMqinzVjxuNfYSlR4Lw%2F14.png?alt=media&amp;token=93f9aec3-329e-4dc8-abb5-5248da546af2" alt=""><figcaption></figcaption></figure>

2. Click **Add Playbook**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FpfobqeB5zZZVm4lvXT1t%2F15.png?alt=media&amp;token=27f6d8fb-7f23-4437-bb05-dbc48176d6ee" alt=""><figcaption></figcaption></figure>

3. Enter a name and click **Create**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FsbffcpRwWVicEkDlbCMh%2F16.png?alt=media&amp;token=8c25d40c-fe03-484c-b8c6-659ca5f5d268" alt=""><figcaption></figcaption></figure>

4. Choose **On Update** as the trigger step.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FvTO8fdJy5svuMNCljCvJ%2F17.png?alt=media&amp;token=5441c509-915e-43b6-b637-b8397c847520" alt=""><figcaption></figcaption></figure>

5. Enter a **Step Name**, select **Alerts** as the resource.
6. Add **Status Is Changed** as the trigger condition.
7. Click **Save**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FmvwhGJzwOOD2jlq4sqkd%2F18.png?alt=media&amp;token=16cd4343-100e-427d-a103-8121ea826c3a" alt=""><figcaption></figcaption></figure>

8. Add the next step and select **Connector** under the **EXECUTE** section.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FHRQB8xcJg2dhjKNXJQCa%2F19.png?alt=media&amp;token=2f6295df-09ac-4a8a-aa39-1ccbf91faff3" alt=""><figcaption></figcaption></figure>

9. Search for `ilert` and select the ilert connector.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2F7mjzGWMUQifbiLVU5Jpe%2F20.png?alt=media&amp;token=a177703c-b133-43f5-a2c3-a344863a63b7" alt=""><figcaption></figcaption></figure>

10. Enter a **Step Name**, select your previously created ilert configuration, and choose **Send alert event** as the action.
11. In **Inputs → alert**, enter: `{{vars.input.records[0]}}`.
12. Click **Save**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fuzde2cbcXqHqhWcjwG8D%2F21.png?alt=media&amp;token=16bb0b1f-d7d9-40a2-9bdb-029762105afb" alt=""><figcaption></figcaption></figure>

13. Save the playbook.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FSapb1Fs8Xa5cSVThLJMo%2F22.png?alt=media&amp;token=716c534d-7143-4d78-b9c9-9c002cfb8184" alt=""><figcaption></figcaption></figure>

## FAQ

#### **Will alerts in ilert be resolved automatically?**

Yes, as soon as a FortiSOAR sends an alert event with field `status.itemValue` value set to `closed`, corresponding alert in ilert will be resolved.

#### **Will alerts in ilert be acknowledged automatically?**

Yes, as soon as a FortiSOAR sends an alert event with field `status.itemValue` value set to `investigating`, corresponding alert in ilert will be accepted.

#### **Can I test the integration?**

Yes. Create a test alert in FortiSOAR and verify that an alert appears in ilert.


---

# 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.ilert.com/integrations/inbound-integrations/fortisoar.md?ask=<question>&goal=<endgoal>
```

`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.
