<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Zero Day Playbook</title><link>https://zerodayplaybook.com/</link><description>Runbooks for the first 72 hours after a critical disclosure, by role and asset type, plus the Disclosure Clock of 37 headline bugs from 2026.</description><lastBuildDate>Thu, 19 Nov 2026 00:00:00 GMT</lastBuildDate>
<item><title>Zero day response plan: the complete template with owners, triggers and a drill</title><link>https://zerodayplaybook.com/guides/zero-day-response-plan/</link><guid>https://zerodayplaybook.com/guides/zero-day-response-plan/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>A zero day response plan has 10 clauses: scope, triggers, roles, standing approvals, inputs, deadlines, communications, exceptions, records and a drill.</description></item>
<item><title>What to do when a zero day is disclosed: the first four hours, worked on PHP2Shell</title><link>https://zerodayplaybook.com/guides/what-to-do-when-a-zero-day-is-disclosed/</link><guid>https://zerodayplaybook.com/guides/what-to-do-when-a-zero-day-is-disclosed/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>In the first four hours after a zero day disclosure, extract seven facts from the advisory, check exploitation signals beyond the CISA catalog.</description></item>
<item><title>Out-of-band patch: how to run one without breaking production</title><link>https://zerodayplaybook.com/guides/out-of-band-patch/</link><guid>https://zerodayplaybook.com/guides/out-of-band-patch/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>An out-of-band patch is a fix applied outside the maintenance calendar because exploitation will not wait. Steps, owners, records and sources, read 19 Nov 2026.</description></item>
<item><title>The board brief by noon: template, interim note and a filled brief for Cisco ISE</title><link>https://zerodayplaybook.com/guides/board-brief-by-noon/</link><guid>https://zerodayplaybook.com/guides/board-brief-by-noon/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>Five lines fill the board brief: what is affected, whether exploitation is confirmed, what is done, what is open, and when the next update comes.</description></item>
<item><title>Zero day vulnerability defined: the sources, the tests and six 2026 cases</title><link>https://zerodayplaybook.com/guides/zero-day-vulnerability-defined/</link><guid>https://zerodayplaybook.com/guides/zero-day-vulnerability-defined/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>Google's threat intelligence group defines a zero-day as a vulnerability &quot;maliciously exploited in the wild before a patch was made publicly available.&quot;</description></item>
<item><title>Mitigations that buy time before the patch</title><link>https://zerodayplaybook.com/guides/mitigations-that-buy-time/</link><guid>https://zerodayplaybook.com/guides/mitigations-that-buy-time/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>Mitigations that buy time fall into a few types: restrict the interface, disable the feature, filter at a proxy or WAF, take the service off the internet.</description></item>
<item><title>How to tell where a new CVE hits you</title><link>https://zerodayplaybook.com/guides/where-a-new-cve-hits-you/</link><guid>https://zerodayplaybook.com/guides/where-a-new-cve-hits-you/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>To tell where a new CVE hits you, check three things in order: the version of every copy of the product, the configuration the advisory requires.</description></item>
<item><title>The 72-hour post-incident review: template and a worked review of the BeyondTrust zero-day</title><link>https://zerodayplaybook.com/guides/72-hour-post-incident-review/</link><guid>https://zerodayplaybook.com/guides/72-hour-post-incident-review/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>Held on day three or four, the review takes 90 minutes, one facilitator who held no role, and a record of eight timestamps. With sources, read 19 Nov 2026.</description></item>
<item><title>Compromise assessment after patching a critical flaw</title><link>https://zerodayplaybook.com/guides/compromise-assessment-after-patching/</link><guid>https://zerodayplaybook.com/guides/compromise-assessment-after-patching/</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><description>A patch closes the flaw, not what came through it. A worked hunt for JFrog Artifactory CVE-2026-82329: the window, the requests, admin users, plugins and keys.</description></item>
</channel></rss>
