Back in February, in my deep dive comparing SAST with Claude Code Security, I described something in theoretical terms: a metabase of versioned, validated facts about an organisation’s source code, built so that cross-repository taint analysis becomes possible. Sources in one repo, sinks in another, internal libraries acting as transparent…
The Blast Radius runs on one conviction: prefer...
From Principle to Practice: Privacy in the Real...
Untangling the Confusion People often confuse these two...
The Plan, the Order, and the Bill In...
Quantum, AI, and the Window That’s Already Closing...
Last week, Anthropic announced Claude Mythos Preview and...
Bear with me on this train of thought....
Cutting the Dead Wood from Your Dependency Graph...
Mitigating Third-Party Component Risk: Swapping the Cancer for...
How One Bad Library Can Poison Your Entire...
I’ve been talking about graphs for dependency analysis...
SAST vs Claude Code Security: A Deep Dive...
Why SAST is broken, and how it could...
Cursor as your Secure Dev Team What I...
Building an AppSec Program: A Collaborative Approach Are...
AI-Generated Code: Productivity Gains, Security Pains, and the...
