Skip to main content
Version: 3.0.0-preview

CISA.MS.EXO.11.1 - Impersonation protection checks SHOULD be used.

Overviewโ€‹

Impersonation protection checks SHOULD be used.

Rationale: Users might not be able to reliably identify phishing emails, especially if the FROM address is nearly indistinguishable from that of a known entity. By automatically identifying senders who appear to be impersonating known senders, the risk of a successful phishing attempt can be reduced.

Remediation actionโ€‹

  1. Sign in to Microsoft 365 Defender.
  2. In the left-hand menu, go to Email & Collaboration > Policies & Rules.
  3. Select Threat Policies.
  4. From the Templated policies section, select Preset Security Policies.
  5. Under Standard protection, slide the toggle switch to the right so the text next to the toggle reads Standard protection is on.
  6. Under Strict protection, slide the toggle switch to the right so the text next to the toggle reads Strict protection is on.

Note: If the toggle slider in step 5 is grayed out, click on Manage protection settings instead and configure the policy settings according to Use the Microsoft 365 Defender portal to assign Standard and Strict preset security policies to users | Microsoft Learn.

Test Metadataโ€‹

FieldValue
Test IDCISA.MS.EXO.11.1
SeverityHigh
SuiteCISA
ProductExchange Online
Related productsDefender
FeatureAnti-phishing
AreaEmail and collaboration protection
Resource typeTenant
User impactLow
Implementation costLow
MITRE ATT&CKT1566 Phishing, T1684.001 Impersonation
Supports benchmarkCISA SCuBA Secure Configuration Baselines for Microsoft 365 (version ScubaGear main, 2026-10-11), requirement MS.EXO.11.1
CriticalitySHOULD
Upstream requirementMoved to MS.SECURITYSUITE.2.1v1 (was MS.EXO.11.1v1)
Supports controlscisa-scuba:MS.EXO.11.1, nist-800-53-r5:SI-8
PowerShell testTest-MtCisaImpersonation
ServicesExchangeOnline, Graph, SecurityCompliance
Compatible licensesATP_ENTERPRISE

Sourceโ€‹