1. Mistake: treating “golden” systems as untouchable. Avoiding patches may protect a 24/7 service or a long ETL window temporarily, but leaves operating systems, middleware, and SQL Server exposed to security flaws, bugs, and stability problems. section 9.11
The MagicChoc outage
MagicChoc excluded its online sales database and marketing warehouse from patching. An attacker exploited the unpatched servers, moved laterally, and launched ransomware across the company, making every database inaccessible. The immediate availability concern became a company-wide security and business crisis. section 9.11
Patching is operationally painful, but postponing it creates more than cyber risk. Cumulative Updates can fix security flaws, correct bugs, improve stability, and occasionally add features. Unpatched systems therefore face avoidable attacks and outages. section 9.11
Use a safer operating rule:
- Do not permanently exclude production or “golden” servers from regular patching. section 9.12
- Reduce patching outages with AlwaysOn availability groups or failover clustered instances. section 9.12
- Resolve customer-availability and ETL constraints through creative scheduling rather than indefinite deferral. section 9.11 section 9.12
