Email security built for school teams

See the risk.
Understand why.
Act with confidence.

Guard helps K–12 technology teams inspect inbound email, explain suspicious signals, hold risky messages, and coordinate a reviewed response.

Guided evaluations are planned around each district’s mail environment and requirements. Already using Guard? Sign in.

Sender authenticationAttachments and QR codesLink inspectionImpersonation signalsCampaign context

From message to decision

Email security should explain itself.

A warning is useful only when the person receiving it understands what happened and what to do next. Guard brings the evidence, decision, message history, and response workflow together.

Every organization stays inside its own tenant boundary, with roles for platform operators, district administrators, analysts, and delegated managers.

Layered protection

Look at the whole message—not one signal.

Guard combines independent checks so school teams can see both the verdict and the evidence behind it.

Sender and authentication

Evaluate SPF, DKIM, DMARC, ARC, alignment, lookalike domains, display names, aliases, and protected people.

Content and attachments

Inspect message structure, archives, documents, images, QR codes, and supported scripts with layered malware and content analysis.

Links at delivery and click

Analyze destinations, follow bounded redirect chains, and present a clear interstitial when a link needs caution or should be blocked.

Impersonation and BEC

Protect high-risk identities and surface reply-domain, payment-change, and vendor-context signals in an explainable decision.

Quarantine and investigation

Hold suspicious mail, preserve decision evidence, support reviewed release, and connect related messages without exposing cross-tenant data.

Reports and campaign context

Bring user reports, similar-message discovery, incident context, and authorized provider response into one auditable workflow.

A clear operating loop

Detect. Explain. Review. Respond.

Guard keeps consequential actions visible and reviewable from intake through resolution.

  1. 01
    Inspect

    Analyze message identity, content, attachments, links, and related activity.

  2. 02
    Explain

    Translate technical evidence into a reasoned verdict and visible policy match.

  3. 03
    Review

    Give authorized staff the message context, quarantine state, and recommended next step.

  4. 04
    Respond

    Record reviewed release, removal, restoration, sender blocks, and incident activity with durable receipts where available.

Built for the people on call

One workspace for the jobs behind the alert.

Start from an overview, then move into messages, quarantine, investigations, protected people, policies, integrations, reports, and incidents without losing the thread.

  • Plain-language decisionsSee what was found and why it matters.
  • Guided setupStage identity, domains, protected people, providers, and mail routing in reviewable steps.
  • Tenant-aware operationsKeep data, roles, policy, and response scoped to the customer.

Plan the right rollout

Start with a guided district evaluation.

Guard activation is reviewed against the district’s mail platform, domains, identity configuration, routing, support needs, and agreed operating boundaries.

Current evaluation path Google Workspace environment review Domain and administrator readiness Staged mail-flow validation Acceptance and rollback planTalk with the Guard team

Guard questions

What school teams ask first.

Does Guard replace Google Workspace?+

No. Guard is an email-security layer that works with the district’s mail environment and administrator workflows.

Can administrators see why a message was held?+

Yes. Guard is designed to preserve the matched policy, relevant signals, verdict, and review state so authorized staff can understand the decision.

Does Guard inspect links and attachments?+

Yes. Guard combines URL, attachment, authentication, content, and sender-identity checks. Exact coverage depends on file type, destination behavior, and the approved customer configuration.

How does a district get started?+

Begin with an environment and readiness review. K12First then plans identity, domains, protected people, mail routing, canaries, acceptance, and rollback with the district team.

K12First Guard

Bring one suspicious message. Leave with a clearer picture.

See how Guard turns technical evidence into a focused investigation and reviewed response.

Request an evaluation Review our Trust Center