> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# SIEM & SOAR Overview

> The two ways xorlab connects to a SIEM or SOAR: an outbound event stream over Syslog, and an inbound REST API for automation.

Both integrations are **optional**. xorlab protects email without either of them, and analysts can do everything described here by hand in the web interface.

They rest on two interfaces:

* **Outbound**, over Syslog: verdicts, extracted threat intelligence, and the full analyst and admin audit trail. This is what a SIEM ingests, and what a SOAR uses as a playbook trigger.
* **Inbound**, over HTTPS: the [List API](/latest/api-rule-list-management), which lets a playbook or script change list entries without a human in the web interface.

| Step                                              | Description                                                                                                                                   |
| :------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------- |
| [Connect a SIEM](/latest/integrations-siem)       | **Optional**. Forward the events you care about to Splunk, Microsoft Sentinel, QRadar, Elastic, or any other platform with a Syslog listener. |
| [Automate with a SOAR](/latest/integrations-soar) | **Optional**. Turn those same events into playbook triggers, and let playbooks manage Blacklists, Whitelists, and VIP lists over the API.     |

<Warning>
  **Prerequisites**

  * Complete the [integration](/latest/setup-integration-overview)
</Warning>