Blog
Write-ups of projects from my work: evidence fetchers, validators, framework mapping, and the tools I build along the way. Client names and system details are left out.
-
Replacing hand-exported scan files with fetchers that pull the report from the SentinelOne, Tenable, and Wiz APIs.
-
My first fetcher in paramify-fetchers, and the question every fetcher has to answer: what does an empty result mean?
-
Scheduled Claude skills that pull bug reports and feature requests out of recorded client calls, and why the first version had too much autonomy.
-
How I scoped a Google Workspace evidence fetcher for FedRAMP 20x by starting from the 23 checks it had to pass.
-
Building about 320 capabilities for a client on Microsoft 365 GCC High, and why the extra records were worth it.
-
A three-tab workbook and a chain of Claude skills that answer the same three questions for every new FedRAMP 20x client.
-
Mapping NIST CSF 2.0, Japan's ISMAP, and FedRAMP's new identifiers onto capabilities that already exist.
-
What I found building intake presets for Fortify, Qualys, Grype, and SentinelOne.
-
Fitting change requests into the Significant Change Notification schema, and building a viewer for Security Decision Records.
-
Building internal tools on the Claude API, and the guardrails I put around them.