How networks really work
Addressing, routing, DNS, and the traffic you can see when you look. Everything after this depends on understanding what normal looks like.

A defensive-first introduction to security: how networks behave, how they are attacked, how attacks are detected, and how an incident is documented and reported under pressure.
14 weeks
6 classroom hours + 6 court hours weekly
In person at the ACT learning lab, with a live practice network
Student-athletes from 15 upward; curiosity about systems matters more than experience
Nothing here is a video library. Every module ends with something you built, ran, or defended in front of a person who does this for a living.
Addressing, routing, DNS, and the traffic you can see when you look. Everything after this depends on understanding what normal looks like.
Operating systems, permissions, patching, and building a baseline that survives contact with real users.
Phishing, credential abuse, misconfiguration, and supply-chain exposure. You run the attacks in a sandboxed lab so the defence makes sense.
Logging, alert triage, and reading a queue without panicking. Most of the job is deciding which of sixty alerts actually matters.
Containment, escalation, evidence handling, and the written report. A clear paragraph at 2am is a skill, and we practise it.
A team defends a live network across a simulated week of pressure, then walks the panel through what they saw and what they changed.
Every outcome below is a thing you can point at, not a feeling about the course.
Hands-on time in a real practice network
A written incident report reviewed by a practitioner
Preparation for a first certification attempt
A clear picture of which security role actually suits you
Build the product end to end. 16 weeks, same weekly rhythm, taught by the same classroom team.
Compare the tracksEvery cohort is capped so each athlete gets real review. Tell us where you are starting from and we will place you honestly.
Talk to admissions