<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DataProtection on Pfisterer Consulting</title><link>https://pfisterer.xyz/en/tags/dataprotection/</link><description>Recent content in DataProtection on Pfisterer Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 15 Jun 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://pfisterer.xyz/en/tags/dataprotection/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Act Access by Design: The ERP Question Hiding Behind the IoT Label</title><link>https://pfisterer.xyz/en/news/data-act-access-by-design-september-2026-iot-erp/</link><pubDate>Mon, 15 Jun 2026 12:00:00 +0200</pubDate><guid>https://pfisterer.xyz/en/news/data-act-access-by-design-september-2026-iot-erp/</guid><description>&lt;p&gt;A machine builder in the Hunsrück region is three months out from launching a new generation of connected equipment. The production schedule is set, the first units ship in the autumn, and the control-system supplier has already answered the compliance question in one sentence: &amp;ldquo;Access by design? We will do that on the PLC.&amp;rdquo; Everyone in the room nods, because it sounds like a firmware setting and firmware is the supplier&amp;rsquo;s department.&lt;/p&gt;</description></item></channel></rss>