<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident Response on Cliff Hults</title><link>https://www.haguest.com/tags/incident-response/</link><description>Recent content in Incident Response on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Sun, 12 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>When Your Security Tool Goes Down: Surviving an SCA Tool Outage</title><link>https://www.haguest.com/posts/2026-04-12-sca-tool-outage/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-04-12-sca-tool-outage/</guid><description>&lt;p>Security tooling exists to protect your organization. But what happens when the security tool itself becomes the outage?&lt;/p>
&lt;p>That&amp;rsquo;s the situation we found ourselves in when an SCA tool experienced a service disruption that lasted approximately five hours. For us, it wasn&amp;rsquo;t a degraded experience; it was a complete development freeze.&lt;/p></description></item></channel></rss>