Helping design and run an OWASP TIET CTF that pulled in 1800+ registrations taught me more about how people actually learn security than any single course did. A slide explaining SQL injection is forgettable. A login form that breaks the moment you type ' OR 1=1 -- is not.

Breakable systems beat abstract explanations

Cybersecurity concepts are inherently adversarial - they only make sense when you're trying to break something. CTF challenges across web exploitation, cryptography, reverse engineering, and forensics force participants to apply a concept immediately, instead of just recognizing its definition on a quiz.

Designing challenges that teach, not just gatekeep

When designing challenges, the temptation is to make them as hard as possible. A better goal is to make the "aha" moment land at the right difficulty for where most participants are. A few things that consistently worked:

What the offline workshop added

Pairing the CTF with an offline cybersecurity workshop for 400+ attendees closed the loop - students who'd hit a wall during the CTF could ask "why didn't this work" in person, and the answer usually mapped straight back to a fundamental (how cookies work, how a web server parses input) rather than an obscure trick.

The best CTF challenges aren't the cleverest ones - they're the ones where solving them teaches you something you'll recognize again in a real system.

If you're trying to get a group of students into security, my honest recommendation is to skip the slide deck and start with something they can break. The curiosity that follows tends to be self-sustaining.