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.
We have almost 140 Linux Suse servers running in virtual environment, All the users are login to system as root account. There will be no check who is login and executing what.
My task to restrict the root account and promote the user named accounts and once the user login his account he can siwtch to root and perfrom the activities.
The above task i achieved by using sshd_conifig file changes of "Permirtrootlogin no" and "Allowusers" and its working fine.
but here is another problem came if tow users login their named account and switch to power users than again i can't track who is performed what
Kindly advise the industry best practice to implement the user security or at initial level of security what are steps i have to follow
probably you can try sudo and sudoers, that can give you more restriction and more logging features. Also you can check the owner of the terminal, usually it will remain the original user (who opened that terminal - or logged in).
Definitely use sudo and DON'T give them all privs, it negates the the the whole soln.
Find out what cmds each user NEEDS (not wants!) and give them only those.
Why don't you switch on mandriva system, root account is separate on limited user account like on windows that you can use limit account for ordinary user.
Last edited by tailinlinux; 04-09-2013 at 03:49 AM.
Kindly advise the industry best practice to implement the user security or at initial level of security what are steps i have to follow
I'll echo what pan64 and chrism01 suggested. It will take a lot of adjustment (especially for users who were used to do everything as root without thinking) but not allowing users to switch to root and limit the commands they may execute by using Sudo is the best way. On top of that SELinux audit service can track both user sessions and commands, albeit the latter in a limited fashion, so if you need a more complete user session audit trail please see Rootsh. *Note logging to a remote well-protected syslog server would be advisable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.