The Principle of Least Privilege
The Principle of Least Privilege says that users or applications should only have access to the what it needs to access and that access should be as limited as possible. This idea can be applied to any number of things, but it is a very important topic when talking about security.
The idea is that processes, users, modules, or whatever can only access what they need to in order to function. This keeps users in check since they don’t have any access to anything outside their home directories (or whatever). It keeps developers in check since their code can only access a small set of files or processes. It keeps hackers in check since the Apache server they’re hacking can’t access the password file. It even keeps administrators in check since it forces them to use sudo, which is logged to syslog.
Like everything, this is a simplistic description, but it’s very important for every administrator to adopt this idea.
You may also want to check out SELinux if you’re a Linux admin, which is a system that is used to enforce least privileges for nearly everything on a Linux box.
- Netbox Upgrade Play-by-play - April 25, 2023
- Sending Slack Messages with Python - March 15, 2023
- Using Python Logging to Figure Out What You Did Wrong - February 26, 2023
[…] 2 years ago this month, I wrote a terribly-written article on The Principle of Least Privilege. Since then, though, my writing has improved (at least, I think it has), the topics have […]