<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Risk Management on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/risk-management/</link>
    <description>Recent content in Risk Management on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/risk-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Build an ICT Third-Party Risk Register for NIS2 Compliance</title>
      <link>https://sovereignshift.eu/blog/nis2-ict-third-party-risk-register/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/nis2-ict-third-party-risk-register/</guid>
      <description>&lt;p&gt;NIS2 (Directive 2022/2555) requires organisations in essential and important sectors to implement cybersecurity risk management measures that specifically address &amp;ldquo;supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers&amp;rdquo; (Article 21(2)(d)).&lt;/p&gt;&#xA;&lt;p&gt;This means you need a documented understanding of your ICT third-party dependencies, the risks they introduce, and the measures you have in place to manage those risks. Most organisations call this an ICT third-party risk register.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
