Why this portfolio exists
AI Security Engineer postings ask for two skill stacks that almost never live in the same person: detection-engineering muscle from a mature SOC, and current LLM/agent security knowledge. I have the first from nine years of building Splunk-based SIEMs at federal agencies (IRS, federal health, federal oversight) and Fortune-500 banks. This portfolio is me showing the second.
Detection engineering, not demos
Each project has inputs, a detector or guardrail, and a measurable output — precision/recall/F1 on a held-out set, or a clear pass/fail signal. Project 1 ships F1 = 1.000 on the included eval set with CI enforcing an 0.85 regression floor.
Splunk + AI, deliberately
Verdicts are CIM-aligned JSON events ready for Splunk HEC. Project 4 generates ATLAS-mapped Splunk ES correlation searches end-to-end. The portfolio reads as content for a SOC team that has just been handed AI workloads.
Federal-fluent
Built by someone who already does ATO evidence packages on Splunk via Qmulos. NIST 800-53 control IDs, FedRAMP awareness, and a NIST AI RMF gap analyzer (Project 8) that consumes the other seven projects as evidence sources.
Reproducible, offline by default
Every project's heuristic / deterministic path runs without an API key. Reviewers can clone, pytest -q, and read JSON output in under five minutes. The Anthropic SDK path is opt-in.