I help organisations put AI systems into production without inheriting their blast radius — agentic security patterns that hold under an adversary rather than under a policy review.
Twenty years to get here: lead secure-code reviewer, site reliability for the Nintendo Switch eShop at 99.99% sustained availability, and forward-deployed cloud security with global accounts. Today I lead a security practice in Tokyo and deliver in Japanese and English.
I still write the code. BlueSquadron is where the detection and application-security tooling lives, and this site is where the reasoning gets published — including the trade-offs and the places the advice does not apply.
Full history on LinkedIn.
A web application scanner with a plugin architecture, packaged in Kali Linux and BlackArch and carrying 612 stars and 115 forks. Fingerprints servers, frameworks, WAFs and CDNs, then runs the modules a risk level you choose permits. I wrote the code; distribution maintainers chose the reach — still the clearest lesson I have had on the gap between building and being adopted. Python 3.11+, GPL-3.0.
The artefact that made OWASP ASVS practical to actually run, tracking 4.0.2 and rendering coverage as you fill it in. 218 stars, 53 forks, and ten years on it is still the most-used thing I have written — a spreadsheet, which is worth remembering the next time I want to build a platform. MIT.
Incident-response case management for the analysts who work the queue rather than report on it. Multi-tenant, real-time, OCSF-native, with ATT&CK mapping, observables, evidence and notes. One bootstrap.sh reaches a populated UI in sixty seconds, because time-to-first-opinion decides who gets to evaluate a security tool at all. Python 3.12 and React 18, Apache-2.0, alpha.
Real-time security event correlation in a single Rust process. Write Sigma rules, feed it OCSF events, get alerts — no cluster, no JVM, no brokers. Flink’s ideas about event time, keyed state and windows are correct and necessary; the operational weight bundled with them is a separate purchase most teams do not need. Worker layout is derived from the compiled rule set, not configured.
A security-oriented unit and functional testing library for PHP. The argument is about where security assertions live: in the same suite as everything else, running on every commit, rather than in a report that arrives once a quarter. GPL-3.0.
A cloud penetration-testing toolbox, assembled from the checks I kept rewriting by hand on engagements. Published on the theory that anything I have retyped three times belongs in a repo. GPL-3.0.
A survey of the attack surface that arrived with Web 2.0 — client-side trust boundaries, mashups, and the assumption that the browser was a safe place to make a decision. Presented at SAR-SSI, and the start of a career spent in the gap between what a platform makes possible and what it makes safe. That gap has not closed; it has only moved.
How to compose untrusted third-party components on a mobile client without inheriting their privileges: mediate capability at the boundary rather than trust each component to behave. Written years before anyone said agent, and it is the same answer to the same question — which is why I am sceptical when agentic security is described as unprecedented.
Founded and organised the group, from 150 to 600 members across 8 editions as an official AWS speaker. Sessions covered cloud security architecture, identity at scale, and the operational reality of regulated workloads — with a standing preference for talks that named a trade-off over talks that named a product.
