5 ms·
I'd say yes, especially if they're not getting security updates and are connected to the rest of the network. Honestly, the cost of it getting broken into seem
by codefined 9y ago
I'd say yes, especially if they're not getting security updates and are connected to the rest of the network.
Honestly, the cost of it getting broken into seems to be significantly higher than the cost of upgrading the systems.
- noxToken 9y agoThe problem is getting the funding for such a thing approved when it's not already stipulated in the contract from the start. "Who cares if it's EoL at Microsoft? Is it broken? Will it break when they put it in EoL status? Alright then - leave them be."
- thehardsphere 9y ago> Honestly, the cost of it getting broken into seems to be significantly higher than the cost of upgrading the systems. We don't necessarily know what the costs of "getting broken into" are. It depends on who you are and what the breakin does. It could only cost the time it takes for IT to restore a backup and plug the hole. I mean, yeah, if you suffer a spectacular ransomware attack and are screwed so badly that you must pay the ransom and everyone finds out, that's probably more expensive than updating. But that's not the only threat or even the most likely threat your organization may contend with. We also don't necessarily know what the costs of updating are. If you're just doing boring office stuff, the costs are low and you should just fork over the money to Microsoft and get it over with. If you need to update a bunch of custom drivers for some devices that are important to your business because the device manufacturer went out of business, that could be a vastly expensive software development project that your organization can't afford to do. Certainly that costs a lot more than having Bob in IT rewind the tapes when Russian hackers get ransomware past the firewall.