Security Incidents mailing list archives
Re: Compromised Win2000 machine.
From: Mark Newby <mark () dranton com>
Date: Wed, 29 May 2002 21:38:00 +0100
H C wrote: > [...]
Danny took the typical action seen of most admins...port scanning the system from the outside, and comparing the open ports to lists of known trojans and services. This is inconclusive at best, and leads to a lot of speculation and time-wasting. Better to run fport on the system (if NT/2K...if the system is XP, run netstat w/ the '-o' switch) instead, to see the process to port mapping. [...]
...but I thought the advice for a (possibly) compromised box was *not* to run executable programs that resided on that host, as they can't be trusted?
mark ---------------------------------------------------------------------------- This list is provided by the SecurityFocus ARIS analyzer service.For more information on this free incident handling, management and tracking system please see: http://aris.securityfocus.com
Current thread:
- Compromised Win2000 machine. Daniel Hay (May 28)
- Re: Compromised Win2000 machine. H C (May 28)
- RE: Compromised Win2000 machine. Kit (May 28)
- RE: Compromised Win2000 machine. Don Weber (May 29)
- RE: Compromised Win2000 machine. H C (May 29)
- Re: Compromised Win2000 machine. Daniel Hay (May 29)
- Re: Compromised Win2000 machine. Mark Newby (May 29)
- Re: Compromised Win2000 machine. H C (May 29)
- Re: Compromised Win2000 machine. Patrick Andry (May 29)
- Re: Compromised Win2000 machine. H C (May 30)
- Re: Compromised Win2000 machine. - Follow UP Daniel Hay (May 30)
- Re[2]: Compromised Win2000 machine. Joris De Donder (May 31)
- Re: Re[2]: Compromised Win2000 machine. H C (May 31)
- RE: Compromised Win2000 machine. Don Weber (May 29)
- <Possible follow-ups>
- Re: Compromised Win2000 machine. ghb the irrepressible (May 29)
