Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi ,
I have recently inherited a LINUX Network without any documentation anything at all . I would like your advise on :
1) How can I collect and check logs to see If someone was trying to break in .
It sounds to me like you want to configure syslog on all your boxes to send all its messgaes to a loghost. That way anything sent through syslog will get log to the single box where you can carry out your checks. Have a look at man syslog.conf at it has some pretty good examples. You might also want to look at the various howto's available on http://www.tldp.org
Jharris' advice will be an excellent way to improve your current logging situation.
a LINUX Network without any documentation
There is a problem you will need to address and that is the current unknown/untrusted state the boxen are in. If you're speaking about break in attempts in the past tense: the attempts itself aren't interesting, but those that succeeded are. If some did, then I would advise caution: chances are you probably won't find much info about them in the logs. Start logging all in/outbound traffic, determine the most crucial boxen, backup, change all passes and start your audit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.