<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>web privacy engineer</title><description>Bridging the gap between code and compliance.</description><link>https://www.webprivacyengineer.com/</link><item><title>From Regulation to Pipeline: Auditing Cyber Resilience Act Compliance with cra-audit</title><link>https://www.webprivacyengineer.com/blog/cra-audit/</link><guid isPermaLink="true">https://www.webprivacyengineer.com/blog/cra-audit/</guid><description>The CRA&apos;s vulnerability reporting duties have applied since 11 September 2026. I built cra-audit, an open-source CLI and GitHub Action, to turn the CRA and BSI TR-03183 into checks that run on every commit.</description><pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Applying Law to Code: A Web Developer&apos;s Path into Privacy Engineering</title><link>https://www.webprivacyengineer.com/blog/web-privacy/</link><guid isPermaLink="true">https://www.webprivacyengineer.com/blog/web-privacy/</guid><description>After years building for the web at Sngular and a law degree, I started asking a different question: what does the law actually require from the code we ship? This is where I share what I find.</description><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate></item></channel></rss>