Comments
Newest First | Oldest First | Threaded View
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.
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.
White Papers
Video
1 Comments
Current Issue
5 Emerging Cyber Threats to Watch for in 2019Online 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
How Enterprises Are Developing Secure Applications
IT security and application development are disparate processes that are increasingly coming together. Here's a look at how that's happening.
Twitter Feed
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database CVE-2019-11378
PUBLISHED: 2019-04-20
PUBLISHED: 2019-04-20
PUBLISHED: 2019-04-20
PUBLISHED: 2019-04-20
PUBLISHED: 2019-04-20
From DHS/US-CERT's National Vulnerability Database CVE-2019-11378
PUBLISHED: 2019-04-20
An issue was discovered in ProjectSend r1053. upload-process-form.php allows finished_files[]=../ directory traversal. It is possible for users to read arbitrary files and (potentially) access the supporting database, delete arbitrary files, access user passwords, or run arbitrary code.
CVE-2019-11372PUBLISHED: 2019-04-20
An out-of-bounds read in MediaInfoLib::File__Tags_Helper::Synched_Test in Tag/File__Tags.cpp in MediaInfoLib in MediaArea MediaInfo 18.12 leads to a crash.
CVE-2019-11373PUBLISHED: 2019-04-20
An out-of-bounds read in File__Analyze::Get_L8 in File__Analyze_Buffer.cpp in MediaInfoLib in MediaArea MediaInfo 18.12 leads to a crash.
CVE-2019-11374PUBLISHED: 2019-04-20
74CMS v5.0.1 has a CSRF vulnerability to add a new admin user via the index.php?m=Admin&c=admin&a=add URI.
CVE-2019-11375PUBLISHED: 2019-04-20
Msvod v10 has a CSRF vulnerability to change user information via the admin/member/edit.html URI.
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2019 UBM, All rights reserved
Tweet This