* Compromises data - The root kit
Maybe and mild damage. A root kit means that somebody wants the machine to keep working. As long as it keeps serving, our business is not lost. I can cope with a root kit, and deal with it at my leisure.
Eh? If a root kit has been installed, how can you ensure the integrity of your data? If the cracker is smart enough to cover their tracks, this strikes me as closer to the *catastrophic* category ... now where are your customer's credit card numbers again? Is that a modified ls in your /bin, or are you just happy to be sending packets of crucial information to nasty.crackers.net that are going to be sold to the competition?
Even if you restore from a known-good state, you still stand to lose any data collected between the time that state was saved and the time the rootkit was installed.
OK, tripwire and the like can help with these issues, but my inclination would be to err on the side of caution were I to find a rootkit installed on any machine I admin.
perl -e 'print "How sweet does a rose smell? "; chomp ($n = <STDIN>); +$rose = "smells sweet to degree $n"; *other_name = *rose; print "$oth +er_name\n"'
In reply to Re: Re(Jepri) 2: Obfuscation and viruses
by arturo
in thread Obfuscation and viruses
by WrongWay
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |