Anti-phishing policies in Microsoft Defender for Office 365 are configured with impersonation and spoof protection
ZTA.41033 is in Maester 3.0.0-preview and not in the stable 2.3.0 release yet. It will be in the next stable release. To use it now, install the preview:
Install-Module Maester -AllowPrerelease -ForceHow to get the preview, and go backUse the preview in GitHub Actions
Overview
Section titled “Overview”A threat actor who registers a domain that looks like the customer’s domain, or who spoofs the From address of an executive, can deliver a payment-redirection or credential-harvesting message that bypasses standard sender authentication checks. Without impersonation protection turned on, the recipient sees a familiar name, opens the message, follows the link, and either submits credentials or approves a wire transfer. The Microsoft Defender for Office 365 anti-phishing policy provides user impersonation protection for named high-value users, domain impersonation protection for the customer’s own and partner domains, mailbox intelligence that learns each recipient’s normal contacts, and spoof intelligence that enforces SPF, DKIM, and DMARC outcomes. Impersonation lists should include board members, executives, finance, and key partners. This check confirms that at least one enabled anti-phishing policy is configured beyond the defaults with impersonation and spoof controls so these techniques are blocked at the front door.
Remediation
Section titled “Remediation”To configure an anti-phishing policy with impersonation and spoof protection:
- Sign in to Microsoft 365 Defender as a Global Administrator or Security Administrator.
- Navigate to Email & collaboration > Policies & rules > Threat policies > Anti-phishing.
- Select an existing custom policy or click Create to add a new one.
- Under Phishing threshold & protection, enable Spoof intelligence, Mailbox intelligence, and Mailbox intelligence protection.
- Enable Enable users to protect and add key executives, board members, and finance users to the protected user list.
- Enable Enable domains to protect, include your own domains, and optionally add partner domains.
- Set Phishing email threshold to 3 - More aggressive (Standard) or 4 - Most aggressive (Strict).
- Set all quarantine actions (spoof, impersonation, mailbox intelligence) to Quarantine and select the AdminOnlyAccessPolicy quarantine policy.
- Enable Apply DMARC policy and set DMARC quarantine action to Quarantine and DMARC reject action to Reject.
- Assign the policy to recipients via an enabled rule.
- Anti-phishing protection in Microsoft Defender for Office 365
- Configure anti-phishing policies in Microsoft Defender for Office 365
- Recommended settings for anti-phishing policies
- Spoof intelligence insight
- Set-AntiPhishPolicy
Run it
Section titled “Run it”The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:
Install-Module ZeroTrustAssessment -Scope CurrentUserConnect-MaesterInvoke-Maester -Pack ZTA -SkipBuiltInLeave out -SkipBuiltIn to run Maester’s own checks in the same run.
About this check
| Severity | High |
| Effort to fix | Low |
| Impact on users | Low |
| Pillar | SecOps |
| Category | Email and collaboration security |
| Product | Defender |
| Feature | Anti-phishing |
| Area | Email and collaboration protection |
| ATT&CK | T1566 Phishing, T1684.001 Impersonation, T1684.002 Email Spoofing |
| Licence | ATP_ENTERPRISE |
| Tenant | Workforce |
Product, feature, area and ATT&CK are Maester’s: the assessment does not record them, so Maester keeps them in the pack’s taxonomy.json.
A Microsoft check, part of the Zero Trust Assessment pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, MIT licence.
About this check
- Severity
- High
- Effort to fix
- Low
- Impact on users
- Low
- Product
- Defender
- Feature
- Anti-phishing
- Area
- Email and collaboration protection
- Pack
- Microsoft Zero Trust Assessment