K–12 Email Security Vendor Evaluation Checklist
Use the same scenarios and evidence requirements for every vendor so the district can compare operational fit instead of presentation quality.

What this guide helps you do
Leave with a workable next step.
- Score evidence observed during a pilot, not promises alone.
- Include student coverage, implementation, retention, support, and growth in cost.
- Require roles, audit history, acceptance criteria, and rollback for consequential actions.
Use a consistent scoring scale
Assign an owner and required evidence to every high-priority requirement. Weight protection, investigation, response, privacy, and operational fit more heavily than cosmetic preferences.
Protection coverage
- SPF, DKIM, DMARC, ARC, alignment, and forwarding context
- Display-name, protected-person, reply-domain, and lookalike impersonation
- Links, redirects, shortened URLs, newly observed domains, and QR codes
- Documents, archives, scripts, images, executables, and encrypted content boundaries
- Inbound, internal, and outbound scope stated precisely
- False-positive controls with reason, owner, scope, and expiration
Investigation and response
- Human-readable verdict evidence
- Search across sender, recipient, subject, message ID, URL, file, and campaign
- Quarantine review and safe release
- Related-message discovery and provider-side actions
- Role-based authorization and confirmation for consequential changes
- Durable activity, decision, and delivery receipts
Implementation, privacy, and service
- Documented mail-flow design, pilot, acceptance tests, rollback, and cutover owner
- Data fields, location, encryption, retention, deletion, subprocessors, and support access
- Identity lifecycle, SSO, administrator roles, emergency access, and audit export
- Monitoring, escalation, after-hours handling, incident communication, and service boundaries
- Portability and exit plan for data, routing, integrations, and DNS
Commercial comparison
| Cost input | Record for every proposal |
|---|---|
| Population | Staff, students, shared mailboxes, groups, aliases, guests |
| Usage | Message volume, storage, retention, API or response actions |
| Services | Implementation, migration, training, support, premium modules |
| Term | Minimum, renewal, increases, multi-year discount, termination |
| Growth | Enrollment, domains, acquisitions, summer and opening-week peaks |
Review every core Guard protection, guided implementation, student inclusion, annual minimum, and district evaluation path.
Sources and further reading
Primary guidance and related K12First material used to review this resource.
This resource provides general operational guidance. Apply changes through your district’s authorized security, privacy, legal, and change-management processes.

