Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

2/8/2019
02:00 PM

6 Reasons to Be Wary of Encryption in Your Enterprise

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

Encryption Is Opaque

Encryption works. That is, once encrypted, data can't be examined without being unencrypted. That's great if you're trying to thwart a hacker. It's considerably less great if you're trying to check data for consistency or regulatory compliance.

If the need for transparency exists for data at rest, then the solution is relatively simple, if possibly expensive: Decrypt the data, examine it, then re-encrypt it if the data must be recommitted to the database. It might be possible to design a process that does all of this without an excessive performance penalty. But things get vastly more complicated when the encrypted data is in motion, flowing through a VPN.

In most cases, looking inside the data flowing through a VPN requires launching a man-in-the-middle attack against yourself. The VPN must be terminated, the data decrypted and inspected, then a new tunnel created linking the data to its destination. Doing this, especially at enterprise scale, is expensive and introduces at least one additional point of failure for the network. Some security solutions say they can do certain levels of inspection without unencrypting the network traffic, but they are still new and at least somewhat limited in the inspection they can perform.

(Image: cutimage via Adobe Stock)

3 of 7
Comment  | 
Print  | 
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.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.