Security hiring managers want evidence that a candidate can do the work, and courses and multiple-choice exams rarely show that on their own. Cyber ranges, capture the flag (CTF) competitions, deliberately vulnerable labs and team exercises are how practitioners build and demonstrate hands-on skill without touching systems they have no right to touch. This guide explains what each format trains, which skills and tools to practise, how to stay inside legal and ethical limits, how organisations run team exercises, and how hands-on work fits alongside certifications and career progression. It is written for people entering security, practitioners moving into a new specialism, and team leads who build training programmes.
Key takeaways
- Authorisation is the line that matters. Practising on ranges, CTFs and your own lab is lawful; testing a system you do not own or have written permission to test can be a criminal offence, whatever your intent.
- Different formats build different skills. Jeopardy CTFs train technical depth in one category, attack-defence and range exercises train working under pressure on live systems, and tabletop exercises train decisions and communication.
- Defenders benefit as much as testers. Blue team ranges, forensics challenges and detection labs build SOC, DFIR and detection engineering skills, not only offensive ones.
- Write-ups turn practice into evidence. A short, honest record of how you solved a challenge, published after the event ends and within its rules, is often worth more to an employer than a scoreboard rank.
- Organisations should measure outcomes, not hours. Map exercises to NICE Framework work roles and track detection time, decision quality and remediation, so training spend links to real capability.
What the role does
Hands-on training is not a job title, but it plays a defined role in every security career: it is where knowledge becomes skill and where skill becomes visible. The formats differ in who takes part and what they exercise.
| Format | How it works | Skills it builds | Best for |
|---|---|---|---|
| Jeopardy CTF | Tasks grouped into categories such as web, forensics, crypto and binary; points per solved task, harder tasks worth more; highest score at the deadline wins | Depth in one technical area, research, persistence | Individuals and small teams starting out or specialising |
| Attack-defence CTF | Each team runs vulnerable services, patches its own and scores for defending them and for attacking opponents' services | Patching under pressure, monitoring, exploitation, teamwork | Experienced teams, university and club squads |
| Cyber range exercise | A controlled replica network with scripted attacks or live red team activity, often scored on detection and response | SOC triage, incident handling, hardening, OT and cloud scenarios | Defensive teams, graduate schemes, operator training |
| Deliberately vulnerable labs | Applications or machines built to be attacked, run locally or in a hosted lab, such as OWASP Juice Shop | Application security testing, tool fluency | Self-study at any level |
| Tabletop exercise | A facilitated discussion of an unfolding scenario using injects, without touching systems | Decision making, escalation, communication, plan testing | Incident response teams, executives, crisis groups |
| Purple team exercise | Red and blue teams work together, running techniques and tuning detections in real time | Detection engineering, ATT&CK coverage | Mature SOCs |
CTFtime, which tracks CTF events, describes attack-defence as the original CTF format and notes that mixed formats combine elements, such as a wargame with dedicated periods for task-based challenges. See the Tabletop Exercise Guide and the Purple Teaming Guide for running those formats inside an organisation.
Legal and ethical boundaries
Hands-on practice is only safe when the target is yours or you have explicit permission. The law in most countries does not care whether the person meant well.
- United Kingdom: under section 1 of the Computer Misuse Act 1990, a person commits an offence if they cause a computer to perform any function intending to secure access to a program or data, the access is unauthorised, and they know it is unauthorised. On indictment the maximum is two years' imprisonment, a fine or both. Curiosity about a live website is not a defence.
- United States: on 19 May 2022 the Department of Justice announced a charging policy under the Computer Fraud and Abuse Act stating that good-faith security research should not be charged. It defines good-faith research narrowly (access solely to test, investigate or fix a vulnerability, designed to avoid harm, with findings used mainly to improve security) and says that claiming research is not a free pass, for example for extortion. It is prosecutorial policy, not a legal shield, and it does not bind civil claims or state law.
- Event rules: CTFs and ranges publish rules on what is in scope. Typical rules forbid attacking the scoring infrastructure or other players, sharing flags between teams, and publishing solutions before the event closes. Breaking them can mean disqualification and, if you attack out-of-scope systems, legal exposure.
- Bug bounties and disclosure programmes: these give permission only within the published scope and safe harbour terms. Read them in full before testing and stop at the boundary.
- Home labs: keep vulnerable machines on an isolated network segment or host-only virtual network, never expose them to the internet, and do not run malware samples on a machine that holds personal or work data.
- Workplace practice: testing your employer's systems needs written authorisation from someone who owns the risk, a defined scope and a stop condition, as for any penetration test. See the Penetration Test Scoping Checklist.
Core skills and tools
Ranges and CTFs reward a broad base. The table maps common challenge categories to the skills they build and the free tools practitioners typically learn along the way.
| Category | Skills practised | Typical tools | Career relevance |
|---|---|---|---|
| Web exploitation | HTTP, sessions, injection, access control flaws, API testing | Browser developer tools, an intercepting proxy, curl | Penetration testing, application security |
| Forensics | File formats, memory and disk analysis, packet captures, timelines | Wireshark, Volatility, Autopsy, strings and hex editors | DFIR, SOC |
| Cryptography | Encoding versus encryption, weak keys, misuse of modes, hashing | Python, CyberChef, OpenSSL | Application security, architecture |
| Reverse engineering and binary | Assembly, debuggers, memory corruption concepts | Ghidra, a debugger such as GDB | Malware analysis, vulnerability research |
| Log analysis and detection | Querying logs, building detections, triage | A SIEM or log stack, Sigma rules, Sysmon | SOC, detection engineering |
| Identity and cloud | Directory attacks, token misuse, cloud misconfiguration and over-privileged roles | Cloud provider CLIs, directory analysis tools in lab tenants | Cloud security, IAM, red teaming |
| OSINT | Public source research, metadata, attribution discipline | Search operators, image metadata tools | Threat intelligence |
Underneath the categories sit the habits that employers notice: comfortable use of the Linux command line, enough Python or another scripting language to automate a repetitive step, networking fundamentals (TCP/IP, DNS, common ports), and the discipline to take notes as you work. Identity skills are increasingly valuable, because many real intrusions turn on stolen credentials, tokens and over-privileged service accounts rather than exploits. See the Red Teaming AI Agents for Identity Abuse guide for one emerging area.
Routes into the role
Hands-on platforms suit every entry route, from school to career change. Starting points that are free or low cost include:
- picoCTF: run by Carnegie Mellon University, free, and described on its site as the largest high school hacking competition, with challenge sets across domains including general skills, cryptography, web exploitation and forensics. It has joined CyLab Security Academy, the university's free cyber security learning platform.
- OWASP Juice Shop: an MIT-licensed, intentionally insecure web application covering the OWASP Top Ten and other flaws, with a score board, guided tutorials and a CTF extension. It runs locally with Node.js, Docker or Vagrant.
- School and university schemes: in the UK, the NCSC's CyberFirst programme has supported young people since 2016, and the NCSC now leads the Cyber Pathway of the larger TechFirst programme. University CTF clubs and national competitions offer team experience.
- Organisational exercises: the NCSC's Exercise in a Box is free and offers micro exercises and tabletop exercises across topics including ransomware, phishing and supply chain. CISA Tabletop Exercise Packages provide more than 100 scenario packages with templates for objectives, facilitator roles and an after action report.
- Commercial ranges and labs: hosted platforms with guided paths and certification-aligned labs suit structured study. Compare them on content currency, defensive as well as offensive scenarios, and whether progress can be exported as evidence.
A practical sequence is to learn fundamentals, solve beginner jeopardy challenges in two or three categories, pick one specialism and go deeper, then join a team event and write up what you learned. See the Cybersecurity Careers Guide for the wider choice of roles and entry routes.
Team exercises in organisations
For employers, ranges and exercises test people, plans and tools together. NIST SP 800-84 covers designing, developing, conducting and evaluating test, training and exercise events for IT plans and capabilities, and remains the reference for single-organisation programmes.
- Set objectives first: choose the capability to test (detecting credential misuse, isolating a host, communicating with the board) and the NICE Framework work roles involved.
- Pick the format: tabletop for decisions and plans, range for technical response, purple team for detection coverage.
- Build safe scenarios: run technical exercises on an isolated range or lab tenant, never on production identity systems, and use synthetic accounts and data.
- Run and observe: assign facilitators and evaluators, log timings and decisions, and keep a white cell to adjust injects.
- Debrief and fix: hold a hot debrief the same day, write an after action report and track remediation actions to closure.
- Repeat and raise difficulty: rerun scenarios after fixes to confirm improvement, then add new techniques.
Measure the programme with a few metrics: time to detect and contain injected activity, share of exercise findings remediated within an agreed period, ATT&CK techniques exercised and detected, participation across shifts and roles, and staff-reported confidence before and after. See the Tabletop Exercise Scenario Pack for ready-made scenarios and the Security Operations Metrics Guide for measurement.
Certifications that help
Many practical certifications are themselves hands-on: candidates complete tasks in a lab rather than answer questions, so range and CTF practice is direct preparation. Rather than restate exam details here, use the dedicated guides, which take facts from the certifying bodies:
- Offensive, lab-based: see the OSCP Certification Guide, the OSEP and OSWE Certification Guide and the Practical Red Team Certifications Guide.
- Defensive: see the Blue Team Certifications Guide.
- Foundation: see the ISC2 Certified in Cybersecurity (CC) Guide for an entry-level credential to pair with lab practice.
- Choosing: see the Cybersecurity Certifications Guide for a role-based comparison.
Certifications show a verified baseline; ranges and write-ups show range and curiosity. Hiring managers usually want both.
Progression
| Stage | Hands-on focus | Evidence to show |
|---|---|---|
| Beginner | Beginner jeopardy challenges, guided labs, Juice Shop | A notes repository and a few write-ups of retired challenges |
| Intermediate | One specialism in depth, team CTFs, defensive range scenarios | Consistent event participation, a home lab, a practical certification |
| Practitioner | Attack-defence events, purple team work at your employer, detection building | Detections or tools you wrote, exercise reports (sanitised) |
| Senior | Designing challenges, running exercises, mentoring | Events you built or ran, talks, published research within disclosure rules |
Designing a good challenge or exercise is a skill in its own right and a strong signal for senior roles: it shows you understand a weakness well enough to build, scope and explain it. See the SOC Analyst Career Guide for a defensive progression path.
Framework mapping
| Framework | Where hands-on training fits |
|---|---|
| NIST CSF 2.0 | PR.AT-01 awareness and training for personnel; PR.AT-02 training for individuals in specialised roles |
| NIST SP 800-53 Rev. 5 | AT-2 literacy training and awareness; AT-3 role-based training; IR-3 incident response testing; CP-4 contingency plan testing; CA-8 penetration testing |
| NICE Framework (Components v1.0.0, March 2024) | 7 work role categories, 52 work roles and 11 competency areas, used to align exercises to roles and tasks |
Common failure patterns
- Testing live systems "for practice": scanning or probing a site without permission, which can be an offence under the Computer Misuse Act or similar laws.
- Collecting ranks, not skills: following walkthroughs flag by flag without understanding the weakness, which shows in interviews.
- Offence only: ignoring forensics, logging and detection challenges, though most entry roles are defensive.
- Publishing too early: releasing write-ups or flags during an event, against its rules.
- Exercises with no follow-through: organisations running ranges or tabletops without an after action report or remediation tracking, so the same gaps reappear.
- Unsafe labs: vulnerable machines exposed to the internet or real credentials used in training tenants.
Practitioner checklist
- Practise only on systems you own, ranges, CTFs and programmes whose written scope covers you.
- Build an isolated home lab with no internet exposure for vulnerable machines.
- Cover at least one defensive category (forensics or log analysis) alongside offensive ones.
- Write up challenges after events close, explaining the weakness and the fix.
- Join a team event each year to practise collaboration under time pressure.
- Pair hands-on evidence with a certification suited to your target role.
- For team leads: map each exercise to NICE work roles and set measurable objectives.
- For team leads: produce an after action report and track every remediation to closure.
Standards and references
- CISA NICCS: NICE Framework
- NIST: SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities
- legislation.gov.uk: Computer Misuse Act 1990, section 1
- US Department of Justice: New policy for charging cases under the Computer Fraud and Abuse Act
- NCSC: Exercise in a Box
- CISA: Tabletop Exercise Packages
- OWASP: Juice Shop
- Carnegie Mellon University: picoCTF
Related NHI Mgmt Group resources: Cybersecurity Careers Guide · Cybersecurity Certifications Guide · Penetration Testing Guide · Red Teaming Guide