The Dispatch

Once a month.
Written by the person who signs it.

A short operator’s note on what actually moved in security this month, and what it means if you are the one accountable for it. No news roundup, no vendor press releases dressed as analysis, and nothing generated while I was asleep.

What is in it

  • One thing that changed, and what it costs you. A regulation, a deadline, a breach pattern worth learning from. Written for the person who has to decide something, not the person who has to patch something.
  • One thing everybody is wrong about. Usually something a vendor category has convinced the market is true. This is the section that will occasionally annoy people.
  • One thing I got wrong. Mine, recent, and specific. Thirty-eight years of this is thirty-eight years of being corrected by production.
  • What I would do about it. Concrete, and free. If the answer is “nothing, ignore this one”, that is what it will say.

What it is not

Not a newsletter about my services. Not a weekly. Not a feed of headlines you already saw. And not a drip campaign wearing a newsletter’s clothes — subscribing gets you the Dispatch and nothing else. If you want to buy something you will have to book a call like everyone else.

Archive

The Dispatch itself has not shipped issue 01, so there is no back catalogue of it yet and I am not going to relabel old posts to pretend otherwise. What is below is the rest of the writing — published, searchable, and a fair sample of whether you want a monthly note from me at all. It is a looser voice than the Dispatch will be, and some of it is not about security. Read a couple and decide.

23 posts, oldest 2025.

Book the 30-minute diagnostic Read the case files → The Dispatch is free. So is the first conversation.