RE: Navy Marine Corps Internet hit

2003-08-20 Thread Scott Weeks
On Wed, 20 Aug 2003, McBurnett, Jim wrote: : -It sounds like a "turnkey" operation, with EDS managing everything. They : -may have 100,000 users with identical configurations (software, patch : -levels, etc) in one big flat network. A large homogeneous population is : -vulnerable to a common

Re: Navy Marine Corps Internet hit

2003-08-20 Thread Scott Weeks
On Wed, 20 Aug 2003, Sean Donelan wrote: : On Tue, 19 Aug 2003, Scott Weeks wrote: : > on the .pif, .scr, etc. attachments...) Maybe I was just lucky. Most : > likely, though, they did not create "security zones" to keep problems : > contained within certain network segments and not let them ou

RE: Navy Marine Corps Internet hit

2003-08-20 Thread McBurnett, Jim
On Tue, 19 Aug 2003, Scott Weeks wrote: -> on the .pif, .scr, etc. attachments...) Maybe I was just lucky. Most -> likely, though, they did not create "security zones" to keep problems -> contained within certain network segments and not let them out to destroy -> other networks. -Luck is very

Re: Navy Marine Corps Internet hit

2003-08-20 Thread Sean Donelan
On Tue, 19 Aug 2003, Scott Weeks wrote: > on the .pif, .scr, etc. attachments...) Maybe I was just lucky. Most > likely, though, they did not create "security zones" to keep problems > contained within certain network segments and not let them out to destroy > other networks. Luck is very impor

Re: Navy Marine Corps Internet hit

2003-08-19 Thread Adi Linden
> > Obviously they didn't filter 135, 137-139, 445, and inbound > > Not obvious. I know of several sites that were infected even though they > had filters in place, due to infected laptops being brought on-site. Filtering ports 135, 137-139, 445, and only delays the inevitable...

Re: Navy Marine Corps Internet hit

2003-08-19 Thread Scott Weeks
On Tue, 19 Aug 2003 [EMAIL PROTECTED] wrote: : > Obviously they didn't filter 135, 137-139, 445, and inbound : : Not obvious. I know of several sites that were infected even though they : had filters in place, due to infected laptops being brought on-site. :: The new EDS managed Navy Mar

Re: Navy Marine Corps Internet hit

2003-08-19 Thread Gary E. Miller
Yo Scott! They better start blocking port 25 too. That has been the big problem today... RGDS GARY --- Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701 [EMAIL PROTECTED] Tel:+1(541)382-8588 Fax: +

Re: Navy Marine Corps Internet hit

2003-08-19 Thread vern
> Obviously they didn't filter 135, 137-139, 445, and inbound Not obvious. I know of several sites that were infected even though they had filters in place, due to infected laptops being brought on-site. Vern

Re: Navy Marine Corps Internet hit

2003-08-19 Thread Scott Weeks
Obviously they didn't filter 135, 137-139, 445, and inbound, so I doubt we can hope that they were blocking it outbound to keep their machines from infecting other networks... scott On Tue, 19 Aug 2003, Sean Donelan wrote: : : : The new EDS managed Navy Marine Corps Intranet with 100,

Navy Marine Corps Internet hit

2003-08-19 Thread Sean Donelan
The new EDS managed Navy Marine Corps Intranet with 100,000 users has become so congested by worm traffic it can not be used for useful work today. http://www.nwfusion.com/news/2003/0819navy.html