Hands-on labs that run entirely on school hardware. No internet required. Nothing a student does can leave the classroom. Built for teachers who have never taught security before.
Students want to try things without breaking anything. Teachers want lesson plans that just work. Schools want it safe, private, and easy to support. All three are already handled.
A sandbox that resets every time. Try something wrong, nothing breaks. Try something right, they see it happen.
Lesson plans with slides, answer keys, and a way to see who is stuck. No security background needed to teach it.
One install for the whole lab. No cloud account, no data leaving the building, no per-student subscription.
A curriculum, not a toolbox. Each lesson builds on the one before it. Everything runs locally. Everything has an answer key.
Read a system log. Spot the difference between a successful sign-in and a failed one. Talk about what a computer remembers.
Take a noisy log and reduce it to just the failed attempts. Students learn that finding a signal is a skill.
Count failures by IP. First place students see a pattern emerge from raw data. Conversation about what “suspicious” means.
Feed the output of one tool into another. Students see how professional analysts build small pipelines instead of doing everything by hand.
Read the header of a real binary. Architecture, entry point, sections. Gentle first look at how programs are built.
Students write a small parser for a log format of their choice. First real code they ship. Published privately to the class.
Every decision we've made for the schools program starts with the same question: what happens if a student does the unexpected?
Lessons run entirely on the school's own network. Nothing a student does reaches outside the classroom. No cloud account needed.
Each lesson runs in an isolated environment. If a student breaks something, they press Reset. It comes back exactly as it started.
Student work is stored locally on the school's own machines. No analytics, no telemetry, no data sent to us. FERPA and COPPA-friendly by default.
The teacher decides what capabilities are available in a lesson. Students cannot reach beyond the current lab, even if they try.
School-level labs are defensive and educational. Offensive security is taught as a concept, not practiced as a tool. No scanners, no exploitation, no C2.
Lessons are files on disk. Capabilities follow an open spec. A district can move to another platform without losing their curriculum.
We're working with a small number of pilot schools and CTE programs. If you teach security, run a lab, or coordinate a district program, we'd like to hear from you.