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.

Security Management

10/16/2017
06:17 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

HONEST Poll Results: How Much Should You Encrypt?

What is the 'Goldilocks Zone' when it comes to encryption? Security Now community members speak out in our latest poll.

If the goal is to keep data out of unauthorized hands, should organizations simply encrypt every bit they possess?

That's the essence of the question we posed in the most recent Security Now poll. Is it possible to miss encrypting important data? Or is it possible to encrypt too much? Executives responding to our poll are split, but only in the degree to which data should be encrypted. It's tough to find anyone in the community here who thinks encryption itself is a waste of time.

As always, we recognize the limitations of our methods. We understand the polls we conduct on our pages aren't going to fuel academic research. That's why it's important we properly label the conclusions. I think it's accurate to call them a Highly Opinionated, Not Especially Scientific Tally -- or, as I like to think of them: HONEST results.

More than half of those responding said encrypting everything is the way to go. Why take a chance, right? But community member (and Security Now contributing writer) Joe Stanganelli sounded a cautionary note in the comments when he wrote, "I put 'Encrypt everything,' but there are compelling arguments to be made against encrypting everything -- particularly in highly regulated industries where encryption can hamper accessibility to the point of potentially resulting in questionable compliance."

In addition to regulatory compliance questions there are undeniable costs in performance, resource utilization and software or service licensing when you encrypt everything. It can be the safest option but security has always been a matter of cost versus reward and many organizations may well find the scales tipped in the wrong direction when it comes to encrypting everything inside the perimeter.

Another 30% said encryption is the right answer, but need only be applied to an organization's most critical data. This is a widely used standard though it does carry with it an extra cost: An organization must go through its data to determine what is actually important. While it sounds like an exercise that should fall well within the bounds of "obvious," there can be a great deal of nuance and legal or regulatory judgement that teams must apply before encryption can take place.

Of course, a handful of folks decided that throwing up their hands in frustration and defeat was the proper response. It's certainly easy to understand why they might reach such a conclusion -- encryption is a complex topic from both policy-making and technology points of view. Nevertheless, the growing number of public incidents indicates it's a topic that each organization must deal with -- and deal with sooner, rather than later.

Keep an eye out for the next Security Now poll. It's going to deal with a question of an international nature -- one that may well have you questioning who deserves to be on your lists of friends and enemies.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...