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

# Important Operational Resources

> Support address, release announcements, status page, and the contact for reporting a vulnerability.

| Topic                     | Resource                                                                    |
| :------------------------ | :-------------------------------------------------------------------------- |
| Support address           | [support@xorlab.com](mailto:support@xorlab.com)                             |
| Release announcements     | [Subscription form](https://share.hsforms.com/1yOHcQkvBQiOiO3j9qwv1Yg2u2pk) |
| Status page               | [Status page](https://status.xorlab.com/)                                   |
| Reporting a vulnerability | [security@xorlab.com](mailto:security@xorlab.com)                           |
| Data protection           | [List of Data Sub-Processors](/latest/data-third-party-subprocessors)       |

## Support address

If you have any questions or need our assistance, contact us via **[support@xorlab.com](mailto:support@xorlab.com)**.

## Mailing list & release announcements

Subscribe to xorlab release and security announcements here: [Subscription form](https://share.hsforms.com/1yOHcQkvBQiOiO3j9qwv1Yg2u2pk). We strongly recommend to subscribe there to be informed about important updates.

<Accordion title="Example release announcement">
  <img src="https://mintcdn.com/xorlab/IcncXAkAdr97zV2Y/latest/assets/mailing-list.png?fit=max&auto=format&n=IcncXAkAdr97zV2Y&q=85&s=c5f682cae3a866c43a918089ffc4df54" alt="Release Announcements mailing list" width="857" height="1035" data-path="latest/assets/mailing-list.png" />
</Accordion>

## Status page

Here you can find the xorlab status page: [Status page](https://status.xorlab.com/). You can subscribe there to get informed about scheduled maintenance and incidents.

It includes the status of xorlab SaaS instances, as well as xorlab services used by on-premises deployments.

Note that the `xcc - GUI` status information is for SaaS customers only, as well as `Rollout of xorlab Security Platform x.x.x` announcements.

## Data protection

Which external parties may handle data in your deployment is listed in [List of Data Sub-Processors](/latest/data-third-party-subprocessors). For what the platform sends out while analyzing email, and what it keeps afterwards, see [Data Sent to External Services](/latest/data-to-external-services) and [Data Storage](/latest/data-storage).

## Vulnerability reports

Send security vulnerability reports to **[security@xorlab.com](mailto:security@xorlab.com)**. This address can be used for all xorlab’s products, services, and websites. We can accept only security vulnerability reports at this address.

When we receive a security vulnerability report, we will evaluate it. And, if we agree it is a vulnerability, we’ll work to fix it and release the fix in a timeframe that matches the severity.

Let us know if you would like credit for discovering the issue. We can cite you as the discoverer if we weren’t previously aware of the issue.