Locking Down Linux Servers with “sudo” command | the principle of least privilege
#stayinandexploreitkb #informationtechnology #blueteam #redteam #oscp #blackhat #pentester #pentesting #cybersecurity #hacker #tool #redteaming #bugbountytips #bugbounty #linux #nmam #linuxsudo #linuxserver #linuxsecurity #cybersecurity #hacker #blueteam #readteam #tools #nmap oscp #blackhat #pentester #informationtechnology #pentesting #cybersecurity #hacker #tool #redteaming #bugbountytips #bugbounty #linux #linux_tutorial #fail2ban #iptables #linuxinhindi #linuxnetwork #linuxadministrator #linuxadmin #linuxadministration #linuxkernel #linuxforbeginners #security #hosting #vps #vpsserver #vpssecuritie #bestpractice #bestvideo
We’ve been using the sudo in every Linux server's distro to run or execute commands with elevated privileges or you can say with root (administrator) rights.
In fact, sudo usage took a deeper look when you are “Managing Users and Permissions”.
Therefore, I won’t go into too much detail regarding sudo here, but some things bear repeating as sudo directly impacts security.
Introduction to Sudo
First and foremost, access to sudo should be locked down as much as possible.
A user with full sudo access is a threat, plain and simple.
All it would take is for someone with full sudo access to make a single mistake with the “sudo rm -rf /” command to cause you to lose data or render your entire server useless.
After all, a user with full sudo access can do anything the root can do (which is everything).
By default, the user you’ve created during installation will be made a member of the sudo group.
Members of this group have full access to the sudo command. Therefore, you shouldn’t make any users a member of this group unless you absolutely have to.
In my upcoming video, I will demonstrate in detail how to “Manage Users and their Permissions” and will talk about how to control access to sudo with the visudo command.
References
https://en.wikipedia.org/wiki/Filesys...
https://help.ubuntu.com/community/Lin...