<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zero Trust on Phillip Büchler</title><link>https://53fd2d4a.blog-6cm.pages.dev/tags/zero-trust/</link><description>Recent content in Zero Trust on Phillip Büchler</description><generator>Hugo</generator><language>en</language><copyright>&amp;copy; 2022 &lt;a href="https://philipbuechler.ch/"&gt;Fime&lt;/a&gt;</copyright><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://53fd2d4a.blog-6cm.pages.dev/tags/zero-trust/index.xml" rel="self" type="application/rss+xml"/><item><title>Who Holds the Keys to Your Patching?</title><link>https://53fd2d4a.blog-6cm.pages.dev/posts/who-holds-the-keys-to-your-patching/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://53fd2d4a.blog-6cm.pages.dev/posts/who-holds-the-keys-to-your-patching/</guid><description>&lt;p&gt;On 21 October, details of two critical PHP flaws leaked to VirusTotal at 02:29 UTC. By 07:34, hosting providers were reporting active exploitation, and PHP released the fix at 13:52, &lt;a href="https://www.recordedfuture.com/blog/php2shell-vulnerability-exploitation"&gt;according to Recorded Future&lt;/a&gt;. Amazon later said the first exploitation attempts &lt;a href="https://www.bleepingcomputer.com/news/security/amazon-says-php2shell-exploitation-began-4-days-before-patches/"&gt;started on 17 October&lt;/a&gt;, four days before any patch existed.&lt;/p&gt;
&lt;p&gt;In &lt;a href="https://53fd2d4a.blog-6cm.pages.dev/posts/patch-less/"&gt;Patch Less&lt;/a&gt; I argued that the long tail of utilities on user devices should be patched automatically, with a third-party tool or Microsoft&amp;rsquo;s own catalogue. Timelines like this one are the reason. But that automation raises a question I keep coming back to: when you hand patching to a third-party tool, whose keys are you handing over?&lt;/p&gt;</description></item></channel></rss>