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
0 Comments
Current Issue
Flash Poll
Surviving the IT Security Skills Shortage
Cybersecurity professionals are in high demand -- and short supply. Find out what Dark Reading discovered during their 2017 Security Staffing Survey and get some strategies for getting through the drought. Download the report today!
Twitter Feed
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database CVE-2018-10839
PUBLISHED: 2018-10-16
PUBLISHED: 2018-10-16
PUBLISHED: 2018-10-16
PUBLISHED: 2018-10-16
PUBLISHED: 2018-10-16
From DHS/US-CERT's National Vulnerability Database CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2018 UBM, All rights reserved
Tweet This