On Sun, 24 Jul 2005 16:29:09 +0100, "Borrox"
<Spamoff@foad.co.uk> wrote:
>How would you suggest/recommend the best way to rid of anything lurking in
>the background?
There are tons of tools on the 'net, I can't begin to give
you a comprehensive list at the moment but a few ideas:
MSCONFIG- check what's starting at boot
Windows' Temp folder (and user temp folder(s))- spyware
likes to hide there in addition to the Windows, Winnt,
System folders. You can ofen spot new files, those with
modified or new dates. Sometimes it's the order in which
you clean that matters. For example, removing all things
with automated scanners then booting to safe mode and
deleting files.
Automated scanners and blockers- scan with more than one,
after updating their data (signature) updates. Spyware
Blaster, Adaware, Spybot Search & Destroy, etc.
Other ways to check startup (boot items)- HijackThis,
BHODemon, StartupList, etc.
More than one brand of Antivirus program after having
updated it. If those aren't sufficient there are also
online scanners such as;
http://security.symantec.com/ssc/hom...KVYRMHCGVRVRMN http://www.pandasoftware.com/actives...&Ref=PR-AS-107 http://housecall.trendmicro.com/ http://www.ravantivirus.com/scan/ http://www.trojanscan.com/trojanscan/trojanscan.htm
Naturally there are also the operating system patches, and
patches for any other programs one might install that have
internet connectivity.
An audit of the installed software can be necessary too.
Some things like toolbars and browser extentions install
spyware along with them. If user perpetually installs such
things they'll just keep reinfecting themselves. Easiest
(or rather, quickest attempt) at discriminating them is to
Google search for that software title along with "spyware".
For example, if user has Weatherbug installed (or is
planning to install),
http://www.google.com/search?q=Weatherbug+spyware
Ultimately, if at all possible determine the point of entry,
the security hole that allowed infection. If this isn't
done, the system could become reinfected rather quickly.
Resolutions depend on the hole but generally one doesn't
want ANY holes, so towards that end one must balance
functionality with security.
For example, does someone "need" to run Outlook /Express
and/or Internet Explorer? If the answer is yes then one
should also look into whether they need ALL the features
(potential security holes) in these products, and how are
they configured. Just disabling those holes is part of
WinXP SP2's purpose, but ultimately details on doing that
are enough that it's beyond the scope of an (already too
long) usenet post. Once again, Google comes to the rescue-
security is an ever popular topic and you should find enough
hits to keep you busy for quite awhile.