Timeline for Debian - limiting access for not-fully-trusted admin users
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 10, 2017 at 2:28 | comment | added | John Mahowald | The liability of the company is not entirely an IT problem. With some legal advice you set the expectations in an employment agreement, and not be entirely ruined personally should the worst happen. And then take out insurance against those risks if appropriate. And so on. | |
| Oct 9, 2017 at 20:31 | answer | added | HackSlash | timeline score: 2 | |
| Oct 9, 2017 at 20:06 | comment | added | Zip | Selinux or apparmor can restrict access to a lot of things, even to the root user, but you'd need to configure them properly... | |
| Oct 9, 2017 at 16:21 | comment | added | anneb | Why would a stranger want to ruin your company? It is more likely that the stranger or you yourself make mistakes that could cost 'millions'. Prepare backups, set limits. | |
| Oct 9, 2017 at 16:16 | comment | added | anneb | This depends on the tasks you want 'the stranger' to do. You can probably configure the system in such a way that the stranger can only do the tasks that you specify. For instance you can limit or set the sudo command for a sub-set of tasks | |
| Oct 9, 2017 at 16:00 | history | asked | Matthias | CC BY-SA 3.0 |