For Hiring Managers / Triage Teams

This corner of Ownchain is for people who care about how systems are built, monitored, and defended in practice.

I’m aiming at Security Operations (SOC), Junior Cyber Analysis, and Cloud Infrastructure roles where I can work with real logs, active incident response, and hardened infrastructure. Everything documented here is backed by my own Alpine-based Linux lab, live containerized services, and structured operational drills. Nothing is theoretical—if it’s listed, I’ve broken it, analyzed it, and fixed it.

Certifications & Technical Foundation

CompTIA Security+ (SY0-701)
CompTIA Secure Infrastructure Specialist (CSIS)
CompTIA IT Operations Specialist (CIOS)
CompTIA Network+
CompTIA A+
U.S. Navy Advanced CASS School

Everything listed here represents real hands-on operations or verified lab work that I can explain, defend, and reproduce down to the packet and log line. No inflated titles, no borrowed war stories.

Bastion Codex & Incident Reports

CODEX-001: Decommissioning Socket-Mounted Web UIs
- Focus: Eliminating attack surface by revoking /var/run/docker.sock container mounts, tearing down Portainer, and migrating container ops strictly to terminal-native TUIs over encrypted SSH.
CODEX-002: Hardening the Domain Mail Perimeter (SPF, DKIM, DMARC)
- Focus: Troubleshooting transactional dropouts, aligning multi-service envelope senders, and enforcing hard DMARC quarantine policies with automated telemetry monitoring.
CODEX-003: Container Lifecycle, Layer Drift & Database Migrations
- Focus: Managing automated Laravel schema migrations, resolving parallel layer pull race conditions, and executing zero-downtime stack updates.
CODEX-004: Validated Backups & Disaster Recovery Drills
- Focus: Client-side encrypted offsite pipelines and the operational rule of only trusting a backup once a cold restore actually boots.
CODEX-005: Sandboxing vs. Storage Vaults: Flatpak, AppImage, and Native Packaging
- Focus: Diagnosing container sandbox permission boundaries, FUSE execution limits on encrypted storage vaults, and evaluating native runtime integration.
CODEX-006: Hybrid GPU Provider Synchronization & GUI Kernel Recovery
- Focus: Troubleshooting xrandr display provider synchronization failures on hybrid discrete paths, driver stack rebuilds, and recovering from session manager collapses.
CODEX-007: Digital Identity Excision & Data Broker Surface Reduction
- Focus: Executing systematic Right-to-be-Forgotten account excisions and deploying continuous data broker countermeasures to reduce external threat surface.

How I Learn & Defend 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.

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.