News
3/29/2008
01:12 PM
Terry Sweeney
Terry Sweeney
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Lockdown Tradeoffs

Enterprise users and consumers alike have been scared straight about data protection, given the regular headlines about laptop theft or misplaced hard drives. But as users rush to secure the desktop, are their good intentions making the jobs (and lives) of storage pros more difficult?

Enterprise users and consumers alike have been scared straight about data protection, given the regular headlines about laptop theft or misplaced hard drives. But as users rush to secure the desktop, are their good intentions making the jobs (and lives) of storage pros more difficult?I ask this as after reading over this interesting review of whole-disk encryption which looks at seven different products and rates them on ease of use, cool extras, cost, and manageability.

There's certainly no good reason not to encrypt. It's gotten a lot easier and more transparent to the user in the last five years. Many programs are even available free of charge, and whether you're Windows or open source based, there are lots of choices. In many cases, crypto developers have gone to great lengths top ensure that their protections don't swallow up tons of capacity or overhead.

We'll leave the issue of whether your data's worth protecting for another time. Better yet, we'll check in with you on this topic a few minutes after you discover your laptop's gone. Funny how urgency can often create value.

What's less clear to me is how these programs get treated from a data center perspective (assuming that the usage case is business, and not standalone, personal data). Do the virtual volumes on which these encrypted files reside get backed up as well by enterprise servers? Is it presumed that IT has signed off on approved programs or that file protections won't make a hash of daily or weekly backup processes?

And what about the impact of encryption on the wave of data de-duplication that's sweeping the market? If it doesn't make them moot, what does encryption do to restoration times? I'm guessing it's not going to accelerate them any.

I'd love to hear from readers about how you address this, either with your users or CIO. Does one crypto policy fit all where backup's concerned? Let me know.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.