Security & privacy
An overview of how CyberLab is designed to protect schools. Detailed documentation is available on request.
Activities must only be performed within authorized CyberLab environments.
Each school is provisioned as its own organization. Every record — users, classes, attempts and responses — carries an organization identifier, and pages only show records from the signed-in user’s organization.
We collect the minimum information needed for learning: name, school email, class membership and lab activity. See the privacy notice for details and how to request export or deletion.
Four roles — Platform Admin, School Admin, Teacher and Student — determine what each user can see and do. Role checks run on the server for every restricted page, and teachers can only open classes they teach.
CyberLab is currently a prototype. Production authentication, database-level row security, multi-factor authentication and audit logging are planned but not yet in place. We do not hold any third-party security or privacy certifications.
CyberLab teaches defensive cybersecurity. Every lab uses simulated evidence and reserved documentation IP addresses, and no activity ever interacts with real systems.
Students agree to use techniques learned only within authorized CyberLab environments. Attempting to apply them against real systems without permission may be illegal.
School security & privacy
Security education should model security practice. CyberLab is designed with the controls schools expect.