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

# Default Static Policies

These policies are active by default and put emails into quarantine unless disabled via a [profile](https://docs.xorlab.com/9.0/actions-rules-and-profiles.md#profiles). They are high-confidence filter rules that are triggered when specific criteria are met:

| Static policy (`FILTER` rule) | Description |
| :- | :- |
| `FILTER_executable` | This rule is triggered when an executable file is found in attachments |
| `FILTER_flash` | This rule is triggered when a Flash script is found in attachments |
| `FILTER_iso` | This rule is triggered when an ISO file is found in attachments |
| `FILTER_legacy_archive` | This rule is triggered when a legacy archive file is found in attachments |
| `FILTER_shortcut` | This rule is triggered when shortcuts are found in attachments |
| `FILTER_windows_script` | This rule is triggered when a Windows script is found in attachments |
| `FILTER_office_dde` | This rule is triggered when Microsoft Office documents containing Dynamic Data Exchange (DDE) fields are detected in attachments |
| `FILTER_office_external_frame` | This rule is triggered when Microsoft Office documents containing external frame(s) are detected in attachments |
| `FILTER_office_external_webvideo` | This rule is triggered when Microsoft Office documents containing external videos are detected in attachments |
| `FILTER_wwwdata_sender` | This rule is triggered when the sender’s FROM address is matched by this regex: `.*www-data.*` |
| `FILTER_UNTRUSTED_new_file_type_from_unknown_sender` | This rule is triggered when a file containing an untrusted/new file extension is sent from a new sender |

> [!NOTE]
>
> The file extensions blocked by each static policy are documented in
> [Detection Defaults → Static policy file extensions](https://docs.xorlab.com/9.0/detection-defaults.md#static-policy-file-extensions).
> Password required.

Available states for the `FILTER_` rules are `PASSIVE`, `DISABLED`, or `ACTIVE`. If you want to disable a particular rule, we recommend assigning the `PASSIVE` state to it, e.g.:

```
FILTER_iso_state=PASSIVE
```

> [!WARNING]
>
> **Low-trusted senders still blocked**
>
> Even if the above static policies (filters) are disabled, xorlab will still block the majority of their associated file types because of the malware rules that depend on trust, e.g., the malware rules will still block shortcuts/scripts/flash/legacy archives/ISOs when they come from low- or untrusted senders.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.