Appearance
Technology Deep Dives
One narrated video for each main technology in the Cyber Range: what it is, why the project needs it, where it sits, how the code sets it up, one real flow from start to finish, the security choices made for it, and its known limits.
About these videos
The facts come from the code on main at ba1e1e5 (2026-10-23, after pull request 316), not from the capstone paper. For the paper itself, see Capstone Paper Chapters. The voice is machine-generated (Microsoft neural voice "Ava").
Lab infrastructure
How three golden images become an isolated, disposable lab for every student: system containers, the two LXD profiles, the pod network and its peering to the monitoring network, the default-reject egress ACL, admission, the two-part build, teardown and the reaper. See also Lab Infrastructure.
The one Always Free Ampere A1 virtual machine that runs the whole range: the instance settings, what ARM64 changes, the golden image builder, the outbound Cloudflare Tunnel, the OCI packet filter fix, zram, the env file and deployment profiles, systemd units, the GitHub release pipeline and the memory budget. See also Deployment.
Browser access
The range was designed around Apache Guacamole, but the deployed system does not run it. This video explains what Guacamole is, why it was planned, and what the code uses instead: an xterm.js terminal in the portal, a WebSocket through nginx to the bridge on the host, and lxc exec into a tmux session. It also covers the leftover Guacamole code that no longer does anything.
Security monitoring
The manager on the monitoring network, the agent baked into the target image, enrollment on TCP 1514 and 1515, how a lab waits for its agents before going active, the rules behind Scenario 3, how scoring and the SIEM viewer read alerts, the admin health check, and the API hardening and certificates. See also Scenario 3.
App stack
The one web app every student, instructor and admin uses: the App Router, middleware route guards, the server-side proxy to the lab API, sign-in sessions, polling a lab while it starts, the Next.js 15 security headers, tests and how it is built and run. See also Frontend.
The Python service that owns every lab, score and record: its module layout, the 48 routes by group, role checks, the SQLite database and its migrations, starting a lab, scoring a task, background jobs, the terminal bridge, and the test suite. See also Backend and Database.
The single front door for the portal, Keycloak and the web terminal: where nginx runs, its routes, WebSocket proxying, body and buffer limits, and why HTTPS ends at Cloudflare instead of in nginx. See also Deployment and Security.
How people sign in, get a role, and are asked for a 6-digit code. Eight scenes cover the two-factor setup step by step: the OTP policy, the required action, the change to the login flow, how the scripts prove MFA is on, the first-login QR enrolment, and the code prompt on later sign-ins. Also covers the realm and clients, role mapping, the portal and backend token checks, and the Admin "Reset MFA" action. See also Authentication.