Audit, Patch, SWAT & Security Hygiene

2015 taught me the value of reliability. 2016 taught me the value of precision: the kind you only learn by facing audits, SWAT remediation sprints, patch cycles, and compliance expectations all landing in the same quarter. Internal audits forced a closer look at how we documented changes, tracked patching, validated backups, evidenced monitoring, controlled access. It was uncomfortable and necessary. Audits don't weaken IT, they reveal exactly where it needs to get stronger.

Then came SWAT: coordinated strikes with infrastructure and security to clean stale AD objects, patch unsupported systems, close configuration drift that had been quietly accumulating for months. Intense, exhausting, and the fastest way I know to learn to think in root causes instead of symptoms. I took direct ownership of patch compliance across the Windows estate and learned the hard way that a reboot is never just a reboot — it's a potential outage or a hidden dependency waiting for the wrong moment to surface.

The threat landscape was shifting under all of it. Ransomware was going mainstream, and malware investigation, endpoint remediation, firewall and VPN hygiene became part of the daily rhythm. Security, I understood by year-end, isn't a tool you install. It's a culture, and IT is one of its guardians whether it signed up for the job or not. By December I'd stopped seeing a server, a patch failure, a locked-out user as isolated events. I saw patterns, dependencies, governance failures. The first stirrings of an architect's voice.

2016 in one sentence: Audits don't tell you that you're sloppy. They tell you exactly where.