Every target in the lab exists to be compromised. Nothing you touch here belongs to anyone else — that is the entire point.
What it is
A range you are allowed to break
The hardest part of learning offensive security legally is finding somewhere to
practise. The Cyber Lab is that somewhere: isolated networks, deliberately vulnerable
applications and scripted incidents, running on infrastructure built for the purpose.
Segmented from the public internet and from other students
Reset to a clean state whenever you want to start over
Scope is written into every exercise brief
Graded on your remediation write-up, not just the flag
ck-lab@range-03 — scope: 10.20.0.0/24
Environments
What you can work on
Easy
Broken Access Control Range
Web application
A reporting application where the session logic trusts a value it should not. Reach another tenant's data without valid credentials, then ship the fix.
Identify the flawed authorisation check
Access a second tenant's records
Write the remediation as a code change
2–3 hours
Easy
Injection Playground
Web application
Six endpoints, six injection contexts — SQL, NoSQL, command, LDAP, template and header. Each one wants a different technique and a different fix.
Identify the injection context in each endpoint
Extract the flag from each
Write parameterised fixes for all six
3–4 hours
Medium
Compromised Host Triage
Incident response
A Linux host that has been compromised. Work out how they got in, what they did, what persists, and what you would tell the client.
Establish the initial access vector from logs
Identify every persistence mechanism
Build a defensible timeline
4–6 hours
Medium
Segmented Network Range
Network
Six hosts across three segments. Start with a foothold on the DMZ and reach the internal database — documenting every hop.
Enumerate each segment from your current position
Identify the pivot paths available
Reach the internal database host
5–8 hours
Hard
Domain Escalation Lab
Active Directory
A small Windows domain with a realistic set of misconfigurations. Go from a low-privileged user to Domain Admin, then write the hardening plan.
Map the domain attack paths
Escalate to Domain Admin
Identify the detection signature of each step
8–12 hours
Hard
Capture the Flag: Chained
Mixed
Nothing here is critical on its own. Three low-severity issues chain into full compromise — the exercise is seeing the chain.
Find all three individual issues
Work out how they combine
Achieve full compromise via the chain
6–10 hours
The rule that matters
Lab scope is not a suggestion
Every exercise brief states exactly which hosts are in scope. Testing anything
outside that range — including other students' instances — ends lab access. This isn't
bureaucracy; scope discipline is the skill that separates a professional tester from a
liability, and it's assessed like everything else.
Written scope in every brief, before any tooling is mentioned
Techniques taught with their legal context attached
Responsible disclosure practised as part of the exercise
No lab content is transferable to systems you don't own