> ## 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.
# How to Activate the Configuration
xorlab Security Platform has different configuration files that are treated differently. Some are
hot-reloaded and will get active right after saving the change, some require a restart of a
component.
**Non-expert changes do not require a restart**
All changes outside of the Expert settings do not require a restart and will get automatically
active after one minute (for example, adding a new entry to a list on the [**Lists**](/9.0/lists)
page).
To change the Expert settings, click the tiles icon next to your account name, click the **Admin**
icon in the displayed menu, and then click the **Expert** tile as described in
*[Expert Editor](/9.0/expert-editor)*.
## Configuration files
The following table lists all xorlab Security Platform configuration files from the Expert settings
and how changes to them will get active. More specific entries overwrite the “required action” for
wildcard (`*`) entries.
| File | Required action |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `activeguard/core/active_guard.yml`:
- `rules`
- `trustedMTAProfiles`
- `pipelines`
- `pipelineTypeConfig`
- `ruleListUpdateCron`
- `ruleListUpdateOnStartup`
- `ruleListUpdateDisabled`
- `scanSources/smtp/handler/*`
- `smtpConfiguration`
- `additionalReceivedFromPatterns`
- `pdfAnalysis`
- `emailReporting`
`activeguard/core/logback-audit.xml`
`activeguard/core/logback.properties`
`activeguard/core/rule_sets/*`
`activeguard/mta/logback-audit.xml`
`auth/auth/*`
`shared/*`
`xcc/backend/logback-audit.xml`
`xcc/backend/logback.properties`
`xcc/backend/xcc.yml`:
- `misclassificationSubmission`
- `roleToPermissionMappings`
- `deliveryStatus`
`monitored_mta/*`
`monitoring/* except grafana.ini` | None, automatically activated after one minute |
| `activeguard/core/active_guard.yml`:
`all properties not mentioned above, including:`
- `serviceProviders`
- `scanSources`
`activeguard/core/startup_cfg/*`
`activeguard/db/*`
`activeguard/mta/audit/audit.yml`
`activeguard/rspamd/*`
`activeguard/core/startup_cfg/spamhaus_[hbl_]license.txt` | Restart MTAs. For all MTAs:
1. SSH connect to the MTA
2. `cd /etc/xorlab/activeguard`
3. `docker compose down && docker compose up -d` |
| `xcc/backend/xcc.yml`: all properties not mentioned before
`xcc/web/*` | Restart XCC:
1. SSH connect to the XCC
2. `cd /etc/xorlab/xcc`
3. `docker compose down && docker compose up -d` |
| `monitoring/grafana/grafana.ini` | Restart Monitoring on MTAs. For all MTAs:
1. SSH connect to the MTA
2. `cd /etc/xorlab/monitored`
3. `docker compose down && sleep 2 && docker compose up -d` |
**xorlab Security Platform (SaaS)**
Restarting components is only possible for on-premise deployments. If you are using xorlab Security
Platform (SaaS), please contact [support@xorlab.com](mailto:support@xorlab.com) to do the restart. Future releases will support
more configuration hot-reload and thereby make this obsolete.