<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Positioning on Trust Anchor</title><link>https://trustanchor.pro/tags/positioning/</link><description>Recent content in Positioning on Trust Anchor</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 George Vaculik</copyright><lastBuildDate>Tue, 26 May 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://trustanchor.pro/tags/positioning/index.xml" rel="self" type="application/rss+xml"/><item><title>Two perimeters, one trust anchor</title><link>https://trustanchor.pro/posts/trust-anchor-thesis/</link><pubDate>Tue, 26 May 2026 10:00:00 +0200</pubDate><guid>https://trustanchor.pro/posts/trust-anchor-thesis/</guid><description>The problem that started this blog: a Microsoft cloud tenant that grew faster than any person could track. The solution: everything-as-code — CA, PIM, Defender, Sentinel, M365 settings, Azure infrastructure all declared in version-controlled repos and delivered by pipeline. And the two-perimeter identity architecture that makes it trustworthy.</description></item></channel></rss>