SCHOOL CONTACT

Tag: guardian alias

  • Rebuilding School Communities After Wildfire Displacement

    The Challenge

    Following a wildfire, residents of a single neighborhood are displaced to a nearby, overwhelmed county. Parents face re-enrolling their children in an unfamiliar school district while managing insurance claims and housing logistics. Without a unified system, information sharing is fragmented, and children risk being separated from their existing peer groups during a high-stress transition.

    The School Contact Solution

    The same retire-never-recycle guardian alias used to defeat phishing attacks also simplifies this transition. Displaced parents use their existing verified guardian aliases to coordinate with the receiving school and with one another.

    • Coordinated enrollment — because each student’s identity anchor is already linked to their guardian’s alias, a whole group of neighborhood families can independently enroll their children at the same receiving school, with the registrar verifying each family’s guardianship attestation.
    • Real-time information loop — a verified channel delivers authenticated district updates, while a separate parent-to-parent channel — never conflated with the school’s own broadcast alias — lets neighbors share transportation and housing information.
    • Continued peer connection — because each student’s identity anchor persists and is never reassigned, children can keep reaching established classmates through existing aliases after relocating, with no new accounts and no lost history.

    Demonstrates the relationship layer linking guardian and student identity anchors, and the persistence-without-reassignment principle at the center of the whole architecture.

  • Stopping a Phishing Attack Before It Starts

    The Challenge

    A phishing campaign targets parents at a local high school. Bad actors send SMS messages and emails spoofing the school’s branding, claiming an active emergency and demanding a “transportation fee” to safely bus students to a reunification site.

    The School Contact Solution

    Under School Contact, the attack fails structurally rather than depending on parents noticing something is wrong. Every domain the district uses carries the mandatory email-authentication baseline — DNSSEC, SPF, DKIM, and enforced DMARC — so a spoofed message impersonating the district’s domain simply doesn’t deliver as genuine mail. The district pushes an authenticated, one-way broadcast confirming the earlier messages were fraudulent.

    Because parents communicate using their retired-never-recycled guardian alias, the school’s system can check any inbound reply against the relationship layer — confirming both that the alias is active and that the sender currently holds guardianship rights for a specific enrolled student — before treating it as trusted. And because the verified channel was never publicly browsable, it was never a target the attackers could spoof in the first place.

    Demonstrates the domain security baseline, the retire-never-recycle guardian alias policy, and query-response verification working together against a real attack pattern.

  • How Aliases Protect Students and Parents from Phishing

    Earlier drafts of the Contact Initiative imagined a public, browsable directory where anyone could look up a verified teacher or administrator. Review identified an obvious problem: a browsable list of every verified educator in the country is also a ready-made target list for harassment.

    Query-Response, Not Browsable

    Version 5 replaces the browsable directory with query-response verification. A relying party submits a specific claimed identity — “is this person currently a teacher at this school?” — and receives a confirm or deny answer, rate-limited to prevent bulk scraping. This preserves the entire anti-phishing benefit of the original idea while removing the enumeration risk.

    Aliases That Can Be Replaced Without Losing Identity

    Institution-issued aliases follow role-based, human-readable patterns and can be rotated or reissued at any time without affecting the underlying identity anchor or its attestation history. A compromised or leaked alias can simply be retired and replaced — no loss of identity continuity, and a much smaller practical target for spear-phishing.

    A Non-Negotiable Security Baseline

    Every domain issued under the Contact Initiative — production or sandbox — is proposed to carry DNSSEC and registry lock to prevent hijacking, enforced SPF, DKIM, and DMARC with a reject policy to stop spoofed mail from delivering as genuine, and a published, cryptographically signed list of real Contact Initiative domains so relying parties can spot look-alikes.