EdTech

Learning platforms, assessment engines, and student-data pipelines tested with kid-safety, FERPA scope, and LTI trust boundaries front and centre.

Three named threats we test for

1. 01

   Assignment-submission race conditions

   Submission, regrade, and late-policy endpoints raced against each other to overwrite grades, replay submissions, or bypass cutoff windows.

2. 02

   LTI integration trust abuse

   LTI 1.3 launches and Deep Linking flows tested for over-trusting consumer claims, signature reuse, and role escalation across tenants.

3. 03

   Grade-tampering via stale session tokens

   Long-lived tokens, sticky roles, and proctoring side-channels tested for paths that let a student or insider rewrite the record.

1. 01

   Scope and threat-model

   Engagement lead walks the platform with your engineering and student-safety owners. Outcome is a written threat model that names FERPA scope.

2. 02

   Manual exploitation

   Researchers attack LTI launches, submission flows, and grade pipelines by hand. Tools assist, they do not lead.

3. 03

   Chained-finding write-up

   Every report shows the path from entry to student-data impact, with reproduction steps a developer can replay against a staging tenant.

4. 04

   Retest and sign-off

   Fixes are retested against the original exploit chain. CISO gets a signed letter that fits into the district or institution audit file.