Labs

Hands-on IT and cybersecurity labs

Three ways to practise: short guided labs and a hands-on Practice Lab for each career, simulated technical tasks in Job Workstation, and hands-on projects with real tools in your own home lab. This page shows which fit your career.

Lab Library

Labs by career path.

Each lab gives you one focused problem with synthetic logs, configurations or artifacts, step-by-step tasks, hints and instant scoring. Free guided labs are marked Free. Hands-on Practice Labs are included with Pro.

Three ways to practise, and which fit your career

  • Guided labs (this Lab Library): short decision exercises in your browser, about 12–15 minutes each. You match, rank or choose, then see an explanation. They practise judgement, not hands-on tool use.
  • Simulated technical tasks (Job Workstation, in the app): workplace tickets with simulated terminals and consoles, scored on resolution, safe actions, evidence, verification and notes.
  • External hands-on projects (home lab, below): real tools on your own computer or virtual machines.
Practice routes for each of the 8 main careers
CareerGuided labs that fitSimulated tasks in Job WorkstationGap
IT SupportGrant, Reduce or Reject (access decisions, from the IAM Analyst path)Account lockout and shared-mailbox tickets in a simulated directory and mail consoleNo guided lab written for IT Support yet
Network EngineerNone that practise network configuration. Reading Traffic Patterns is a traffic-classification exercise for security monitoring7 network tickets with a simulated device command line and network mapNo hands-on networking lab yet
SysAdminSpot the Weak Configuration (server hardening review)Disk and service-failure tickets with a simulated server terminal and service logsNo hands-on server administration lab yet
SOC AnalystIncident Severity Assessment, Containment Decision Drill, Baseline or Anomaly?, Pipeline Health TriagePhishing and beaconing investigations with simulated SIEM, mail and EDR toolsNone
Cloud SecurityIAM Policy ReviewPublic bucket and leaked-key tickets with simulated cloud consolesNone
Penetration TesterRules of Engagement Check, CVSS in ContextFinding triage and retest ticketsNo live exploitation: all testing is simulated
Digital ForensicsWhich Artifact Answers It?USB and ransomware evidence casesNone
GRC AnalystRate the RiskAccess review and vendor review ticketsNone
IAM Analyst labs
Guided labLevelPlan
IAM Policy ReviewBeginnerPro
Grant, Reduce or RejectBeginnerFree

Shared labs count for every role that uses them. IAM Analyst learners are also recommended related labs from other paths.

Build a home lab for IT and cybersecurity

Updated October 2026 · Beginner to intermediate

A home lab lets you practise with real tools: build and fix a small network, run servers, and generate and investigate security logs. It is also one of the best things to talk about in interviews. You can build a useful lab entirely with free software.

Stay legal and isolated. Only run attack simulations against machines you own, inside an isolated lab network. Never test techniques on systems you do not have explicit permission to use.

What you need

  • A computer with enough memory. 16 GB of RAM is a comfortable minimum for several virtual machines; 32 GB is better.
  • A hypervisor such as VirtualBox, VMware Workstation or Hyper-V.
  • Operating systems: a Windows evaluation image, a Linux server distribution and optionally a Windows Server evaluation for Active Directory.

For IT Support, networking and server practice, a domain controller, a Windows client and a Linux server are enough. For security monitoring, add the pieces below.

A simple security monitoring lab design

  1. Windows endpoint with Sysmon installed for detailed logging.
  2. SIEM server running Wazuh, Elastic or Splunk’s free license to collect logs.
  3. Optional domain controller to practice Active Directory and identity investigations.
  4. Optional network sensor such as Security Onion to capture traffic.
  5. An isolated virtual network connecting the machines, with internet access only when needed.

Lab projects to try

IT and infrastructure projects

1. Run a small Active Directory domain

Build a domain controller and a client, create test users, cause a lockout with wrong passwords, then find it with PowerShell, unlock the account and confirm the sign-in works. Snapshot first so you can reset.

2. Build and troubleshoot a small network

In Cisco Packet Tracer (free with a Cisco Networking Academy account) or GNS3, build two VLANs, a trunk and DHCP. Break one setting on purpose, then use ping, show commands and tracert to find and fix it.

3. Recover a Linux service

On a Linux server VM, run a simple web service, fill a test disk, read the service logs with journalctl, free space safely and confirm the service recovers. Then practise restoring a file from a backup.

Security monitoring projects

4. Detect a brute-force attack

Generate repeated failed logons against a test account, then find the 4625 events in your SIEM and build an alert. Check whether you can spot a successful logon afterward.

5. Trace a suspicious process

Run a harmless PowerShell command with an encoded argument, then use Sysmon event 1 to find the process, its parent and its full command line. Decode it with CyberChef.

6. Analyze your own traffic

Capture traffic with Wireshark while browsing, then identify DNS lookups, TLS handshakes and the hosts contacted.

7. Simulate attacker techniques

Use an open-source adversary emulation library such as Atomic Red Team — only inside your lab — to run individual MITRE ATT&CK techniques and check which ones your logging catches.

8. Write it up

For each project, write a short report: what you set out to do, the evidence, what you changed or detected, and how you checked the result. These write-ups become portfolio pieces for job applications.

No hardware? Use the Lab Library

If you do not have a machine that can run several virtual machines, start with the guided labs above and the simulated tickets in Job Workstation. They teach the reasoning and workflow in your browser, but they are not the same as hands-on time with real tools, so add a home lab when you can. See the career paths for what each role practises.

FAQ

Home lab questions

Do I need a home lab to get an IT or cybersecurity job?

No, but it helps. A lab gives you hands-on experience and concrete projects to discuss. Browser-based practice is a faster way to start if you do not have the hardware, but it does not replace hands-on time with real tools.

Can I build a lab in the cloud instead?

Yes. Cloud providers offer free tiers and credits, but watch costs carefully and shut resources down when you finish.

Is it legal to run attack tools in a home lab?

Running tools against machines you own in an isolated lab is generally fine. Using them against systems you do not own or have permission to test is illegal in most countries.

No lab? No problem

Practice full job tasks in your browser.

Skip the setup. Start free with Module 1 and an introductory Job Workstation ticket in one of eight career paths. The Practice Labs are included with Career Pro (your career) and Premium Lifetime (all careers).

Start free. No experience required.