home / home-lab
Home Lab Documentation
Diagrams and write-ups of the lab architecture (networks, cloud environments, detection stack), plus scenarios I have run and how they were detected and handled.
What is documented
Networks
Segmentation, trust zones, routing and firewall policy, drawn with the data flows marked.
Cloud environments
Accounts, identity and permissions, logging and the guardrails around them.
Detection stack
What is logged, where it is collected, and how alerts are written and tuned.
Scenarios
Exercises run in the lab: what was done, what the detection stack saw, how it was handled and what changed afterwards.
Write-ups
newest firstCloud Identity Range
A disposable cloud identity lab with a code-applied landing-zone baseline and immutable logs, running IAM privilege paths and the detections that catch them.
02 · architecture + scenarioIsolated Research Range
A disposable, default-deny lab for reproducing vulnerabilities safely, with the network instrumented so every run doubles as a detection exercise.
How entries are written
- Every diagram carries a legend: trust zones, data flows and logging points.
- Scenarios are written as objective, setup, what was run, what was detected, how it was handled and what changed.
- Everything is run against systems I own, in an isolated environment, with no real data.
- Published under the sanitization policy: no real addresses or credentials, no working exploit payloads.