This is me — not in a suit, not posing for the 9 to 5. Just me, living cybersecurity.

🚨 New post just dropped: Locked Out of My Own Spine: A Real-Life Incident Response Case Study

Most people don’t think about incident response in their own bodies… until the system breaks. My latest case study isn’t hypothetical — it’s my actual experience being locked out of my own spine due to a Medtronic stimulator failure. And because I breathe cybersecurity, I handled it like a SOC analyst. Root cause analysis, troubleshooting, recovery — applied not to a compromised endpoint, but to myself.

---

More Than Just a Job Title

Here’s the thing recruiters rarely see: I’m not just “Adam, applicant #342.” I’m a spicy little chaos nerd who deep dives for fun, who codes because my brain doesn’t stop thinking in problem trees, and who treats even a broken medical device like an incident ticket.

I don’t do bandages. My brain simply can’t fathom walking away from a problem until it’s actually solved the right way. That’s why I deep dive — peeling back layers, testing, retesting, and documenting until the issue is corrected at the root. Quick patches might stop the bleeding, but they don’t build resilience. And resilience is the only outcome I’ll accept. Which is why I’ll go from 8 AM well into the midnight hours chasing down solutions — whether I’m brainstorming fixes for issues I’ve seen at work, or finding ways to make everyday life a little bit easier in a world full of chaos and deception.

On paper, you’ll find certifications and experience. But here’s what you won’t see on a one-page resume:

• 👨‍👩‍👧‍👦 Family IR on speed dial: I’m the first call when laptops break — not just parents or siblings, but aunts, uncles, cousins, and grandparents. I don’t just fix their systems; I harden them, close open services, and cut down attack surfaces while I’m at it.
• 🛠️ GhostHunter.ps1: My in-progress defensive script for everyday users. Windows ships bloated with services and ports open by default. Most people will never touch them — but attackers will. GhostHunter pares down that noise, giving people fewer doors to guard.
• 🤖 Resume + Cover Letter Automation: Applying shouldn’t feel like a CTF challenge. I wrote my own Tkinter + python-docx automation tool to generate tailored application packets, connection messages, and cold emails — cutting out the repetitive friction of the job hunt.
• 🔍 Relentless vuln management: I scan my own systems, remediate, verify, and re-scan. It’s not for compliance — it’s because I hate leaving loose ends. If there’s a hole, I’m patching it.

---

Why I Write

Obfuscated links, URL shorteners, insecure defaults — organizations normalize practices that make it harder for anyone (even professionals) to tell fake from real. I don’t just gripe about it in DMs; I publish it here on SOCDFIR because cybersecurity is a survival skill, and I live it daily. My blog isn’t clickbait — it’s documentation of my thought process, my experiments, and my failures turned into field manuals.

Cybersecurity isn’t a hat I put on at 9 and take off at 5. It’s the way I live, troubleshoot, and navigate the world. My stimulator case study was proof: if my body can fail, so can systems. If there’s no manual, I’ll build one.

---

If You’re Reading This as a Recruiter

Know this: I’m not just another resume your ATS might mangle. I’m the person who sees chaos as a puzzle, who codes his own tools when the off-the-shelf answer doesn’t exist, and who applies IR methodology whether it’s malware, medical hardware, or misconfigured endpoints.

So, if you’re looking for someone who lives and breathes this work — someone who treats it as survival, not a paycheck — then hi. I’m Adam. Chicago-based, remote-ready, and always open to conversations.

📥 Referrals welcome. 🎯 Cybersecurity analyst | Threat intel | DFIR | Python nerd | Human firewall