A research team uses a shared workstation to run an overnight data analysis task. The task is started under the researchers’ main account, but they want to prevent team members from altering the analysis while it runs. Which measure best fixes this oversight so the background task is isolated from the team’s usual login?
Run the analysis under a dedicated account that has limited permissions for that task
Move the job to another machine and keep a single user account on the new workstation
Increase privileges for the account that runs the job so it can manage its own security
Use the same account for the task and rely on detailed auditing to track modifications
Using a separate process identity with limited permissions helps ensure the data analysis job runs with fewer privileges than a human user account. This limits the actions a logged-in researcher can perform on the job. Adding more privileges to a shared login or just monitoring user commands does not isolate the job’s credentials. Migrating to a different device ignores the need for more granular process restrictions on the current system.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is a dedicated account with limited permissions better for running tasks like the data analysis job?
Open an interactive chat with Bash
What is the difference between auditing user commands and limiting an account's permissions?
Open an interactive chat with Bash
How does privilege management contribute to system security?