Date: Wed, 20 Aug 2003 09:48:53 +0100 From: MeatballTurbo <carl.robsonnopsamcing-czechs.com> Subject: Re: OT - Windows port 135 virus alert
In article <3F3A46E4.80B69224nopsamlamelame.org>, lamealameadingdongnopsamlamelame.org says... > You would be well advised to bring all your machines in - patch them and > run a complete system scan on them all given you are an ISP.. Moreover - if > you are running VPN - you will also need to get everyone who logs in to do > the same on their home machines.. > Luckily we are running Symantec Corporate anti virus, so once a new def file is out, the whole network gets updated automatically, and new versions are checked for nightly. Also full system scans are run nightly too, with live protection running as well. As well as the firewall stopping it getting in (not forgetting muppets bringing in machines from home, becuase it has a problem (that would be the sales guy)) we where all advised to patch as soon as it became public. Nobody here has been infected apart from the one external machine brought in to find out what was wrong with it, and we were all running upto date defs, and the MS patch. Most of the servers are Linux based, so imune from that kind of attack, but of course they are harder work to keep upto date, because vulnerabilities and fixes are more prolific. We all used to manage and update out own AV software (I had a daily 1am update 2am full deep scan schedule) but the sales drones didn't know how do it, or didn't care, and were sometimes running 6 month old defs, hence the company policy on running the corporate Lan version now. Don't worry, I won't get into a Holy war crusade with you. I know that linux and windows on servers is essential if you want to cover as many customers as possible. I think we even have a couple of hosted client Mac servers in the Datacentre. -- The poster formerly known as Skodapilot. http://www.bouncing-czechs.com
 |
 |
 |
 |
 |
