<?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://d13f4a21.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://d13f4a21.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://d13f4a21.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://d13f4a21.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://d13f4a21.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><item><title>Holistic Approach to Conditional Access Exclusions</title><link>https://d13f4a21.blog-6cm.pages.dev/posts/ca-exclusions/</link><pubDate>Tue, 30 Aug 2022 00:00:00 +0000</pubDate><guid>https://d13f4a21.blog-6cm.pages.dev/posts/ca-exclusions/</guid><description>&lt;p&gt;Whoever works with Microsofts cloud offerings and has a role that is somewhat impacted by Security, must have heard of Conditional Access (CA) by now. It is a very essential part of Microsofts Security offering and Zero-Trust-implementation. Rightly, planning, defining, and implementing CA-policies has a lot of coverage on the internet. I&amp;rsquo;ll try to add a little something which might seem dry, but is essential: How to handle exclusions?&lt;/p&gt;
&lt;p&gt;All CA-policies are assigned to groups, users, and machines. With exclusions, CA offers a way to define policies that don&amp;rsquo;t apply to certain subsets of your landscape. In my example, I will create an exclusion process around a policy that blocks access from certain countries.&lt;/p&gt;</description></item><item><title>Zero Trust</title><link>https://d13f4a21.blog-6cm.pages.dev/posts/2020-03-10_zero-trust/</link><pubDate>Tue, 10 Mar 2020 00:00:00 +0000</pubDate><guid>https://d13f4a21.blog-6cm.pages.dev/posts/2020-03-10_zero-trust/</guid><description>&lt;p&gt;Man könnte meinen &amp;ldquo;Zero Trust&amp;rdquo;-Konzepte seien eine top moderne Modeerscheinung. Ohne jetzt die volle Recherche-Power des Internets zu nutzen, kann ich allerdings sagen, dass diese Konzepte schon seit über zehn Jahren propagiert werden. Google war der erste grössere Implementator.&lt;/p&gt;
&lt;p&gt;Auf einen Satz zusammengedampft besteht &amp;ldquo;Zero Trust&amp;rdquo; in der ständigen Authentisierung von Anwendern, Anwendungen und Endgeräten.&lt;/p&gt;
&lt;p&gt;Als Verfechter von benutzbarer Sicherheit sehe ich hier auch den Grund für den jetzigen Erfolg des Konzepts. Heute sind die Lösungen so einfach zu verwenden, dass Anwender akzeptieren sich ständig anmelden zu müssen. Weil Anwender Anmeldungen in den meisten Fällen gar nicht mitkriegen. Sie melden sich via Biometrie an ihrem Endgerät an. Dieses Endgerät ist fix auf sie zugeteilt und deshalb in Systemen als sichere Anmeldung hinterlegt.&lt;/p&gt;</description></item></channel></rss>