full-disclosure - Re: Linux - Indicators of compromise

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 16 Jul 2012 11:20:55 +0200
From: Michael Stummvoll <fulldis@...mmi.org>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: Linux - Indicators of compromise

> Greetings FD,

Hi

> Does anyone have any guidelines/useful material on analysis logs of a
> Linux machine to detect signs of compromise? 

First thing: You can NOT surely determine if a machine is compromised
within the machine itself. Once a machine is compromised it can
(theoretical) react to all your approach to detect it and manipulate
the output of your tools.

If there is something compromised there is a high chance that it has to
communicate to somebody. So you could dump the network traffic on your
router or add an (transparent) networklogger between your machine and
the router.

Another way would be shutting down the machine an analyzing it with an
live-cd. But there is not a general way to go sure, its compromised or
not.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/