On Fri, 22 Aug 2003, Jason Joines wrote:
We have a completely Linux back-end environment but unfortunately
hundreds of windows desktops. I'm pretty tired of all the attacks on
the unprotected windows boxes but don't have the authority to put up a
network firewall. We protect all of our Linux servers with iptables.
Does anyone know of a similar tool for windows, particularly w2k? The
built-in stuff seems to be virtually worthless.
The native filter in WinXP can be configured to totally block or totally open selected ports. Unfortunately you have to open 135 etc. if you expect to have outsiders mount your filesystems or (I think) if you want to mount theirs. Not much help there. 3rd party products might be more flexible.
I think you have a social engineering problem. Has your department chairman or dean or whatever gotten hit by MSBlaster, SoBig, etc? Explain to him/her that a virus could ruin his whole day. Here at UCLA several other departments were essentially shut down because they had no firewall. My department has a very effective one, plus a pretty aggressive policy on patches, and we evaded MSBlaster, but due to the lack of internal barriers and some machines that were missed, SoBig got us yesterday. The campus telecom service has taken the "unprecedented" step of blocking relevant ports at the campus perimeter, to protect our less clueful departments from the worms and to protect the outside world from our less clueful departments. Tell that to your chairman.
James F. Carter (postmaster) Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: jimc@xxxxxxxxxxxxx http://www.math.ucla.edu/~jimc (q.v. for PGP key)
You're exactly right, it's a social/political problem. My direct supervisor, the college IT manager and his direct supervisor, the dean of the college, are 100% on board. We have asked for permission to put
up our own firewall to protect the network many times and been denied.
We have asked for the university network operations group to put up
whatever they like, NAT us, etc., etc., and been denied may times. The
campus was hit with thousands of infections and when we asked to have
routing of port 135 completely disabled in and out of our network and
disabled on the switches, they couldn't believe we wanted that and had
to have it in writing first.
We had many machines hit but were fortunate enough to be able to clean and patch them via network boot (PXE - Rembo Tool Kit - http://www.rembo.com). Many of the other colleges had no such tool and are having to manually rebuild machines. We have a new CIO over the university system who seems to worship microshaft. His security philosophy seems to be "microsoft can release patches faster than hackers can come up with new attacks and viruses". We have lots of unusual applications that often get broken by microshaft patches and like to do thorough testing before deploying them.
Maybe a few more attacks wacking thousands of machines will change their policies.
Jason ===========
