Operations

2/8/2019
02:00 PM
0%
100%

6 Reasons to Be Wary of Encryption in Your Enterprise

Encryption can be critical to data security, but it's not a universal panacea.
Previous
1 of 7
Next

Encryption is the answer to every cybersecurity issue. That message seems to flow from countless articles and blog posts on the Internet — so why isn't everything, everywhere, encrypted? As it turns out, issues with encryption make some data best left unencrypted where it sits.

Now, there's no denying that encryption is an enormously valuable tool and far more data should be encrypted than is currently being protected by the technique. Especially in certain regulatory frameworks, it can seem that full encryption is a forgone conclusion as a strategy.

But encryption should be given the same level of scrutiny as any other technique before deployment. In particular, a half-dozen factors should be taken into account when an organization is considering encryption. Knee-jerk reactions seldom provide the best results, and that's as true for encryption in cybersecurity as in any other endeavor.

What has your organization decided to do about encryption? Are you encrypting everything, drawbacks aside? Or are you proceeding cautiously and encrypting in stages? Let us know in the comment section, below.

(Image: mrhighsky vis Adobe Stock)

 

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
davinoishi
100%
0%
davinoishi,
User Rank: Apprentice
2/12/2019 | 11:35:33 AM
Transparent Encryption
While file and volume encryption have limits, there are transparent solutions available that allow information to remain encrypted even in use.
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7303
PUBLISHED: 2019-04-23
A vulnerability in the seccomp filters of Canonical snapd before version 2.37.4 allows a strict mode snap to insert characters into a terminal on a 64-bit host. The seccomp rules were generated to match 64-bit ioctl(2) commands on a 64-bit platform; however, the Linux kernel only uses the lower 32 b...
CVE-2019-7304
PUBLISHED: 2019-04-23
Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run arbitrary commands as root. This issue affects: Canonical snapd versions prior to 2.37.1.
CVE-2019-0223
PUBLISHED: 2019-04-23
While investigating bug PROTON-2014, we discovered that under some circumstances Apache Qpid Proton versions 0.9 to 0.27.0 (C library and its language bindings) can connect to a peer anonymously using TLS *even when configured to verify the peer certificate* while used with OpenSSL versions before 1...
CVE-2017-12619
PUBLISHED: 2019-04-23
Apache Zeppelin prior to 0.7.3 was vulnerable to session fixation which allowed an attacker to hijack a valid user session. Issue was reported by "stone lone".
CVE-2018-1317
PUBLISHED: 2019-04-23
In Apache Zeppelin prior to 0.8.0 the cron scheduler was enabled by default and could allow users to run paragraphs as other users without authentication.