News for hackers. Stuff that matters.
Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by zdw on Friday November 25, 2011 @02:25PM (#3277968)
The problem for this falls directly on vendors that make their crap hard to keep up to date. I'm not blaming Microsoft for this, as they're actually pretty decent - the problem usually is with 3rd parties that don't validate on the newest releases.

Seriously people - there's a reason OS vendors have prerelease software programs. If you're not testing your software on say the Windows 8 beta or on prerelease versions of OS X 10.7.3, then when it doesn't work on day one of release it's likely your fault, not the OS vendor for breaking stuff.

The larger issue is that software testing is a PITA... this is probably a shared issue between Dev and Ops. Every time I see a new single function "installs software X outside of package management" program, I have to think that both sides are doing the other a disservice. Dev's should be able to get their software on multiple platforms easily, and Ops shouldn't have to wrestle to get it installed. We've only been wrestling with this problem for the last 30 years...

Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by cr4zy on Friday November 25, 2011 @10:22PM (#3278968)
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.

Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by fakeempire on Friday November 25, 2011 @10:36PM (#3278987)
"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.

Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by nobody314159265 on Friday November 25, 2011 @11:10PM (#3279031)
You 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.

Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by mkchandler on Saturday November 26, 2011 @01:16AM (#3279236)
This 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.)
Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by briandear on Saturday November 26, 2011 @04:26PM (#3280744)
The real question is why anyone would willingly run a windows server for anything?
Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by nobody314159265 on Saturday November 26, 2011 @01:08PM (#3280308)
So leaving your main system exposed to the new zero day vunerability for a whole day while you do the tests!
Re:Hacked NASDAQ Servers were running on unpatched Windows 2003 by DanBC on Saturday November 26, 2011 @10:24AM (#3279911)
No. 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.