<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CISO on Cliff Hults</title><link>https://www.haguest.com/tags/ciso/</link><description>Recent content in CISO on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Fri, 06 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/ciso/index.xml" rel="self" type="application/rss+xml"/><item><title>Giving the Backlog Teeth: What Enforcing Remediation SLOs Actually Requires</title><link>https://www.haguest.com/posts/2026-02-06-give-the-backlog-teeth/</link><pubDate>Fri, 06 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-02-06-give-the-backlog-teeth/</guid><description>&lt;p>Every security leader has stared down a backlog of ignored vulnerabilities. You know the shape of it: thousands of open findings, tracked diligently, remediated rarely. The problem wasn&amp;rsquo;t that people didn&amp;rsquo;t care; it was that nothing was &lt;em>at stake&lt;/em> for not fixing them.&lt;/p>
&lt;p>I led a vulnerability-management program across a large engineering organization of thousands of developers and repositories. Early on I learned that you can&amp;rsquo;t improve what you don&amp;rsquo;t enforce. Here&amp;rsquo;s what actually happens when you give the backlog teeth, and the uncomfortable truth about what enforcing it really takes.&lt;/p></description></item></channel></rss>