<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-03-31T21:29:00+00:00</dc:date>

	
	<item>
		<title> Alternative Insights on Article 28 of the NIS2 Directive (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20240612-alternative-insights-on-article-28-of-the-nis2-directive</guid>
		<link>https://circleid.com/posts20240612-alternative-insights-on-article-28-of-the-nis2-directive</link>
		<description><![CDATA[On June 9 CircleID published an insightful article by Thomas Rickert entitled "Demystifying Art 28 NIS2." In that piece Thomas set forth two alternative interpretations of Article 28(6) of NIS2, and argued that TLD registries should not be required to maintain a separate database of the registrant data under NIS2. In my view, Thomas' approach is inconsistent with the remainder of Article 28, and would not achieve the goals of NIS2 to improve cybersecurity across the EU member states. <a href="https://circleid.com/posts20240612-alternative-insights-on-article-28-of-the-nis2-directive">More...</a>]]></description>
		<dc:date>2026-03-31T14:29:00-07:00</dc:date>
	</item>
	
	<item>
		<title> NIS2, ICANN and "Thick" WHOIS: A Mandate to Move Forward (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20230111-nis2-icann-and-thick-whois-a-mandate-to-move-forward</guid>
		<link>https://circleid.com/posts20230111-nis2-icann-and-thick-whois-a-mandate-to-move-forward</link>
		<description><![CDATA[The recent adoption at the end of December of the new EU Directive for a high level of cybersecurity across the Union -- commonly referred to as "NIS2" - paved the way for important updates to the domain name system (DNS). Most significantly, Article 28 of NIS2 and its related recitals resolved any ambiguities about the public interest served by a robust and objectively accurate WHOIS system that permits legitimate access by third parties to data... <a href="https://circleid.com/posts20230111-nis2-icann-and-thick-whois-a-mandate-to-move-forward">More...</a>]]></description>
		<dc:date>2026-03-31T14:29:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>