Security checks / Check reference / Email security

Phish SCuBA Exo Phishing Protections

High Severity Microsoft 365 security check in the Email security domain.

SCUBA/CISA baseline check: Exchange Online anti-phishing protection configuration Verifies impersonation protection, mailbox intelligence, and spoof settings Weak impersonation and sender validation raise BEC (Business Email Compromise) and payment‐fraud risk Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityEmail securitySCuBA MS.DEFENDER.1.1v1

Check summary

Severity

High

Domain

Email security

Rank in domain

Frameworks

What this check verifies

SCUBA/CISA baseline check: Exchange Online anti-phishing protection configuration Verifies impersonation protection, mailbox intelligence, and spoof settings

Why it matters

Weak impersonation and sender validation raise BEC (Business Email Compromise) and payment‐fraud risk

How to fix it

Tune impersonation/sender controls; prioritize impersonation protections for executives and finance roles

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "Phish SCuBA Exo Phishing Protections" (source: https://senserva.com/check/emphishscubaexophishingprotections.html):
- Verifies: SCUBA/CISA baseline check: Exchange Online anti-phishing protection configuration Verifies impersonation protection, mailbox intelligence, and spoof settings
- Severity: High; domain: Email security
- Risk: Weak impersonation and sender validation raise BEC (Business Email Compromise) and payment‐fraud risk
- Remediation guidance: Tune impersonation/sender controls; prioritize impersonation protections for executives and finance roles
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS; SCuBA MS.DEFENDER.1.1v1, MS.DEFENDER.1.2v1, MS.DEFENDER.1.3v1, MS.DEFENDER.1.4v1, MS.DEFENDER.1.5v1, MS.DEFENDER.2.1v1, MS.DEFENDER.2.2v1, MS.DEFENDER.2.3v1, MS.DEFENDER.3.1v1, MS.DEFENDER.4.1v2; MCSB LT-1, LT-3
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISSCuBA MS.DEFENDER.1.1v1 SCuBA MS.DEFENDER.1.2v1 SCuBA MS.DEFENDER.1.3v1 SCuBA MS.DEFENDER.1.4v1 SCuBA MS.DEFENDER.1.5v1 SCuBA MS.DEFENDER.2.1v1 SCuBA MS.DEFENDER.2.2v1 SCuBA MS.DEFENDER.2.3v1 SCuBA MS.DEFENDER.3.1v1 SCuBA MS.DEFENDER.4.1v2MCSB LT-1MCSB LT-3

References

learn.microsoft.com: /defender-office-365/anti-phishing-policies-mdo-co...learn.microsoft.com: /security/benchmark/azure/mcsb-logging-threat-dete...www.cisa.gov: /resources-tools/services/m365-exchange-online...

Related Email security checks

Link SCuBA Exo Link Protection Malware SCuBA Exo Malware Scanning Spam SCuBA Exo Inbound Anti Spam Protections

Common questions

What does the Phish SCuBA Exo Phishing Protections check verify?

SCUBA/CISA baseline check: Exchange Online anti-phishing protection configuration Verifies impersonation protection, mailbox intelligence, and spoof settings It is a High Severity check in the Email security domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Phish SCuBA Exo Phishing Protections finding?

Tune impersonation/sender controls; prioritize impersonation protections for executives and finance roles Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, including SCuBA policy MS.DEFENDER.1.1v1, MS.DEFENDER.1.2v1, MS.DEFENDER.1.3v1, MS.DEFENDER.1.4v1, MS.DEFENDER.1.5v1, MS.DEFENDER.2.1v1, MS.DEFENDER.2.2v1, MS.DEFENDER.2.3v1, MS.DEFENDER.3.1v1, MS.DEFENDER.4.1v2, and MCSB controls LT-1, LT-3. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.