I was looking over the definition of secure the other day and found the following entry:
v. fix or attach (something) firmly so that it cannot be moved or lost
And then I applied it to security initiatives within IT. The goal aligns well; you want to fix (read: configure) your network so that the security controls you put in place doesn’t are not “moved or lost” – that is, in our case, allowing someone to bypass those controls.
But, for most organizations, the idea of giving someone elevated privileges is given little focus, other than to consider whether the person in question needs the permissions. So, in essence, you simply choose to trust the person and likely, never give their use of permissions a second thought.
Now look at the definition of trust:
n. firm belief in the reliability, truth, ability, or strength of someone or something
...