# (L1) Ensure mail transport rules do not whitelist specific domains

No mail flow rule sets the spam confidence level to -1 for mail from specific sender domains.

Source: https://maester.dev/docs/tests/CIS.M365.6.2.2

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/jeremyfinney-lgtm" title="jeremy finney · Original author"><img src="https://github.com/JeremyFinney-lgtm.png" alt="jeremy finney" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/jeremyfinney-lgtm">jeremy finney</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/cis">CIS</a> · Exchange Online · Mail flow · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId CIS.M365.6.2.2
```

## Overview

No mail flow rule sets the spam confidence level to -1 for mail from specific sender domains.

A spam confidence level of -1 tells Exchange Online to deliver the message without spam filtering. If the rule matches a sender domain, anyone who can spoof that domain, or who compromises it, sends mail straight to your users, with the same trust as an internal sender.

If a business exception is necessary, CIS says to whitelist the domain only when inbound mail from that domain originates from a specific IP address, and to document and regularly review the exception. The CIS PowerShell audit flags every rule that combines `SenderDomainIs` with `SetSCL -1`; this check does not verify an IP restriction or exception documentation, so assess each flagged rule against those conditions. Prefer fixing the cause of false positives, for example by configuring SPF, DKIM and DMARC for the partner domain.

#### Remediation action

1. Sign in to the [Exchange admin center](https://admin.exchange.microsoft.com).
2. Go to **Mail flow** > [**Rules**](https://admin.exchange.microsoft.com/#/transportrules).
3. Open each rule that is listed in the test result and remove the action **Set the spam confidence level (SCL) to Bypass spam filtering**, or delete the rule.

#### Related links

* [Exchange admin center - Mail flow rules](https://admin.exchange.microsoft.com/#/transportrules)
* [Use mail flow rules to set the spam confidence level](https://learn.microsoft.com/exchange/security-and-compliance/mail-flow-rules/mail-flow-rule-actions)
* [Create safe sender lists in Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/create-safe-sender-lists-in-office-365)
* [CIS Microsoft 365 Foundations Benchmark v7.0.0 - 6.2.2](https://www.cisecurity.org/benchmark/microsoft_365)

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | CIS.M365.6.2.2 |
| Severity | Medium |
| Suite | CIS |
| Product | Exchange Online |
| Feature | Mail flow |
| Area | Email and collaboration protection |
| Resource type | MailFlowRule |
| User impact | Low |
| Implementation cost | Low |
| MITRE ATT&CK | T1566 Phishing, T1684.002 Email Spoofing |
| Supports benchmark | CIS Microsoft 365 Foundations Benchmark (version 7.0.0), requirement 6.2.2 |
| Benchmark level | L1 |
| Benchmark profiles | E3 Level 1 |
| Supports controls | cis-m365:6.2.2, nist-800-53-r5:SI-8 |
| PowerShell test | [Test-MtCisTransportRulesNoDomainAllowList](https://github.com/maester365/maester/blob/main/tests/cis/Test.CIS.M365.6.2.2.ps1) |
| Services | ExchangeOnline |

</details>

## Source

- Test: [`tests/cis/Test.CIS.M365.6.2.2.ps1`](https://github.com/maester365/maester/blob/main/tests/cis/Test.CIS.M365.6.2.2.ps1)
- Documentation: [`tests/cis/Test.CIS.M365.6.2.2.md`](https://github.com/maester365/maester/blob/main/tests/cis/Test.CIS.M365.6.2.2.md)
