3 ms·
I wouldn't say Microsoft is pretty good at updates. I once installed a patch for a security flaw in DNS in our Windows DNS server and got reamed by my boss for
by cr4zy 15y ago
I wouldn't say Microsoft is pretty good at updates. I once installed a patch for a security flaw in DNS in our Windows DNS server and got reamed by my boss for bringing our site down. I have found the policy of installing all updates when first setting up a Windows server and then never touching it again to work quite well. We also keep all non-HTTP access to a VPN.
Alternatively, don't use Windows. App Engine is my preferred platform for new projects and the security on that is most likely top notch and constantly upgraded.
- fakeempire 15y ago"I have found the policy of installing all updates when first setting up a Windows server and then never touching it again to work quite well." I think you need to reevaluate your policies immediately. Not applying security patching isn't a good policy.
- nobody314159265 15y agoYou have a choice between: The chance of someone bothering to hack you multiplied by the chance that the new patch doesn't include several new security bugs Or the chance of a new untested patch bringing down your business.
- mkchandler 15y agoThis is why we use QA servers for most of our systems. We try our best to test all functionality on a patched QA server before deploying patches to our production servers. We have had good success doing this (with Windows at least.)
- nobody314159265 15y agoSo leaving your main system exposed to the new zero day vunerability for a whole day while you do the tests!
- briandear 15y agoThe real question is why anyone would willingly run a windows server for anything?
- DanBC 15y agoNo. You wait a few hours (maybe half a day) and see how other people get on with the patch. Then you patch. Or you leave more holes for the automated bots and worms to exploit.