During a routine audit, an enterprise discovered that processes running with special permissions accepted parameters from user sessions. Which approach best prevents a process from carrying out unintended actions on behalf of an untrusted initiator?
Restricting system calls in a container environment
Enforcing separate tokens for privileged actions
Using static analysis to find memory leaks
Disabling dynamic library loading for user sessions
Enforcing separate tokens for privileged actions reduces the possibility of mixing user-supplied input with tasks that require higher permissions. This prevents an administrative process from accepting questionable parameters. The other options do not address the risk of unintentionally executing privileged actions due to user input. Dynamic library loading controls can reduce executable injection, but they do not separate high-privilege tasks. Restricting system calls in a container environment can reduce the attack surface, yet it does not prevent elevated tasks from taking unauthenticated input. Static analysis for memory leaks focuses on programming errors, not on verifying who triggers sensitive operations.
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.
What are separate tokens for privileged actions?
Open an interactive chat with Bash
How does dynamic library loading differ from enforcing separate tokens?
Open an interactive chat with Bash
Why aren't system call restrictions effective in this scenario?