<rss xmlns:webfeeds="http://webfeeds.org/rss/1.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
  <atom:link href="https://nxlog.co/news-and-blog/index.xml" rel="self" type="application/rss+xml" />
  <title>Telemetry auditing</title>
    <link>https://nxlog.co/news-and-blog/tags/telemetry-auditing/</link>
    <description>Recent content in Telemetry auditing on NXLog Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
  <lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate>
  
  <item>
    <title>NIS2, HIPAA, PCI DSS: What compliance means when you can&#39;t upgrade your OS</title>
    <link>https://nxlog.co/news-and-blog/posts/nis2-hipaa-pci-dss-compliance-legacy-os/</link>
    <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
    
    <enclosure url="https://nxlog.co/news-and-blog/images/categories/security.png" type="image/webp" />
    <atom:logo>https://nxlog.co/news-and-blog/images/categories/security.png</atom:logo>
    
    <guid>https://nxlog.co/news-and-blog/posts/nis2-hipaa-pci-dss-compliance-legacy-os/</guid>
    <description>
    
    &lt;img src=&#34;https://nxlog.co/news-and-blog/images/categories/security.png&#34; width=500 /&gt;
    
    Compliance frameworks don’t have a checkbox for &amp;amp;#34;we know it’s a problem, but we can’t afford to fix it right now.&amp;amp;#34; Yet that’s the position thousands of organizations find themselves in — bound by regulation to meet security standards that their operating systems are physically incapable of supporting.
If you run Windows XP, Server 2003, or any other unsupported OS in a regulated environment, the compliance obligation doesn’t go away just because the upgrade path is blocked.
    </description>
    
    <dc:creator><![CDATA[ João Correia ]]></dc:creator>
    
  </item>
   
  </channel>
</rss>
