A cybersecurity blog for real-world notes, lab work, troubleshooting, architecture thoughts, and practical security lessons without the vendor-flavored nonsense.Welcome to justgibbs.com.
I finally decided to build a place for cybersecurity notes, lab work, troubleshooting stories, architecture thoughts, and the occasional rant when something deserves it.
The goal is simple: write about security in a way that is useful to actual humans. Not marketing fluff. Not copy/paste vendor nonsense. Not another recycled “top cybersecurity trends” article written by someone who has never had to troubleshoot a broken VPN, weird DNS issue, or firewall policy at the worst possible time.
What this blog is going to be
This site is going to be part notebook, part lab journal, part field notes, and part “here is what actually happened when I tried this.” Some posts will be technical. Some will be higher level. Some will probably start because something annoyed me enough to write it down.
That is probably where the good stuff lives anyway.
Topics I’ll cover
Expect posts around things like:
- Network security
- Firewalls and secure connectivity
- SASE, ZTNA, VPNs, and remote access
- Home labs and testing
- Logging, visibility, and detection
- Security architecture
- WordPress hardening and self-hosting
- Practical security lessons learned the hard way
Why bother?
Because a lot of cybersecurity content has a problem.
Some of it is too shallow to be useful. Some of it is so buried in acronyms and vendor language that normal people tune out before the second paragraph. And some of it sounds like it was written by someone who has only ever seen a firewall in a PowerPoint deck.
I want this site to sit somewhere in the middle: technically honest, but still readable. Useful without pretending every topic needs to sound like a compliance document.
The approach
If something works, I’ll explain why. If something sucks, I’ll say that too. If I test something in a lab, I’ll try to show the process, not just the clean final answer after all the mistakes were deleted.
The messy middle matters. That is usually where the actual learning happens.
Security is rarely about one magic product. It is usually architecture, visibility, process, defaults, weird edge cases, and whether someone bothered to test the thing before trusting it.
What comes next
I’ll start building out posts around the topics I run into regularly: secure remote access, firewall design, DNS mistakes, home lab projects, WordPress hardening, logging, and practical security architecture.
The site is live. The first post exists. That is good enough to start.
Now the real work begins.