Applying Least Privilege: Backup User with Execute-Only Access

Quick Answer

Least privilege is the correct principle because the scenario describes granting an employee exactly the narrow capability their job requires, the ability to execute a backup command, while deliberately withholding broader permissions like reading or modifying the underlying data that aren't necessary to accomplish that specific task. This is the essence of least privilege: access should be scoped to the minimum set of permissions needed to perform a defined function, not granted more broadly just because it might be convenient or because a single elevated account is easier to set up. In practice, this often means using a purpose-built execution capability, such as running a backup utility with a scoped or read-only snapshot mechanism, rather than granting the employee general read or file-level access that would let them view or alter the actual data being backed up. The security value here is concrete: if that employee's account were ever compromised, or if the employee made a mistake, the damage is limited to what a backup-execution privilege alone could do, rather than extending to full read or write access over sensitive data. This scoped-permission approach is what separates least privilege from simply assigning a role that happens to include backup duties among a wider set of permissions; the goal is always the narrowest access that still lets the job get done. When a question describes assigning only the specific permission needed for one task while explicitly excluding broader access, that's least privilege in action.