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.

Careers & People

Stop Blaming Users. Make Security User-Friendly.

50%
50%

Jelle Niemantsverdriet of Deloitte visits the Dark Reading News Desk at Black Hat to explain how security can be improved if security tools, error messages, and help desk calls educate users and 'put a smile on someone's face.'

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
bboink1
100%
0%
bboink1,
User Rank: Strategist
9/15/2016 | 10:09:50 AM
Users Still need the Blame
Users are the weakest link.  When the security measures are in place and the user still does the wrong thing because there are no consequences adapting the security to them is a futile effort.  The only fix to that is to hold the users accountable.  Case in point, trying to make cars that keep you in your lane or stop for you is needed because people are not paying attention.  How about when they cause an accident due to texting and driving they get rewarded with license revocation.

As far as taking the empathy approach with the user, it is difficult to build security around the "I am going to do what I am going to do regardless of what I am supposed to do" attitude. No matter how friendly you make the security if it inhibits the user from doing what they want they will ignore and find a way around.

Designing better error messages for the users is a good idea.  It is possible if the error message was informative it would help the tech that has to work on it.  .That being said most of the users do not read the error message so that would not help a user.  Just as they do not read the popup that downloads the cropto-ware on their system.  An example of this is when the help desk gets the call of "It just stopped working," and "I didn't do anything."  Of course the answer of "ummm....I don't know" when asked "What did the error message say?"  Users just click without reading.

The point of rewarding them for doing what they are supposed to do is like giving them a trophy for showing up.  Then they will expect a trophy all of the time and the value of the "incentive" will diminish.  This is what created the situation that we are in with the users not caring now.

I do agree that security must be made to be a bit more user friendly.  I also believe that the users will adapt in a downward direction to put us back in the same situation.  I think accountability is the direction that will produce a bigger bang for the buck.
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...