> 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/sekoia.md).
# Sekoia Integration
Forward Sekoia alerts to ilert via the ilert integration in Sekoia playbooks to notify on-call teams and centralize security incident response.
[Sekoia](https://www.sekoia.com/) is a SaaS SOC platform that combines SIEM, SOAR, and CTI capabilities to detect, investigate, and respond to threats. Connecting Sekoia to ilert lets you trigger ilert alerts from Sekoia playbooks so security findings reach the right on-call team and are tracked through to resolution.
## In ilert: Create a Sekoia alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Sekoia**, 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**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
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, copy the generated **integration key** and **Sekoia URL**. You will use both in the next steps.
## In Sekoia: Connect the ilert integration
1. In Sekoia, open **Integrations** from the sidebar.
2. Search for **ilert** and select the ilert integration from the results.
3. Click **Show accounts**, then **Connect an account**.
4. Fill in the **Add new account** form:
* **Give a name to this account**: a label of your choice (e.g. `ilert account`).
* **Integration Key**: the integration key from your ilert alert source.
* **Integration Url**: `https://api.ilert.com/api/v1/events/sekoia`.
Click **Add account**.
## In Sekoia: Use the Trigger Alert action in a playbook
1. Open or create a playbook in Sekoia.
2. Add the **Trigger Alert** action from the ilert integration.
3. In the **Account** tab, select the ilert account you just connected.
4. Configure the action input and save the playbook.
Whenever the playbook runs the **Trigger Alert** action, a new alert is created on the corresponding Sekoia alert source in ilert.
## FAQ
#### **Will alerts in ilert be resolved automatically?**
Yes. If a Sekoia event is sent with the `status` key set to `resolved` or `closed`, the corresponding ilert alert is resolved automatically.
#### **Will alerts in ilert be acknowledged automatically?**
Yes. If a Sekoia event is sent with the `status` key set to `acknowledged`, the corresponding ilert alert is acknowledged automatically.
#### **Can I connect multiple ilert alert sources to Sekoia?**
Yes. Add an additional connected account in the Sekoia ilert integration for each alert source, using that source's integration key.
---
# 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/sekoia.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.
