Meh, OS’s don’t die at EOL. There are thousands, if not millions, of machines running Win2k that simply can’t be upgraded because they run industry systems.
And before anyone cries about security - if you’re relying on the OS for your security you’re ignoring everything else (the other layers) that are required… You’re doing it wrong.
There are thousands (tens of thousands?) of Win2k machines that can’t be upgraded because they drive industry systems. Hell, there’s Win95 machines doing the same. Their security is ensured by incorporating layers of control… As should be done with any system, commensurate with it’s risk and criticality.
You are also forgetting millions of consumers still running Windows XP or 7 and not upgrading not because something critical depends on it, but because “if it ain’t broken, don’t fix it”.
If there are exploitable remote execution attacks at the OS level that’s a pretty big hole to fill in with additional measures. Anything short of totally isolated would be a risk imo.
Meh, OS’s don’t die at EOL. There are thousands, if not millions, of machines running Win2k that simply can’t be upgraded because they run industry systems.
And before anyone cries about security - if you’re relying on the OS for your security you’re ignoring everything else (the other layers) that are required… You’re doing it wrong.
There are thousands (tens of thousands?) of Win2k machines that can’t be upgraded because they drive industry systems. Hell, there’s Win95 machines doing the same. Their security is ensured by incorporating layers of control… As should be done with any system, commensurate with it’s risk and criticality.
You are also forgetting millions of consumers still running Windows XP or 7 and not upgrading not because something critical depends on it, but because “if it ain’t broken, don’t fix it”.
If there are exploitable remote execution attacks at the OS level that’s a pretty big hole to fill in with additional measures. Anything short of totally isolated would be a risk imo.