Given an incident at a vendor: who is using this app, who needs to know, and what goes out. Answered from the catalog, in seconds.
SIMULATED SCENARIO · no incident at Instructure is claimedDo Not Approve
The pattern is real. PowerSchool, December 2024: A student-information-system vendor's support portal was entered with a subcontractor's credentials (no MFA). Student and teacher records were downloaded from thousands of districts across the US and Canada over ten days. Districts learned which of their schools were exposed from the vendor, weeks later.
Public reporting ↗.
The question every school then asks is the one this page answers first: are we using it, and where?
3
Schools touched
2,800
Students under contract
Do Not Approve
Round-1 verdict today
2026-09-15
Last Drift Sentinel scan
Blast radius · who is using Canvas LMS
From the catalog and the request pipeline. Contacts are roles, resolved to people by SSO in production. Law column comes from the jurisdiction map.
School
Relation
Enrollment
Notify
Privacy law
Sign-in
All schools · 3 schools
Harbor View School
San Diego · United States
In use
700
School applications lead
+ Regional applications manager
Mapped at intake
SSO · confirm at intake
Northside Academy
Chicago · United States
In use
900
School applications lead
+ Regional applications manager
Mapped at intake
SSO · confirm at intake
Riverside Preparatory School
Austin · United States
In use
1,200
School applications lead
+ Regional applications manager
Mapped at intake
SSO · confirm at intake
Send the alert · drafts generated from the data above
Three buttons, three drafts*. Schools, regions, roles and laws are filled from the catalog. The one line you write is what happened.
✓ copied
Editable. In production the Teams post goes to the regional channel, the email to the resolved role
mailboxes, and the ticket is created in your service desk with the affected schools as linked assets.
* These drafts are trained on your voice, not ours. Each region sets its own framing and wording,
and the drafts can draw on school and regional handbooks and guidelines, so what goes out reads like Demo School Group wrote it, because it did.
shaped per region at rollout
What happens next · the agent fleet closes the loop
1 · Alert goes out
Chat post + email to the roles above; a service-desk ticket mirrors it for audit.
2 · Catalog holds the line
Canvas LMS moves to Restricted · under review in the catalog, flagged for every affected school. A human decides; nothing auto-disables. (How each school and region sees the catalog, and which role sees which features, is a decision to take with NA.)
3 · Drift Sentinel re-vets
The vendor's policy is re-read and re-scored against the same 19 questions. Verdict change → new alert, quote attached.
4 · Weekly watch
Production runs this check on a schedule against the whole catalog: new incident feeds in, "who is using it" comes out, ticket opens. Agent Fleet →
Scenario is simulated for the demo; no security incident at this vendor is claimed. Schools, app lists and enrollments are demo data. Contacts are roles, not people. No student data anywhere in the system.
Add an application
Type any app name. The Enrichment Engine builds its catalog card and the Application Library reviews the vendor — live.