Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Linux
[Top] [All Lists]

Re: Attempts to push spam through apache

Subject: Re: Attempts to push spam through apache
Date: Sun, 22 Aug 2004 22:11:13 -0600
When a box gets compromised, its a good idea to strip it down.  I think
I saw it termed as "burning it down and paving over it" or something of
that ilk.  I realize that in the real world, that of course is not
always possible ;)

Anyway, my point: A rootkit scan should be a daily cronjob on any DMZ or
public services server.  I personally prefer rkhunter due to the fact
that you can customize output for console or cronjob usage, and its
relatively frequent updating and heuristic scanning.

This of course, should be complimentary to other security measures and
works in tandem with firewall rules, a network IDS, properly configured
servers, and any measure of custom tools (I find that portsentry, when
properly configured for the services running on the server, is a good
one to run on servers as well).

-- 
-----------------
Wayne S. Frazee

On Sun, 2004-08-22 at 03:09, Adrian Popescu wrote:

use "chkrootkit" tool , or other programs (run it a couple of times).
Also look in /tmp or other places where Apache (User/Group)
are able to write and see if there is any trace left.




Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>