<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vendor Exposure on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/vendor-exposure/</link>
    <description>Recent content in Vendor Exposure on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/vendor-exposure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EU vs US Vendor Exposure: A Scoring Checklist for European Organisations</title>
      <link>https://sovereignshift.eu/blog/eu-us-vendor-exposure-checklist/</link>
      <pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/eu-us-vendor-exposure-checklist/</guid>
      <description>&lt;p&gt;European organisations tend to think about US vendor exposure in binary terms: either you use US cloud providers or you do not. The reality is more layered. Two organisations can both run on Microsoft 365 and have very different levels of exposure, depending on how identity is configured, who holds the encryption keys, where backups sit, and what integrations exist.&lt;/p&gt;&#xA;&lt;p&gt;This post provides a structured checklist for scoring your organisation&amp;rsquo;s actual US vendor exposure. It is not a compliance form. It is a practical tool for understanding where your sovereignty risk concentrates and which areas you can address without a full migration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
