It is very possible they became pressured to perform an upgrade because something on the old system was compromised and out of support.
Legacy stacks quite often maintain old tech, and then somewhere in there will be a library that has a critical exploit and has been totally replaced for future major versions.
Unsure if you’re defending or objecting to the comment. Flawed and outdated code needs to be replaced and that pressure should be maintained. The ‘Go Fast And Break Things’ model works OK in an internal corporate environment, but not when we’re talking about the FAA or banking. Outlook can fuck right off.
Outdated hardware needs to be replaced, but I’m with JJ about the likely root cause. Some boss decided that the cheapest way to fulfill their job/contract was to install or deploy whatever ChatGPT told them would work.
fair - not broken (yet) doesn’t mean shouldn’t be maintained, though.
Most solid state things are pretty much static, by definition, but there’s still stuff like plastic dry rot or metal corrosion. We’re talking decades, but we’re also talking decades. If that critical router failed outright the result might have been worse while a replacement was sourced, with a follow-on failure when the code bombed too.
I’m not defending the outage – there should have been better testing – but I’ve been on the receiving end of a minimal but crucial server’s power supply capacitor failing (the post-mortem was wild to figure out what broke). That server was ancient and should have been replaced before it failed and the fire drill to recover it (even just taking a backup and restoring to a VM) was unpleasant.
It is very possible they became pressured to perform an upgrade because something on the old system was compromised and out of support.
Legacy stacks quite often maintain old tech, and then somewhere in there will be a library that has a critical exploit and has been totally replaced for future major versions.
Unsure if you’re defending or objecting to the comment. Flawed and outdated code needs to be replaced and that pressure should be maintained. The ‘Go Fast And Break Things’ model works OK in an internal corporate environment, but not when we’re talking about the FAA or banking. Outlook can fuck right off.
Outdated hardware needs to be replaced, but I’m with JJ about the likely root cause. Some boss decided that the cheapest way to fulfill their job/contract was to install or deploy whatever ChatGPT told them would work.
No it doesn’t. Nuclear launch systems were running on floppy disks in the 2010s, IIRC, if it ain’t broke then “fixing it” is at best a nice to have.
Now, if it’s insecure then we should replace it. Unless you’re replacing it with something even less secure (like AI, perhaps).
fair - not broken (yet) doesn’t mean shouldn’t be maintained, though.
Most solid state things are pretty much static, by definition, but there’s still stuff like plastic dry rot or metal corrosion. We’re talking decades, but we’re also talking decades. If that critical router failed outright the result might have been worse while a replacement was sourced, with a follow-on failure when the code bombed too.
I’m not defending the outage – there should have been better testing – but I’ve been on the receiving end of a minimal but crucial server’s power supply capacitor failing (the post-mortem was wild to figure out what broke). That server was ancient and should have been replaced before it failed and the fire drill to recover it (even just taking a backup and restoring to a VM) was unpleasant.
On the bank, a possibility, on Microsoft, based on what they detailed sounded like a go at performance optimization.
For security, I get it, there is little time to lose in this scenario, usually. But huge volume of changes for change’s sake are also in play.