// Security by vertical
SaaS security for edtech
Why edtech has one extra rule
Edtech almost always handles children’s and teenagers’ data, and privacy law gives that data reinforced protection, including the minor’s best interest and, in many cases, a parent’s consent. That adds a layer other SaaS do not have: protecting the data is not enough, you have to prove that only who should (the school, the guardian, the right teacher) reaches the right student’s data.
AI-built edtech grows by school/class, and it is easy for a new endpoint to forget the scope and let a teacher (or worse, a student) see another class’s or school’s data.
What to review in an edtech SaaS
The focus is multi-level isolation (school, class, student) and minors’ data.
- Per-school and per-class isolation: a teacher does not see another school’s class.
- IDOR in a grade, attendance record, message or student datum.
- Role-based access (student, guardian, teacher, coordination) checked on the server.
- Minors’ data with retention, deletion and (where applicable) parental consent.
- Student-teacher chat with moderation and logs that do not expose a minor’s PII.
The sector bar
Beyond privacy law with the rigor of minors’ data, edtech faces the demand of schools and networks (the institutional buyer asks for security proof) and the sensitivity of any incident involving a child. The technical proof that multi-level isolation and student data hold is what RET delivers.
Where RET fits
Risk Review reads the flows that touch student data (grades, attendance, messages) and school/class isolation, and says what to fix before selling to an education network. When the customer requires proof, the Manual Pentest delivers. The Promptbook guides the first pass.
Want to know whether this happens in your system?
Manual pentest for web applications, APIs and apps, from R$9,500, with the Sprint run within 7 business days. We refund 50% if we find no flaw.
Frequently asked questions
Is minors’ data treated differently under privacy law?
Yes. It gets reinforced protection for children and teenagers, with the minor’s best interest and, in many cases, a parent’s consent. That weighs on the access and retention design of your edtech.
What is the worst edtech incident?
A teacher or student reaching another class/school’s data (a multi-level isolation failure or IDOR), or leaking a minor’s data. It is sensitive because it involves children, with high legal and reputational weight.
Does RET handle parental consent?
The formal part (policy, consent) is your legal team’s/DPO’s. RET tests the technical security that underpins it: school/class/student isolation, role-based access and minors’ data protection.
Who runs it at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.
Keep reading
Threat and defense
MCP tool poisoning: how to prevent it
Practical guide
Multi-tenant isolation in SaaS
Threat and defense
Credential stuffing and MFA on the admin panel
Comparison
Firebase vs Supabase: security for AI-built apps
By tool
Security for code generated with Cursor
By city
SaaS security and pentest in Brasília (DF)