

Who Needs Access: You know the folks in marketing need access to the marketing portal on SharePoint, but do you know specifically who should have access? And when someone changes jobs, gets a promotion, or moves departments, are you even notified? And with that notification, are you informed about what changes in access are necessary as part of the personnel change? If you’re like most IT departments, the information you receive is probably little more than just a list of everyone in marketing.

(If you can think of another, please add it in the comments section below.) Here are the four: I can think of 4 degrees of separation that keep your security from being as accurate and robust as possible. So, how many degrees of separation can IT really find itself in? Your level of security depends on how many degrees of separation you are from the security you wish to implement. In reality, it may be that your best effort is really a least effort. Given that most of you usually strive to grant the lowest level of privilege required (that is, you’re not wanting to give everyone full access to everything), it’s important to understand just how bad the separation really is.Īcknowledging the existence of this separation is crucial for one very important reason:īy not recognizing that there is a gap between IT and the business teams that are closer to the action, IT runs the risk of “living in a bubble” - of believing that it has a complete handle on security, with all users having exactly the permissions necessary to accomplish their job, and nothing more. In fact, one 2013 study showed that this separation was just a little over 3.5 people.Īlthough not as widely recognized, there is also a degree of separation between the people in IT who establish levels of security (usually through groups within Active Directory) and the people who are closest to the resources and applications for which that security is provided.

We are all well aware of the theory that every person is separated from everyone else by only six people.
