| 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
| ||
|
Message-Id: <8592A505-DB3B-4521-90F0-46DCDC5D11FB@riskologist.com> Date: Mon, 16 Jul 2012 20:02:29 -0400 From: Jerry Bell <jerry@...kologist.com> To: Ali Varshovi <ali.varshovi@...mail.com> Cc: "full-disclosure@...ts.grok.org.uk" <full-disclosure@...ts.grok.org.uk> Subject: Re: Linux - Indicators of compromise Hello Ali. Is your question about investigating a set of servers you suspect may be infected, or setting up a steady state monitoring strategy to alert when/if a host is compromised? Regards, Jerry On Jul 14, 2012, at 8:46 AM, "Ali Varshovi " <ali.varshovi@...mail.com> wrote: > Greetings FD, > > Does anyone have any guidelines/useful material on analysis logs of a Linux machine to detect signs of compromise? The data collection piece is not a challenge as a lot of useful information can be captured using commands and some scripts. I'm wondering if there is any systematic approach to analyze the collected logs? Most of the materials I've seen are more aligned to malware and rootkit detection which is not the only concern apparently. > > Thanks, > Ali > . > --------------------------------------------- > Sent from my BlackBerry device > > _______________________________________________ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html > Hosted and sponsored by Secunia - http://secunia.com/ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists