Proactively address the insider threat
Last week, I wrote about insider threat and some of the risks it can pose to your organization. Today I’d like to follow up and provide some tips to help address it.
There are many strategies for dealing with the insider threat, so I’ve chosen to highlight the things that organizations most often miss.
Some of these things may seem obvious, but I would ask you to honestly assess whether or not you are living the principles mentioned below. As Morpheus famously said, “there is a difference between knowing the path and walking the path.”
So here goes.
1) Think about insider attacks before they occur.
As I mentioned yesterday, many organizations have absolutely no plan in place for dealing with insider threats. Let’s be clear – if you have an incident, you will almost certainly incur a loss. But if you plan appropriately, you can significantly mitigate that risk.
Most people never even get to the planning phase.
2) Cultivate a culture of security.
The medicine that I am prescribing here must be adopted at every level of the organization to be effective. If only the security and technologists in the company understand the things I’m mentioning here, the security problems you currently have will persist, despite your best intentions.
I have seen many examples where a world-class security team is stymied by a business side of the house that doesn’t fully grasp the security implications of their business decisions.
The worst part is, the risks are often simply overlooked or marginalized without being properly analyzed. In many of these cases, if the true risks were known, completely different decisions would be made.
To be successful here, organizations should train and equip every employee to protect information. A successful program sustainably shifts the way employees think about the value of information and their role in protecting it, and is built with a clear understanding of how employees interact with information in their everyday work.
3) Assume nothing is 100% secure.
Any other assumption comes with huge risks. Most companies have a really hard time with this because they have been led to believe that they can somehow address every problem that comes up. It’s uncomfortable to assume things will fail, but every security expert will tell you that there is no such thing as 100% security.
Embrace this one idea, and you will fundamentally make better security decisions.
4) Build defense in depth, and assume that everything will fail.
This has been said a thousand times, but it bears repeating until organizations actually do it. Every security mechanism will eventually fail, so it is key to put as many security layers in place as possible so that when one fails, there is something there to back it up. And it’s not all about technology – sometimes the best layers are human-based processes!
Which leads me to my next point …
5) Trusting in technology alone is absolutely the wrong approach.
Security technologies are a part of the picture, but people and process are just as important, if not more so. It’s extremely important to know that every security technology can be bypassed in some way, no matter how good it is.
Many of the technologies we deploy to resolve insider threats are flawed in some way. Data loss prevention (DLP) software is a great example of this. DLP software helps keep honest people honest, but no matter what the vendors tell you, It will never stop the skilled, dedicated attacker.
Unfortunately, many organizations are deploying DLP as if it were the holy grail of security. Every technology comes with trade-offs, and the overhead of something like DLP is not worth the trade-offs for every organization.
6) Make the assumption that your employees are also potential attackers when building all your internal systems and processes.
Even if you could be positive that every employee has your organization’s best interests at heart, the assumption that internal is safe leads to major architectural weaknesses.
The assumption that “internal is OK” leads to organizations having a hard outer shell and a soft gooey inside. And from experience, I can tell you that there is no such thing as an impenetrable outer shell.
A healthy dose of paranoia is required here. If you build your systems as if your employees will attack everything, you will make better architectural decisions and you are much more likely to frustrate an attacker who does get part way in.
If you can honestly say that you are doing all of these things, then you are probably better off than 95% of organizations out there.
