Least privilege - get what you need, not what you want
I like trains. I would quite like to drive the train, but that is not on the cards as I have no training, so I sit/stand with everyone else in the passenger area - I am assuming someone is driving and it is not being done by an artificial robot train driver... yet...
My firm belief is as security people we are starting to forget the basic principles of security that help protect something important, us and the information we use. And, we forget to explain, sell, story tell them to people - we just say "well you must ensure you have least privilege", and people think "what is he/she on about...?".
One of my favourite principles is "least privilege" - so giving people access to only what they need access. This certainly seems like a very strong way to protect what is important. If people only have access to what they need and they become compromised, the bad actor (they aren't acting) can only access what you have access to.
"The principle of least privilege (POLP) is the practice of limiting access to the minimal level that will allow normal functioning. Applied to employees, the principle of least privilege translates to giving people the lowest level of user rights that they can have and still do their jobs. The principle is also applied to things other than people, including programs and processes." - taken from.http://searchsecurity.techtarget.com/definition/principle-of-least-privilege-POLP
Simple you think? Not so.
In our personal lives we at least feel like we can do anything, go anywhere, buy what we like (for those who have the money), do what we want with nobody telling us the rules. We are obviously aware of laws and what is "right" but in general we have "freedom". At work our companies strive (feeling positive) to protect us and the information we use and therefore generate policies and processes that are for work - but do leak into our personal world too.
In work we need to deliver quicker and more, we need to show progress, we need to be flexible to change and pressures. And, with Cloud software being available at a click, time to evaluate and risk assess a solution is the same time to make a cup of tea.
So there is an immediate conflict in this principle, it conflicts with our perception of freedom.
What can we do as security professionals if we think least privilege is important, in two steps?
1. DON'T tell people they must follow "best practice". Telling people what to do with no reason or context will no doubt create bad behaviour
2. DO tell stories. People remember stories and here is one from me:
The story of security professional Michelle and blue sky dashboards Cloud federation
"Hey Michelle, this is cool, with our new Cloud people directory I can point this funky app we use to create blue sky dashboards at our directory and sign in with one set of credentials. Let's do that." explains enthusiastic Dave.
"Nice, I just checked with blue sky dashboards and this means they have access to our directory, is that ok, do we trust them?" said Michelle.
"Not sure, I just bought a couple of user licenses with my credit card" replies Dave.
"Erm, okay,they have access to information they don't need, all our company directory" explains Michelle.
"Ah, I never thought that was even possible, let me think on this..." sighs Dave.
Obviously this is made up (!), but I think we can all ponder on this next time we are tempted to roll out the "follow best practice" line and maybe turn our response into a story.
Try it and let me know.
Keep well.
Adam

Comments
Post a Comment