The Setup Behind Microsoft.com
Toreo asesino writes "Jeff Alexander gives an insight into how Microsoft runs its main sites. Interesting details include having no firewall, having to manage 650 GB of IIS logs every day, and the use of their yet unreleased Windows Server 2008 in a production environment.
"In terms of how we protect the sites, we utilize (starting at the outside edge of the network and working in):
..."
1. Cisco Guards for DoS detection and automated response
2. Router ACLs are in place to block unnecessary ports
That's what a firewall does... and the funniest thing that this guy doesn't know the definition of a firewall.
Read and Comment at my BLOG
!!!
I read it as "We had to turn them off when we installed everything"
That's correct. However, something intended to be secure, like a firewall, comes out of the box unable to work at all (well, most of the high-end ones). 100% of all functionality may be installed when delivered/setup, but until manually activated, nothing actually works. I haven't tried the most recent version of IIS, but I'm used to it opening up the services upon install, then giving default "not configured" web pages. That is functionally no better than leaving the services off and is less secure than leaving them off. If it is intended to be "secure" at all, everything would start off (including DHCP client) until someone got on it and configured it. But then, people would complain that it doesn't work out of the box. If you buy a Cisco access point, you'll see that they have big stickers all over the device telling you that it doesn't work. But that was a change from the enabled-as-an-insecure-bridge configuration they came in initially.
Learn to love Alaska
Hmm...Is it worth buying Windows 2008 solely to put it on the net without a firewall (as they brag about doing) and then suing them for false advertising when it has porn popups on it 15 mins later?