<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SecOps Machines</title>
    <link>https://secopsmachines.com/</link>
    <description>Essays on running security operations as an engineering and reliability discipline: measuring and eliminating toil, designing sustainable on-call rotas, keeping runbooks correct as systems change, capacity planning for an operations function, and applying error budgets, blameless review and load shedding to security work.</description>
    <language>en</language>
    <atom:link href="https://secopsmachines.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>What Security Can Borrow From Reliability Practice</title>
      <link>https://secopsmachines.com/what-security-can-borrow-from-reliability-practice/</link>
      <guid isPermaLink="true">https://secopsmachines.com/what-security-can-borrow-from-reliability-practice/</guid>
      <pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate>
      <category>Reliability</category>
      <description>Error budgets, blameless review and load shedding transfer into security operations, but only if you are precise about which quantity is being budgeted and which one is not yours to control.</description>
    </item>
    <item>
      <title>Keeping a Runbook True</title>
      <link>https://secopsmachines.com/keeping-a-runbook-true/</link>
      <guid isPermaLink="true">https://secopsmachines.com/keeping-a-runbook-true/</guid>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      <category>Runbooks</category>
      <description>A runbook is a copy of knowledge about a system that changes without telling you. Decay is structural rather than cultural, and the only reliable detector is execution.</description>
    </item>
    <item>
      <title>The Rota Is a Design Artefact</title>
      <link>https://secopsmachines.com/the-rota-is-a-design-artefact/</link>
      <guid isPermaLink="true">https://secopsmachines.com/the-rota-is-a-design-artefact/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <category>On-call</category>
      <description>Most on-call schedules are the output of a spreadsheet and a headcount, not a design. Writing down what the rota has to achieve — before drawing it — changes the shape of the answer and the size of the team.</description>
    </item>
    <item>
      <title>Measure the Toil Before You Automate It</title>
      <link>https://secopsmachines.com/measure-the-toil-before-you-automate-it/</link>
      <guid isPermaLink="true">https://secopsmachines.com/measure-the-toil-before-you-automate-it/</guid>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <category>Toil</category>
      <description>Ask an operations team what to automate and they name the task that annoys them most, which is almost never the task that costs them most. The gap between those two answers is the whole of the problem.</description>
    </item>
  </channel>
</rss>
