<?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 Andrew Healey</title><link>https://healey.io/tags/incident-response/</link><description>Recent content in Incident-Response on Andrew Healey</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Andrew Healey</copyright><lastBuildDate>Wed, 14 Oct 2026 09:01:46 -0500</lastBuildDate><atom:link href="https://healey.io/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>The SANS ICS Five Critical Controls: incident response, architecture, monitoring, remote access, vulnerability management</title><link>https://healey.io/writing/the-sans-ics-five-critical-controls-incident-response-architecture-mon/</link><pubDate>Wed, 14 Oct 2026 09:01:46 -0500</pubDate><guid>https://healey.io/writing/the-sans-ics-five-critical-controls-incident-response-architecture-mon/</guid><description>&lt;p&gt;The SANS ICS Five Critical Controls: incident response, architecture, monitoring, remote access, vulnerability management. Pretty familiar to technology folks, but much more challenging in live production.&lt;/p&gt;&#10;&lt;p&gt;Isolating the wrong host can stop a line or create a safety problem. Segmentation means a new network that rarely gets a maintenance window or carving it up like swiss cheese for vendor support. Monitoring has to be passive and protocol-aware, because the active scanning we take for granted in IT can knock over a PLC. Secure remote access means tracking down every integrator and OEM who has had a standing VPN for a decade. Vulnerability management means accepting that some assets will never be patched, so you prioritize by what the process can survive.&lt;/p&gt;</description></item><item><title>So good</title><link>https://healey.io/writing/so-good/</link><pubDate>Sat, 03 Oct 2026 13:35:42 -0500</pubDate><guid>https://healey.io/writing/so-good/</guid><description>&lt;p&gt;So good. The lesson isn&amp;rsquo;t really about SonicWall, though many will breeze past and see it just as that. It&amp;rsquo;s easy to blame the brand and feel safe on Cisco or Palo Alto. At this point, I can&amp;rsquo;t name a vendor that hasn&amp;rsquo;t had some embarrassing bug. For this one, it was a hardcoded Erlang cookie and a static AES key. And on top of that, it&amp;rsquo;s just as easy to say &amp;ldquo;we&amp;rsquo;re on Entra&amp;rdquo; or &amp;ldquo;we&amp;rsquo;re on Okta&amp;rdquo; and forget that most still have some hooks back to Active Directory.&lt;/p&gt;</description></item><item><title>The Power of Scripting: Finding Morto.A</title><link>https://healey.io/writing/the-power-of-scripting-finding-morto/</link><pubDate>Tue, 27 Sep 2011 22:58:26 -0500</pubDate><guid>https://healey.io/writing/the-power-of-scripting-finding-morto/</guid><description>&lt;p&gt;Here I go on another vbScript tutorial.  You might ask why I&amp;rsquo;m not doing this in powershell yet and it is simple: I still run into 2003 and XP environments. Oh yeah, and this works. I don&amp;rsquo;t care what scripting language I&amp;rsquo;m writing in if it gets the job done; you shouldn&amp;rsquo;t either. My $0.02. The original zip download is long gone, but every piece of the script is below.&lt;/p&gt;</description></item></channel></rss>