<< n0cmonkey: while I agree a textbook firewall configuration would have strict outgoing filter rules, perhaps restricting the user to 80/tcp and 443/tcp out of the internal network, this isn't very practical, especially in a large network environment. Sure, you can configure it like that; but people want to send email through their SMTP server someplace else, or they want to telnet someplace for some research collaboration, or some exec at another site is screaming because he can't make his napster work. etc. I find it's easier to filter on stuff I *KNOW* I wouldn't want on the network and stuff I can actually defend filtering [yahoo! games, napster, kazaa, gnutella, etc] and allowing everything else outbound from workstations. how do you keep the users in check? FW-1 w/ WebSense as a CVP plug-in for web filtering, and Trend Micro's InterScan product for scanning web pages for malicious applets and email going in and out for virii. My two cents 🙂 >>
Of course you have to take every site on a case by case basis. I dont have as strict filtering on my outbound at home because I do quite a bit of things from those machines, but in a work environment I like to keep the users in check as much as possible. But 80, 443, 22, and maybe 23 are important ones I would let out on most networks. Others would depend on what the function of the network is. DMZs in particular should have *VERY* strict outbound filtering in my opinion. Only allow out what you absolutely need to.