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.

Comments
IT Leaders, Employees Divided on Data Security
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/30/2019 | 11:05:38 PM
Re: Brief them properly
Definitely provides further context to the study. I still think its important to cite that different folks see things through different lenses. These differences help provide a more concrete basis to the study and in turn validate it.
DavidHamilton
50%
50%
DavidHamilton,
User Rank: Apprentice
4/30/2019 | 2:24:53 AM
Brief them properly
It is expected of employees to give their answers as such because they are not security experts. They have not been properly briefed regarding what are the risks involved during their daily work habits. They answered as such because they do not know any better.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/26/2019 | 9:53:45 AM
Risk Ownership
I think two facets come into play here. Ultimately, as data owners executives of said data are more heavily responsible for securing data at the company even though the data custodians (employees) directly touch said data. Due to this they way the risks more heavily and are more inclined to support data that creates a narrative that more needs to be done to secure the data. Employees on the other hand, and I believe the term is used to be department agnostic not security centric, support a business function. Many will not stop to think of the ramifications of what they are doing until they are told by a security function that it is not best practice. Due to this ignorance it is more than likely that those individuals surveyed would be inclined to think that they are not jeopardizing company data.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
3/25/2019 | 2:38:22 PM
Han Solo and Srgt. Schultz
Solp: It's not my fault.  Schultz:  I know nothing.  Of course employees are blameless, as there is that line called UNEMPLOYMENT and so they have done nothing wrong and if they did, well, it is the corp at fault because they did not provide security controls.  It was there, so, well I had to take it with me.  You never stopped me from walking into the safe (wide open anyway) and remove cash.  



Tor Weaponized to Steal Bitcoin
Dark Reading Staff 10/18/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
State of SMB Insecurity by the Numbers
Ericka Chickowski, Contributing Writer,  10/17/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-9501
PUBLISHED: 2019-10-22
The Artificial Intelligence theme before 1.2.4 for WordPress has XSS because Genericons HTML files are unnecessarily placed under the web root.
CVE-2019-16971
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\messages\messages_thread.php uses an unsanitized "contact_uuid" variable coming from the URL, which is reflected on 3 occasions in HTML, leading to XSS.
CVE-2019-16972
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\contacts\contact_addresses.php uses an unsanitized "id" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2019-16973
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\contacts\contact_edit.php uses an unsanitized "query_string" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2015-9496
PUBLISHED: 2019-10-22
The freshmail-newsletter plugin before 1.6 for WordPress has shortcode.php SQL Injection via the 'FM_form id=' substring.