Blog
Notes on building secure systems.
Field notes on threat modeling, application security, the software supply chain and regulation — written for the engineers who have to make it work.
- Your dependencies are part of your architectureMost of the code you ship, you did not write. Treating dependencies and the build pipeline as architecture, not housekeeping, changes what you can defend.2 min read
- Paved roads beat policiesA policy tells engineers what not to do. A paved road makes the right thing the fastest thing. Only one of them scales.1 min read
- Reading the Cyber Resilience Act as an engineerThe CRA's reporting obligations now apply. Read through an engineering lens, most of the regulation describes practices good product teams should want anyway.2 min read
- Threat models that survive contact with engineeringMost threat models die the week after the workshop. The ones that last are small, versioned with the code, and owned by the team that ships it.2 min read
Contact
Start with a conversation about your architecture.
Tell us what you are building and where it feels uncertain. You will hear back from a practitioner within one working day — not a sales team.