6 ms·
The best approach is to assume there's a renegade employee constantly trying to screw the company over. Granularity of permissions should be set to minimize the
by _Adam 4y ago
The best approach is to assume there's a renegade employee constantly trying to screw the company over. Granularity of permissions should be set to minimize the blast radius to the absolute minimum they need to do their job.
- bombcar 4y agoHell, you should offer an internal bounty to any employee who reports “I got access to something I shouldn’t need”.
- notakio 4y agoPart of what I do first at any new employer is ask myself the question, "if I wanted to burn all of this to the ground, how would I do it?" I generally don't share the fact that I'm going through this little thought experiment with my management, but it helps triage what's currently "broken", and gives me a clearer focus on what needs to be fixed. If I'm thinking about it, I can be assured that someone with differing motivations likely already has, or soon will be thinking about the same.
- UncleMeat 4y agoThis approach is possible but increases the complexity of your problem by enormous amounts. I know of only a very tiny number of companies that have an active goal of preventing rogue insider threats in a serious way. And the solutions do meaningfully inhibit developer productivity.