Blue Marshal

About

Security engineer, architect and incident responder.

I'm Blue Marshal. My work covers three jobs that usually sit in different teams: building security tooling, designing security architecture, and responding when something goes wrong. A fire marshal does all three. They set the rules, inspect the build, and take charge at the scene. That's the job I try to do, and the name comes from it.

What I write about

  • Local AI and agents for security work, on hardware I own.
  • AI security: maturity, visibility, and the controls that hold up.
  • Detection engineering and threat hunting across more than one platform.
  • Incident response: what worked, what didn't, and what I'd change.

How I write

Ideas and patterns, not client stories. Example companies are fictional, and so is everything about them. Each post links the sources it relies on, and product names belong to their owners. Posts are drafted with help from AI tools and checked against those sources before they go up.

Find me

Email: [email protected]. Found a security problem with this site? The contact details are in security.txt.

Credits

Typefaces

Frameworks and references

Software in the posts

  • llama.cpp, by ggml-org and its contributors.
  • Strata, by Niko1221 (MIT licence).
  • Qwen models, by the Qwen team. Quantized builds by ISTA-DASLab and bartowski.
  • opencode, the open-source coding agent.
  • Intel oneAPI and the SYCL runtime, by Intel.
  • The AI Visibility Map spreadsheets are generated with openpyxl.

How this site is built

Static HTML and CSS from a small Python build. No JavaScript, no cookies, no analytics, and no third-party requests: the fonts are served from this domain.