Email & Phishing Defense
The inbox is the front door. How well it's locked, and what catches what gets through.
Capture progress
6 of 6 fields captured
Maturity preview · Defined
Email & phishing defense tools
Email platforms, advanced threat protection layers, security gateways, and phish-reporting integrations in use. The F1–F7 posture questions below score how the district configures and operates these tools.
Tool

Platform & protection

Structured tier capture lets the AI advisor surface license rationalization opportunities (e.g., A5 + Mimecast layered duplication).

F2Advanced threat protection capabilities in use

Which platform-native ATP features are actually configured. Captured here is the configuration state — not the licensing state.

If platform-native ATP is your only protection (Field 2), select “None — platform-native only.”

Authentication

F4SPF / DKIM / DMARC

Email authentication records that prevent spoofing of the district's sending domains. DMARC at p=reject is the goal; p=none is observation only.

SPF
Published
All sending sources accounted for
DKIM
Published
Selector configured, signing active
DMARC
p=none
Observation mode — not enforcing

User practices

How staff report suspicious emails, and what happens next.

Cross-references Awareness Field 1 (training program) — they should describe the same provider stack.

F7BEC / impersonation controls

Business Email Compromise specifically targets superintendents, business managers, and finance staff. Wire-fraud and W-2 fraud are the common K-12 outcomes.

Notes