About

Philosophy

Every alert, log line, and control narrative gets the same two questions: is it actionable, and can I prove it.

The short version

I started on a 24/7 watch floor at USAF Ramstein: four years of shift-based network defense for 3,000+ personnel across three Combatant Commands. More than a thousand Tier 1/2 incidents. When a zero-day dropped, my team hardened 241 systems across 11 sites inside 24 hours, and the RMF documentation I wrote held up with zero rework on the follow-up audit.

That last part turned out to be the career. Anyone can close a finding; the work that matters is proving it stays closed. At Lockheed Martin I moved fully into that world as a Senior Information Security Analyst on classified DoD programs. Control assessments, eMASS accreditation packages, POA&M governance, and continuous monitoring, with Python and PowerShell doing the evidence collection most teams still do by hand.

Today I work the newest attack surface there is: red-teaming frontier AI models at Invisible Technologies. Prompt injection, adversarial manipulation, and teaching models to reason correctly about the same NIST and ISO controls I’ve spent years implementing.

The through-line: compliance work built by someone who has actually worked the floor. I know which control failed behind an alert, and what the reporting obligation is. That operational time is why my paperwork survives audits.