This corner of Ownchain is for people who care about how things are built, not just the words on top.
I’m learning my way into cybersecurity and cloud security by running and hardening my own Alpine-based homelab: containers, backups, monitoring, and services hosted on my own hardware. Nothing here is theoretical; if it’s listed, I’ve broken it and fixed it at least once.
Over time this section will collect short writeups on what I’ve built, how I secured it, and what went wrong along the way – so other curious geeks can learn from both the design and the mistakes.
How I Learn With a Homelab
I learn security and infrastructure by running my own small lab environment on Linux with Container orchestration, but I keep the exact details private on purpose. Anything described here is about principles and lessons, not a blueprint of my current setup.
The lab exists so I can practice real workflows: provisioning services, breaking them, fixing them, testing backups, and watching how things behave under load and failure. I document every meaningful change and incident so I can see patterns over time instead of treating each problem as a one‑off.
Backups and recovery are a first‑class part of this. I keep multiple encrypted copies of important data, including offsite, and I treat a backup as “real” only after I’ve restored from it and verified it works. I assume hardware and disks will eventually fail and design around that.
I also care about “seeing” the system. I started with raw logs and basic checks, then added self‑hosted monitoring on my internal network so I can spot trends and slow failures instead of only reacting when something is obviously broken. The exact tools matter less than the habit of looking regularly and acting early.
Security is a mindset here, not a marketing label. I minimize what’s exposed to the internet, keep personal and experimental things separate, update and decommission services intentionally, and think in terms of reducing attack surface rather than chasing perfect safety. I share concepts and lessons publicly, but I keep sensitive implementation details offline so that learning in public doesn’t turn into publishing a target map.
Certifications
- CompTIA Security+ (SY0-701)
- CompTIA IT Operations Specialist (CIOS)
- U.S. Navy Advanced CASS School
Everything listed here is either work already done or lab work that I can clearly explain and reproduce. No inflated titles, no borrowed war stories, and no pretending lab experiments are production experience.
Current Direction
Right now I’m focused on turning years of operations, support, and documentation work into a junior-friendly security and cloud skill set. That means more Linux, more careful monitoring, better backups and recovery drills, and getting comfortable with the basics of cloud platforms without pretending to be an architect on day one.
I’m deliberately treating this as a long game: build fundamentals first, prove them in small, contained environments, then scale up only when I can explain what I’m doing in plain language to non‑geeks.
What I’m Aiming At Next
Near term, I’m aiming at security operations and cloud‑adjacent roles (SOC, junior security analyst, or cloud support) where I can work with real incidents, logs, and infrastructure while still learning aggressively.
Over the next 6–12 months, my goals are to:
- Tighten my resume around real operations, monitoring, and Linux experience.
- Earn an entry‑level cloud certification and keep building small, well‑documented lab projects.
- Start publishing selected writeups here so there’s a visible trail of what I’ve actually done, not just what I say I can do.