Operations | Monitoring | ITSM | DevOps | Cloud

In early 2026, two back-to-back Linux kernel exploits, Copy Fail (CVE-2026-31431) and Dirty Frag (CVE-2026-43284 & CVE-2026-43500), shattered assumptions about how quickly attackers can weaponize disclosed CVEs. Dirty Frag, a zero-day Linux vulnerability that affected most major distributions, had PoC exploits published within hours of its disclosure. It’s a stark reminder: the timeline between vulnerability disclosure and active exploitation has shrunk from weeks to hours.

Here’s a story that plays out constantly in enterprise IT, and few people talk about afterward. A team runs an evaluation with multiple vendors using a structured scoring process. Then, they make their choice, but six months into deployment, the platform that excelled in every demo is now struggling with the actual environment. The IT leader who signed off is in a room with their CIO, trying to explain why the numbers fail to match the projections.

I’ve been doing this for over thirty years. Sysadmin, ops lead, global teams, and more data centre migrations than I’d like to admit. Site to site, P2V, V2V, cloud, hybrid, all of it. Every migration gets sold as a clean, well-planned transition. None of them are. They go wrong in very predictable ways. Not because moving infrastructure is especially difficult, but because nobody ever has a clear, current view of what’s actually running, what’s changed, and what still matters.

Drive failures are a matter of when, not if. The good news is that most modern drives warn you before they fail, using S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology). The challenge is collecting that data across a fleet and making it actionable. The new inventory-smartctl module makes this straightforward with a single cfbs add. Once installed, the module auto-detects all storage devices, caches their SMART data, and exposes it as inventory attributes in Mission Portal.