What are some common mistakes and oversights when implementing storage encryption? |
 |
| 04 Oct 2007 | Kevin Beaver |
|
|
The first one that comes to mind is the assumption that if it's encrypted, then it's secure. I think this is a dangerous mindset. You know, encryption doesn't automatically mean security. It's all in how the encryption is implemented and managed. That's the big one, and I tend to see that most with management and less technical people. They hear that they've got laptop encryption or that they've got a hardened data center and they assume that all is well, but that's hardly ever the case. You actually have to validate that with tools and ethical hacking techniques.
I would also say there is a mindset that compliance doesn't really affect us. But, especially with regard to storage, compliance affects all of us in some fashion. Even if your industry isn't governed by a particular law or industry regulation, it still affects you in a downstream fashion through a business associate, a partner, service level agreement (SLA), etc. So, compliance has to be on your radar and management's radar.
Also, in most networks that I'm seeing, people don't have a clue as to what information they actually have. They also don't have a clue where it's stored or what security risks it's up against. So, if they don't know this stuff, they can't reasonably know what needs to be protected. I think the assumption is that everything that is sensitive is on servers or protected storage so there's not that much to worry about. This is wrong. I'm seeing vulnerabilities in these areas all the time. In any given network today, there are megabytes, if not gigabytes, of files scattered all across different hard drives and storage systems within the network. I think sensitive information is everywhere across the network, it's unprotected, and it's waiting to be compromised. And, a lot of people are oblivious to it in many cases.
Check out the entire Storage Encryption FAQ guide.
|
|
|
|
