Replies: 5 comments 3 replies
-
Restricting the use of su, and using sudo in its place, provides system administrators better control of the escalation of user privileges to execute privileged commands. The sudo utility also provides a better logging and audit mechanism, as it can log each command executed via sudo, whereas su can only record that a user executed the su program. https://linux.die.net/man/8/pam_wheel Here an exmaple for centos7, I will check it if it work on Ubuntu. BTW @jvleminc , currently i'm working 'cis-red-hat-enterprise-linux-8-rhel-benchmark' repo, I may need your help with it :) |
Beta Was this translation helpful? Give feedback.
-
Hmmm, I didn't understand your answer :-( Did you confirm that the task is incomplete and can/should be completed with the pam_wheel commands? (My company is not working with RedHat, so no real interest from my side, sorry :-)) |
Beta Was this translation helpful? Give feedback.
-
I'm not sure what should I do with task 5.6, |
Beta Was this translation helpful? Give feedback.
-
I will have a look, I also don't really understand how to implement this. :-/ |
Beta Was this translation helpful? Give feedback.
-
PR merged, will lock this thread. |
Beta Was this translation helpful? Give feedback.
-
Not sure if placing the
root
user in thesudo
group is sufficient to restrictsu
access.Other manuals state:
Solution: Create an empty group that will be specified for use of the su command. The group should be named according to site policy.
groupadd sugroup
Add the following line to the /etc/pam.d/su file, specifying the empty group:
auth required pam_wheel.so use_uid group=sugroup
Beta Was this translation helpful? Give feedback.
All reactions