Input handling & injection
How unsafe handling of user input leads to injection, and how encoding and parameterisation prevent it.
Security lab
A controlled place to show cause and effect.
The lab is where we demonstrate how vulnerabilities arise and how defences change the outcome — in a safe, isolated environment. It is a teaching and research space, not a target range on the public internet.
We build intentionally vulnerable scenarios and their hardened counterparts side by side, so the difference between a broken and a corrected implementation is visible rather than theoretical.
Content
Scenario categories
The public site describes the structure of the lab. Vulnerable applications are not deployed on public production infrastructure.
Broken access control
Missing or object-level authorisation, and what correct enforcement looks like.
Security misconfiguration
Insecure defaults, exposed metadata and permissive headers, with a hardened baseline.
Dependency & supply chain
How vulnerable or abandoned dependencies create risk, and how to reduce it.
Operations
How the lab is run
Isolation is the rule. Nothing in the lab is reachable from the public internet.
- 01
Isolated
Scenarios run on private, disposable infrastructure, never on production hosts.
- 02
Authorised only
Offensive behaviour is demonstrated only against our own controlled targets.
- 03
Documented
Each scenario explains the root cause, the exploit path and the defence.
- 04
Contained
No traffic leaves the lab environment; no external systems are touched.
Responsible by design
We never deploy intentionally vulnerable applications on public production infrastructure, and we never demonstrate attacks against third-party systems.
Training
Want hands-on material for your team?
We can adapt lab scenarios and content structure to your context.