Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.