<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Security on jamesm.blog</title>
    <link>https://jamesm.blog/security/</link>
    <description>Recent content in Security on jamesm.blog</description>
    <image>
      <title>jamesm.blog</title>
      <url>https://jamesm.blog/papermod-cover.png</url>
      <link>https://jamesm.blog/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 20 May 2026 10:30:00 +0100</lastBuildDate>
    <atom:link href="https://jamesm.blog/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Threat Modeling for Engineers: Finding the Flaws Before Attackers Do</title>
      <link>https://jamesm.blog/security/threat-modeling-for-engineers/</link>
      <pubDate>Wed, 20 May 2026 10:30:00 +0100</pubDate>
      <guid>https://jamesm.blog/security/threat-modeling-for-engineers/</guid>
      <description>Most security work is reactive - a scanner flags an issue, someone patches it. Threat modeling is the opposite: a structured way to find design flaws before you write the code. Here is how it works, a worked example, and why it is the one security skill every engineer should have.</description>
    </item>
  </channel>
</rss>
