About
Information is the resolution to uncertainty
I'm kie**er. I study Electronics Engineering and minor in Cybersecurity. The lab started because my friends and I wanted a Minecraft server. Then I kept going: Proxmox and VLANs behind a Sophos firewall, an Active Directory lab I attack and defend, a SOC stack I'm still putting together, and now my thesis.
I write things down because I forget them otherwise, and because the mistakes are the useful part. If you build a homelab, study security, share a thesis group with me, or you're looking at me for an internship, this is how I actually work: check before I change something, and say plainly what a test did and did not prove.
My LinkedIn profileTools I use, with their documentation
Things I got wrong along the way
- Comparing who can reach what with Twingate and NetBirdI now describe access as a sentence: who, what, and why. In my setup that default policy is switched off.
- Hosting Minecraft behind CGNAT for five friendsMoving the port only made the log quieter. The whitelist is what actually kept strangers out.
- Reading my Sophos threat-feed snapshot94% is a capacity figure. It says nothing about whether the feeds are fresh or whether they block anything.
- Tracing a DNS failure: why the firewall answered NXDOMAINThe NXDOMAIN came from my own firewall, not from DNS upstream. One threat list was blocking a mirror I needed.
How I label what you read
Some figures here come from my own lab record. Others are examples or simulations I built to explain an idea. I mark the difference where you meet it: recorded for what my inventory shows, and simulated or "illustrative" for sample evidence and example output.