<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compliance on Cliff Hults</title><link>https://www.haguest.com/tags/compliance/</link><description>Recent content in Compliance on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Fri, 13 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/compliance/index.xml" rel="self" type="application/rss+xml"/><item><title>The Waiver Trap: When Your Compliance Safety Valve Delays Real Remediation</title><link>https://www.haguest.com/posts/2026-02-13-the-waiver-trap/</link><pubDate>Fri, 13 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-02-13-the-waiver-trap/</guid><description>&lt;p>Enforcement worked. Critical vulnerabilities were suddenly getting fixed on deadlines, and the backlog that had sat ignored for years started to clear. But it worked &lt;em>too well&lt;/em> in one sense: the volume of new work it created across thousands of developers turned enforcement itself into a blocker.&lt;/p>
&lt;p>This is the part of the story almost nobody writes about, because it&amp;rsquo;s the part that looks like a failure. It was the most instructive decision I made.&lt;/p></description></item></channel></rss>