I’ve spent years talking to security leaders and practitioners about how people learn cybersecurity well enough to be good at it, and one pattern keeps coming up. The people who can think on their feet during an incident, who can troubleshoot a tool they’ve never touched before, who can explain their reasoning to a non-technical stakeholder, almost never built that skill from a slide deck.
It came from breaking something. Then fixing it. Then breaking it again in a slightly different way until they understood why it broke in the first place.
Courses and certifications still earn their place here. You need a foundation to build on, and that’s a fair starting point. But if your team’s cybersecurity practical training stops at watching a video and reading a study guide, you end up with people who can pass a test and not much else.
What video and text teach
Video and text are good for transferring information, but they don’t build judgment on their own.
I’ve heard this from learning and development leaders directly: when a vendor walks a group of analysts through a tool by having them copy and paste commands, the session looks productive. People follow along, the screen matches the instructor’s screen, everyone nods. But there’s no real understanding happening. Ask that same group to troubleshoot the tool a week later without the script in front of them, and most of them are stuck.
You can usually tell within the first week. The interface looks a little different than what was recorded, the error message doesn’t match anything the instructor covered, or the configuration is slightly off from the example. Passive training doesn’t account for the moments when reality doesn’t match the script, and most of the job happens in exactly those moments.
What a lab environment builds
A good lab skips the step-by-step instructions. You get a goal and a system, and the path is yours to figure out.
One red team lead told me this is the core skill cybersecurity rewards above any other: comfort with not knowing, paired with the ability to research, test, and adjust until you do know. It’s a skill built through repetition under low stakes, not through reading about it.
Working in a virtual cybersecurity training environment forces a few specific habits that passive learning can’t replicate:
- Reading error messages instead of skipping past them, because there’s no instructor to ask
- Forming a hypothesis about what’s wrong before testing it, instead of guessing randomly
- Recognising when a tool is behaving differently than documented, and adapting instead of stalling
- Connecting what’s happening at the command line to what’s happening on the network or system underneath it
A quiz won’t test for any of this, but a real job will, usually in the first week.
Why this builds instincts a course can’t
Here’s the part that’s harder to put a number on: instinct. The ability to look at something and sense that it’s off before you can fully articulate why.
That instinct comes from repeated exposure, specifically the kind with small consequences attached, even simulated ones. One security engineer put it well in a conversation I had recently: when you’re evaluating a candidate or a new hire, the technical checklist counts for far less than whether they can explain how they got somewhere and what they tried first. That kind of explanation only comes from people who’ve done the work themselves, because you can’t narrate a process you’ve never been through.
Why gamified formats work
Gamified cybersecurity training environments, including capture-the-flag style formats, are built for exactly this kind of repetition. A few reasons the format works:
- You get a scenario, not a script, so there’s no fallback to copy-paste
- A scoreboard creates urgency that a self-paced module can’t match
- Open-ended challenges force research instead of recall
- The loop you go through (form a theory, test it, see what breaks, adjust) is the same loop real incidents demand
Why it beats video-and-documentation training
Hands-on formats tend to outpace vendor training that’s mostly video and slides, and the comparison is a useful test for any cyber defense training program your team is evaluating. Teams with built-in hands-on labs for a tool tend to ramp up faster and retain more than teams working through text and documentation alone. The payoff isn’t small. It separates someone who can use a tool under pressure from someone who can only describe what the tool is supposed to do.
A practical starting point
A few starting points that don’t require much infrastructure:
- Replace one passive training module with a lab-based equivalent on the same topic, and compare how people perform a week later
- Run a low-stakes, scenario-based challenge for a tool your team already owns, instead of relying solely on vendor-provided video training
- Ask new hires to walk you through their reasoning on a past project or lab, including the dead ends
None of this needs a big budget, just a willingness to treat “hands-on” as the default for skill-building rather than the occasional add-on after the real training is done.
If you want a head start, a browser-based lab environment is one of the simplest ways to practice without setup or local installs, which makes it easier to build this kind of repetition into a regular routine rather than a once-a-quarter event.
Roman Bohuk is the Co-founder and CEO of SkillBit, a cybersecurity skill development platform for enterprise security teams. Learn more at skillbit.com or contact the team to discuss how SkillBit can support your team.