Description:
Verifies that SPF policies are published for all domains.
Why:
An adversary may modify the "FROM" field of an email such that it appears to be a legitimate email sent by an agency, facilitating phishing attacks. Publishing an SPF policy for each agency domain mitigates forged "FROM" fields by providing a means for recipients to detect emails spoofed in this way. SPF is required for FCEB departments and agencies by Binding Operational Directive (BOD) 18-01, "Enhance Email and Web Security".
Configured: SPF policies are published for all domains.
Not Configured: SPF policies are not published for all domains.
Scoring: Contributes up to 1 point to the Posture Recommendations score.
Category: Exchange
Microsoft Licensing: Works with Basic licensing
Secure Score Impact: YES — Microsoft publishes the improvement action "Ensure that SPF records are published for all Exchange Domains".
Remediation in Augmentt: No in-product remediation — remediate in the Microsoft admin portals.
Compliance Frameworks:
CISA SCuBA — MS.EXO.2.2
CIS Microsoft 365 Benchmark v6 (Level 1) — 6.2.1
CIS Microsoft 365 Benchmark v7 (Level 1) — 6.2.1
Microsoft documentation:
_KB status: new — this check is not yet documented in the knowledge base._
_Source: Sourced from the open-source Maester project and extended by Augmentt with multi-tenant support, compliance mapping and in-product remediation. Check ID CISA.MS.EXO.2.2 (module 1026)._
Sourced for this page:
Category — Maester test catalog (maester.dev/docs/tests) — test is graded against the "exchange" tier, so it evaluates a Microsoft Entra ID setting
Secure Score — Microsoft Learn publishes the Secure Score improvement action "Ensure that SPF records are published for all Exchange Domains".
Draft metadata — apply these as Stonly tags in the console, then delete this block. The Stonly API cannot set tags, so they are recorded here instead.
Tags: posture-check · compliance-audit · Exchange Online · M365 Basic · CIS M365 v6 L1 · CIS M365 v7 L1 · CISA SCuBA